<div dir="ltr"><div class="gmail_extra">Hi Tony!</div><div class="gmail_extra"><br><div class="gmail_quote">On 3 April 2016 at 02:02, 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">You are proposing, appropriately, a new way to handle version
control for Sugar.<br></div></blockquote><div><br></div><div>I'm not sure about that :) I didn't intend to :) </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">
There is documented procedure to add new activities or to update
activities on ASLO. This procedure is working with update
notifications in the ASLO mailing list. This process is independent
(and ignorant of) github. So your proposal is a change to current
practice.<br></div></blockquote><div><br></div><div>I don't follow - ASLO indexes activities and distributes their ".xo" packages, but they are not developed on that site... So moving their source hosting to Github would not effect ASLO...? :) </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 separate tracking would be a byproduct of changing to a github
based procedure from our current practice
(<a href="https://bugs.sugarlabs.org/" target="_blank">https://bugs.sugarlabs.org/</a>) In my experience all bugs/issues are
reported here whether against a specific Sugar activity (say Etoys)
or against a component of Sugar.<br></div></blockquote><div><br></div><div>As I said in earlier emails, I think Github has handled organization-wide issue tracking appropriately. </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 am not sure whether Sugar is supported as a desktop by all GNU
machines. In particular, 32-bit Ubuntu is not supported. Debian
dropped the Record activity because it does not use gstreamer1.0 or
gtk3. This is one of the eight protected activities which are
considered essential to a running Sugar.</div></blockquote><div><br></div><div>Thanks for sharing these details :) </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">As far as I know, SOAS does
not offer an 'install' option.<br></div></blockquote><div><br></div><div>Should it? :) </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">
You are right about the issue of which activity versions support
which Sugar releases. This is complicated by the factor that some
ASLO entries have more recent versions stored as 'earlier versions'.
Someone needs to grab the handle and set up an ASLO system that can
identify which activities work with which versions and make
potentially multiple versions visible in ASLO as necessary.<br>
<br>
During the recent GCI, Walter Bender and some of the participants
came up with a scheme which allows an activity with a binary blob to
identify the XO model and configure with the appropriate blob at
run-time. I suspect there are activities which need this fix.</div></blockquote></div><br>I hope there is an issue for this :D<br clear="all"><div><br></div>-- <br><div class="gmail_signature">Cheers<br>Dave</div>
</div></div>