<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Sam,<br>
<br>
Thanks for the proposal. Naturally this raises the question of the
relationship between your ASLOv3 and the GSOC project. Do you see
two parallel implementations or a merger of the two projects?<br>
<br>
I agree with your proposal to install the activity repositories in
<meta charset="utf-8">
<span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;"
id="docs-internal-guid-78a30f39-1e1f-f9e5-c9d9-8adc92bd7aa5"><a class="moz-txt-link-freetext" href="https://github.com/sugar-activities/">https://github.com/sugar-activities/</a>.
Combining 600+ repositories in with the Sugar core repositories
seems unmanageable. Someone would need to create this community
on github. This needs to be decided quickly so the repostiroies
are in place to support ASLO. We have to get past Walter saying
this is what we are doing and James Cameron saying no decision
has been made. <br>
<br>
Some more detailed comments on the proposal:<br>
<br>
<b>Actors and use cases</b><br>
<br>
I think there is a fourth, very important actor, the deployer.
The deployer needs to configure a laptop installation but does
not have the technical skills to build an image. A practical
solution is to flash a prebuilt image (e.g. 13.2.8) and then
update the activity configuration as needed. The best help we
could provide for the developer is a network install capability
from the institution's lan. <br>
<br>
Since James Cameron (and possibly Jonas Smedegaard) are the only
image builders I know of, it seems hard to justify automation.
Perhaps the scope of the 'update url' should be shifted to
providing a build system that creates a Sugar image for various
target systems. <br>
<br>
<b>Workflows</b><br>
</span><br>
1. The other requirement is for an 'owner' to create the
repository. This is analogous to the current procedure in ASLO.<br>
2. I think the event should be 'new version released'. I am a git
newbie (actually an old dog having trouble with new tricks) but I
think git practice is to signal a release by creating a branch.
This creation could generate the signal.<br>
3. On the ASLO side, I think the information needs to be in
activity.info. If this is done ASLO side, then the published
bundle will not match the repository. If all of the information is
in activity.info (or other file in the activity/ directory), the
developer would have complete control over it. <br>
3. I assume tar files are used in xol bundles. So far these are
not published on ASLO. I think xol bundles should be handled
independently of ASLO.<br>
<br>
Tony<br>
<br>
<br>
On 05/19/2017 05:14 AM, Samuel Cantero wrote:<br>
</div>
<blockquote
cite="mid:CAGA8R4=k3Ci8OY40rsnO-_oT2MN_G+8MSx169puRzNuV+KxUhQ@mail.gmail.com"
type="cite">
<div dir="ltr">I just realized that proposal wasn't send to
sugar-devel list. It was removed from the thread at some point.
So I just forward the link again. Sorry for people subscribed to
multiple lists.
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div>Sam C.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, May 17, 2017 at 4:06 PM, James
Cameron <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Yes,
please attach any files that developers should see.<br>
<br>
The sugar-devel@ mailing list has a message size limit of
1024K.<br>
<br>
Messages above the limit are held for approval by Sebastian
and I.<br>
<br>
My previous offer still stands; if people truly have no time
to edit a<br>
Wiki, set up public web hosting, or upload to github, send
it as mail<br>
to the list and I'll approve it.<br>
<br>
<a moz-do-not-send="true"
href="http://lists.sugarlabs.org/archive/sugar-devel/2017-May/054193.html"
rel="noreferrer" target="_blank">http://lists.sugarlabs.org/<wbr>archive/sugar-devel/2017-May/<wbr>054193.html</a><br>
<br>
On the other hand, there have been Wiki edits in the last
few<br>
hours thanks to Walter;<br>
<br>
<a moz-do-not-send="true"
href="http://wiki.sugarlabs.org/index.php?title=Summer_of_Code&curid=2570&diff=100299&oldid=100290"
rel="noreferrer" target="_blank">http://wiki.sugarlabs.org/<wbr>index.php?title=Summer_of_<wbr>Code&curid=2570&diff=100299&<wbr>oldid=100290</a><br>
<br>
Progress. Yay.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
James Cameron<br>
<a moz-do-not-send="true"
href="http://quozl.netrek.org/" rel="noreferrer"
target="_blank">http://quozl.netrek.org/</a><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>
</font></span></blockquote>
</div>
<br>
</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>