<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi, James<br>
<br>
If you go to activities.sugarlabs.org, you can register via the
register link at the top right. This is not registration for
Sugarlabs but for ASLO.<br>
<br>
As I understand the github repository, access with the ability to
commit changes is closely held. The enables proposed changes to be
vetted before a commit.<br>
However, the web page has a sign in link which gives limited access
(create pull requests and comment on them, for example). That same
two-step process is used for ASLO. The developer submits the change
which puts it into a sandbox pending review.<br>
<br>
Actually Sugar has files, directories and a command shell (Terminal
activity). It is relatively easy to switch activities via the Frame.
I say this from several years of experience developing on the XO
(easier than using usb flash keys to move code to the XO to test).
The fact that Browse does not support flex and the unique XO screen
makes testing on an XO essential if that is the target. <br>
<br>
The process of making changes via github to the Sugar core is
certainly reasonable. However, nothing in this procedure interferes
with a developer modifying and testing a change on an installed
Sugar independently of the internet. Access to the internet being
needed only to submit the change.<br>
<br>
The issue is not to use Sugar for everything, it is to use the
available computer for everything (XO). In general, the XO is the
first computer our users have used and, aside from an Android
device, the only computer available. While used desktops and laptops
are available, the $100+ funds are not available.<br>
<br>
The 'current setup' you mention depends on ready access to the
internet, something not available for at least 2/3 of our users. It
is a strength of Sugar that the source code is immediately available
to the user without need of a repository (except access to
activities not installed - a need supplied by a schoolserver). This
allows learners to get into programming in a meaningful way using
only what is installed on the XO. <br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 03/14/2017 11:25 PM, James Simmons
wrote:<br>
</div>
<blockquote
cite="mid:CAN6VRWzd-Utm1e+1AHEqWZ0XhFW3_KZdkihF7TGVK=tjYzPkkw@mail.gmail.com"
type="cite">
<div dir="ltr">All,
<div><br>
</div>
<div>I only meant to make the manual actually tell where we
currently put our code repositories, without rewriting the
whole chapter. (I had hoped that a Google Code-In mentee might
do that, but it didn't happen). The one piece of information
that is still lacking is how to have your account added to the
sugarlabs organization. That happened so long ago that I
forgot how it happened. If someone could remind me I'll add
that information to the note.</div>
<div><br>
</div>
<div>I haven't done any Sugar development in years but I do
program computers for a living and I use Git in my day job.</div>
<div><br>
</div>
<div>Sugar has some good Activities to teach programming, but I
don't think it is a great Activity development platform. For
that you really need files and directories and a command
shell, the ability to run Sugar as more than one user at a
time, etc.</div>
<div><br>
</div>
<div>I understand the desire to use Sugar for everything, but I
think it would always get in the way. You wouldn't expect to
be able to develop an iphone app on an iphone, or at least I
wouldn't.</div>
<div><br>
</div>
<div>If I wanted to teach Activity development to children I'd
get some reconditioned desktop computers and install Fedora
and Sugar on them. I have used nothing but reconditioned
computers myself for years. It is amazing to me what you can
get reconditioned on Amazon and elsewhere for around a hundred
bucks. This is basically my price range for a "new" computer,
and for that I can get a Lenovo or other quality brand with
more than adequate disk space and memory. These computers are
built for use in offices and have many years of life left in
them. In Fedora you can run Sugar as a desktop environment as
well as in a window. You can hook them up to a TV or a
projector (something I remember many people wanted to do with
the XO).</div>
<div><br>
</div>
<div>I don't see ASLO being separate from Git as a problem. I
think of it like the production environment at work. If it's
good enough to use it goes on ASLO. If not, it stays in Git,
but I might push my code to the central repository so others
could fool around with it.</div>
<div><br>
</div>
<div>Part of teach a child programming should be teaching him
good work habits, and I think our current setup promotes that.</div>
<div><br>
</div>
<div>James Simmons</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Mar 14, 2017 at 9:28 AM, Laura
Vargas <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:laura@somosazucar.org" target="_blank">laura@somosazucar.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span class="">2017-03-14 7:13
GMT-05:00 Walter Bender <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:walter.bender@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a></a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span>On Tue, Mar 14,
2017 at 12:45 AM, Tony Anderson <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:tony_anderson@usa.net"
target="_blank">tony_anderson@usa.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> <br>
<br>
<div
class="m_7726506093757599830m_7517597654755239133m_-6695069844156775650moz-cite-prefix">On
03/14/2017 12:03 PM, Alex Perez
wrote:<br>
</div>
<blockquote type="cite">
<div><br>
</div>
I would think ASLO could simply be
made to inspect the contents of an
activity, upon upload, (since it’s
just a zip file), and look for the
necessary string within <a
moz-do-not-send="true"
href="http://activity.info"
target="_blank">activity.info</a>,
such that it could be displayed
under a “details” section of an
Activity, within ASLO. </blockquote>
<br>
What I propose is that the ASLO page
have a link to the github repository.
See the attached screenshot which
shows a link to home page. I would see
this link being added here.<span
class="m_7726506093757599830m_7517597654755239133HOEnZb"></span></div>
</blockquote>
<div><br>
</div>
</span>
<div>+1. But that can be done if (1) we
include the repo path in the info file and
(2) do the work on ALSO to display it (I
think alsroot was looking into this). </div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>
<div>+1 to add the repository link field on ASLO.<br>
<br>
</div>
<div>This is an example where we all agree that
something needs to be done. <br>
<br>
Now, how do you propose we get it done? <br>
<br>
</div>
<span class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>You proposal has no bearing on where
the repo is hosted, as it should not. </div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span
class="m_7726506093757599830m_7517597654755239133HOEnZb"><font
color="#888888"> <br>
Tony<br>
</font></span></div>
<span>
<br>
______________________________<wbr>_________________<br>
Sugar-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Sugar-devel@lists.sugarlabs.org"
target="_blank">Sugar-devel@lists.sugarlabs.or<wbr>g</a><br>
<a moz-do-not-send="true"
href="http://lists.sugarlabs.org/listinfo/sugar-devel"
rel="noreferrer" target="_blank">http://lists.sugarlabs.org/lis<wbr>tinfo/sugar-devel</a><br>
<br>
</span></blockquote>
</div>
<span><br>
<br clear="all">
<div><br>
</div>
-- <br>
<div
class="m_7726506093757599830m_7517597654755239133gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div><font><font>Walter Bender</font></font><br>
<font><font>Sugar Labs</font></font></div>
<div><font><a moz-do-not-send="true"
href="http://www.sugarlabs.org"
target="_blank"><font>http://www.sugarlabs.org</font></a></font><br>
<br>
</div>
</div>
</div>
</span></div>
</div>
<br>
______________________________<wbr>_________________<br>
Sugar-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Sugar-devel@lists.sugarlabs.org"
target="_blank">Sugar-devel@lists.sugarlabs.or<wbr>g</a><br>
<a moz-do-not-send="true"
href="http://lists.sugarlabs.org/listinfo/sugar-devel"
rel="noreferrer" target="_blank">http://lists.sugarlabs.org/lis<wbr>tinfo/sugar-devel</a><br>
<br>
</blockquote>
</span></div>
<span class="HOEnZb"><font color="#888888"><br>
<br clear="all">
<br>
-- <br>
<div class="m_7726506093757599830gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>Laura V.<br>
<font color="#ff00ff"><b>
I&D SomosAZUCAR.Org</b></font></div>
<div><br>
</div>
<div><font size="2"><span
style="color:rgb(102,102,102);font-family:"Helvetica
Neue",Helvetica,Arial,sans-serif">“No
paradox, no progress.” </span></font></div>
<div><font size="2"><span
style="color:rgb(102,102,102);font-family:"Helvetica
Neue",Helvetica,Arial,sans-serif">~
Niels Bohr</span></font><br>
<br>
</div>
<div>Happy Learning!<br>
<br>
</div>
</div>
</div>
</font></span></div>
</div>
<br>
______________________________<wbr>_________________<br>
Sugar-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.<wbr>org</a><br>
<a moz-do-not-send="true"
href="http://lists.sugarlabs.org/listinfo/sugar-devel"
rel="noreferrer" target="_blank">http://lists.sugarlabs.org/<wbr>listinfo/sugar-devel</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>