<div dir="ltr">Tony,<div><br></div><div>Not sure I agree about your asserts regarding github vs gitroious.</div><div><br></div><div>(1) the were/are many activities that were not hosted in gitorious long before we switched to github, so it wasn't obvious where to find the source repo *before* the switch. This is one of the reasons I started add the repo path to the <a href="http://activity.info">activity.info</a> file.</div><div>(2) ALSO needs work and maintenance regardless of where the repos are hosted.</div><div><br></div><div>-walter<br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 13, 2017 at 10:02 PM, Tony Anderson <span dir="ltr"><<a 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">
Hi James,<br>
<br>
Your book is a wonder and should be much more actively promoted. It
is one of the major contributions of Sugar to constructive learning.<br>
<br>
I believe the use of <a href="http://git.sugarlabs.org" target="_blank">git.sugarlabs.org</a> and github are major steps
backwards from the original conception of Sugar activities as
something which users could develop and make available to the
community. In the first place, the activity bundle contains the
source code that is actually being executed. Second, there is a
simple version system in <a href="http://activity.info" target="_blank">activity.info</a>. The Developer Hub at
<a href="http://activities.sugarlabs.org" target="_blank">activities.sugarlabs.org</a> supplies an adequate means to control
maintenance activities (in the PR sense of having someone monitor
changes before releasing them for general use). <br>
<br>
If one wanted to update an activity, say TuxMath, now the first step
would be to clone the repository not install the activity itself. <br>
<br>
The ASLO site needs some work. Currently, the latest version is not
necessarily exposed (see Browse or TuxMath, for example). In some
cases, activities do not support Arm or use Hulahop and there is no
way to specify which versions of Sugar or its platforms are
supported. The availability of maintainers who know the PhP
implementation of ASLO is apparently dwindling. Perhaps Sugar Labs
could undertake to re-implement ASLO using Python (Django, flask,
...) or javascript to broaden the base of potential maintainers. <br>
<br>
However, dependence on github creates a duplicate repository for the
source code. With 400+ activities, there is no mechanism in github
to make the activities visible. Currently it may require searching 7
screens to find if an activity is there (unlike ASLO which has an
effective search capability). <br>
<br>
I am sympathetic to the desire to acquaint our users with git and
the concept of version control. However, this approach limits the
opportunity to those who have internet access (probably a minority
of our users). <br>
<br>
A more effective approach would be to determine how git could be
installed in Sugar ( a git activity?) so that it can be used. Your
book could then be used as a basis for helping our users learn to
develop activities using version-control. In this way version
control can be used locally by the developer prior to submitting an
updated or new activity to ASLO (which may well involve a visit to
an internet cafe). <br>
<br>
Tony<br>
<br>
Tony<div><div class="h5"><br>
<br>
<div class="m_-8702763985395152740moz-cite-prefix">On 03/14/2017 03:39 AM, James Simmons
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">All,
<div><br>
</div>
<div>I have been neglecting the manual <i>Make Your Own Sugar
Activities!</i> ever since I first wrote it. However, I did
manage to make one needed update in the laziest way possible.
Since Sugar Labs has moved away from <a href="http://git.sugarlabs.org" target="_blank">git.sugarlabs.org</a>
in favor of GitHub since I wrote the version control chapter I
have added the following note to that chapter:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><strong>Important Note</strong>: When this chapter was
written Sugar Labs was still using <strong><a href="http://git.sugarlabs.org" target="_blank">git.sugarlabs.org</a></strong>
as its code repository. While this still exists, the
preferred repository is now <a href="https://github.com/" target="_blank">https://github.com/</a>, using
the <strong>sugarlabs</strong> organization. This chapter
is still a reasonable introduction to using Git, but when
you set up your project repository you should use the
excellent instructions provided on GitHub instead of the
Gitorious instructions provided here.</div>
</blockquote>
<div><br>
</div>
<div>I hope this helps in some way.</div>
<div><br>
</div>
<div>James Simmons</div>
<div><br>
</div>
</div>
<br>
<fieldset class="m_-8702763985395152740mimeAttachmentHeader"></fieldset>
<br>
</div></div><pre>______________________________<wbr>_________________
Sugar-devel mailing list
<a class="m_-8702763985395152740moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.<wbr>org</a>
<a class="m_-8702763985395152740moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/<wbr>listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.<wbr>org</a><br>
<a 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><br clear="all"><div><br></div>-- <br><div class="gmail_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 href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br><a href="http://www.sugarlabs.org" target="_blank"><font></font></a><br></div></div></div>
</div></div></div>