<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi, Dave<br>
<br>
As I understand it, what you are trying to do is make github the
place where Sugar activities are kept. Currently, ASLO provides for
upload of an <br>
activity (new or new version) as an xo bundle from the user's file
system. What would be needed is a way to release an xo bundle from
the github <br>
repository. Experience in the last GCI showed that the way Sugar
activities are stored in GitHub is not compatible with the
requirements of an xo bundle.<br>
For example, a Sugar activity must have a top-level folder with the
name xxxxx.activity.<br>
<br>
By custom, the version is shown in the xo file name (e.g.
helloweb-3.xo) and should match the version number given in
activity.info. However, this requires an act by the developer and is
not automatic.<br>
<br>
So I think some programming is required to release activities from
github to ASLO and to update the ASLO developer hub to conform to
the new requirements.<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 05/18/2016 01:52 PM, Dave Crossland
wrote:<br>
</div>
<blockquote
cite="mid:CAEozd0z5avsu2XNms9+DbENhku744gTXRTiJZmA=B77WHTXvdQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">Hi</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 18 May 2016 at 04:29, 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:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">Sugar activities
from the beginning identified versions by version
number. For some activities we have tens of versions in
ASLO. Switching version control from a version number to
git branches may be non-trivial. It would certainly be
helpful to view changes to activities over time. <br>
</div>
</blockquote>
<div><br>
</div>
<div>There are commits where the version is marked in the
activity's commit history, and its easy to tag those
commits as releases; then Github automatically shows them
in a release timeline page. Automating the release process
(ie, making the .xo bundle and uploading it to the release
page as a binary attachment) is also straightforward with
Travis CI. </div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> I still believe it
is far more important to have a link from the ASLO entry
for an activity to its github repo than to include the
link in <a moz-do-not-send="true"
href="http://activity.info" target="_blank">activity.info</a>.</div>
</blockquote>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Great idea :) </div>
<br>
<a moz-do-not-send="true"
href="https://wiki.sugarlabs.org/index.php?title=Vision_proposal_2016&type=revision&diff=98736&oldid=98696">https://wiki.sugarlabs.org/index.php?title=Vision_proposal_2016&type=revision&diff=98736&oldid=98696</a> <br>
<div><br>
</div>
-- <br>
<div class="gmail_signature">Cheers<br>
Dave</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>