<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 2 April 2016 at 22:18, 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: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">The Sugar activities, which represent 90% or more of the Sugar lines
of code, are being relocated to the github accounts of individual
developer/maintainers - not under a single Sugar account. </div></blockquote><div><br></div><div>I think that is fine :) If they would like to make their activity 'official' then they can ask to be invited to the <a href="http://github.com/sugarlabs">github.com/sugarlabs</a> organization, and then after they accept the invitation, they can go to <a href="http://github.com/username/repo/settings">github.com/username/repo/settings</a> and at the bottom move the repo to the org. </div><div><br></div><div>(Or, someone who has joined the org with appropriate permissions can fork their repo into the org, to maintain an 'official' copy of it, and the initial developer or anyone else can then make pull requests to it. However, I think the first way is better since then Github will show that as the 'upstream' repo on network graph pages, eg <a href="https://github.com/sugarlabs/sugar/network">https://github.com/sugarlabs/sugar/network</a>) </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">At the
moment this information is recorded in the <a href="http://activity.info" target="_blank">activity.info</a> file of the
activity itself. This change has not yet been implemented across all
of the activities. <br></div></blockquote><div><br></div><div>Cool - that seems like a good milestone for Sugar Labs this year. I added it to <a href="https://wiki.sugarlabs.org/go/Vision_proposal_2016">https://wiki.sugarlabs.org/go/Vision_proposal_2016</a> </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 don't understand the process. However, it appears that OLPC makes
the release images. It decides which Sugar activities will be
included in a release. I gather that SugarLabs has no say in this.<br></div></blockquote><div><br></div><div>That sounds great to me :) </div><div><br></div><div>As I understand it, Sugar is a desktop environment for all computers that can run GNU, while OLPC makes "OLPC OS," which is a GNU distribution tailored to XO laptops that packages Sugar and GNOME desktops.</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 don't know the technical details, but it would seem desirable to
separate issue tracking into separate Sugar and Sugar activity
branches. </div></blockquote><div><br></div><div>That is unavoidable with the way Github is designed.</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">The issues for Sugar related to releases (e.g. 0.108) and
for Sugar activities to version numbers. Update to Sugar activities
are independent from Sugar releases.<br></div></blockquote></div><br>However, surely some Sugar releases are requirements for some activity versions? Eg, Chat 78 (<a href="http://activities.sugarlabs.org/en-US/sugar/addon/4069">http://activities.sugarlabs.org/en-US/sugar/addon/4069</a>) says it requires a Sugar release of 0.86 or higher (and may not work with 0.108, according to the metadata on that page) <br clear="all"><div><br></div>-- <br><div class="gmail_signature">Cheers<br>Dave</div>
</div></div>