<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Walter,<br>
<br>
I made a pass through the 137 activities. In each case the latest
version (as shown in github) is in ASLO. However, in many cases that
version is not visible on the ASLO page. Strangely, the current
version is often shown in the link to 'an earlier version'. This, of
course, means that visitors to ASLO will in many cases be
downloading an obsolete version. In a few cases, the activity.info
committed in github shows a version like 26.3 although the version
in ASLO shows version 27. This makes it difficult to be sure that
the most recent version committed in github is the same as the one
to be downloaded from ASLO. <br>
<br>
There was a lot of activity on GitHub early in 2016 apparently
motivated by GCI. In several cases the activities were upgraded to
GTK3 but retained the same version number. This, of course, means
again that visitors to ASLO will not realize a need to download a
new version. <br>
<br>
My remark on Turtle Blocks is that the source does not have a github
repository under Sugar Labs.<br>
<br>
In the short run, I think we should put these activities in GitHub
(and ASLO) as Sugar Web activities. Lionel can sort out how to
incorporate them in Sugarizer releases. Since Sugarizer is installed
in Android as a single app, I can see that he would have difficulty
in maintaining separate releases of activities. Perhaps, he can
address this issue first with the server version.<br>
<br>
Today, I hope to start testing current versions of activities in
this group of 137 that failed on Ubuntu Sugar and see if the
problems have been corrected or are correctable. <br>
<br>
A number of the github commit messages refer to adding 64 bit
binaries. Again as part of the ASLO problem - the 'Works with' needs
to show restrictions on activities such as 'requires accelerometer,
works only with XO-4'. <br>
<br>
I am not sure how we can handle an activity where the same version
(update level) requires different bundles for Ubuntu amd64 and XO.
The trick used in GCI of testing the platform means that a bundle
needs to have binaries for multiple architectures. Given the
restricted amount of storage, this may not be practical. <br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 04/13/2017 09:44 PM, Walter Bender
wrote:<br>
</div>
<blockquote
cite="mid:CADf7C8sEBi_p1ZTUhJW-K9vuACHjY20Qc_PqbpEmr7W8+n1Cbw@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Apr 13, 2017 at 2:36 AM, Tony
Anderson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:tony@olenepal.org" target="_blank">tony@olenepal.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,
Walter<br>
<br>
My statisitics for github links in <a
moz-do-not-send="true" href="http://activity.info"
rel="noreferrer" target="_blank">activity.info</a> is 9
of 632 (3 of those to those to the Sugarlabs githbub).
Starting from the other end, there<br>
are 137 activities in the SugarLabs github. Unfortunately
there is no release information in GitHub so it is
impossible to know whether the<br>
version in GitHub corresponds to the current version in
ASLO. Of these 60 did not work in Ubuntu Sugar (but I may
have tested an earlier version and the problem found has
been fixed.). There are, of course, discrepancies. For
example, there is a tamtam repository but I have no way to
know how that relates to the four TamTam activities.
MusicBlocks has a repository but is not in ASLO. However,
TurtleBlocks does not (apparently you have a private one).<br>
<br>
My plan is to focus testing on these 137 activities (this
excludes the core eight which I consider a part of Sugar).<br>
</blockquote>
<div><br>
</div>
<div>I think we need to formalize a process for updates now
that many activities are hosted from the Sugar Labs team
as opposed to individual maintainers. I know that I have
lost track of many of the activities I wrote/maintained
since the transition (in part because I seem to get very
spotting notifications from GitHub about PRs, issues,
etc.)</div>
<div><br>
</div>
<div>Re Turtle, the Python version(s) are in ASLO. I don't
recall ever putting the JS version there since it was
somewhat redundant; Music Blocks has not been packaged for
ASLO, in part because the synth was not working with the
Browse activity. That may be resolved on recent versions
of Browse. I will have to test.</div>
<div><br>
</div>
<div>I am still confused and put off by the process of
adding Apps to Sugarizer and have no idea if Lionel plans
to incorporate ASLO or maintain his own repositories -- my
impression is that one installs Sugarizer and all Apps in
one package and new Apps only come in when the entire
package is updated.</div>
<div><br>
</div>
<div>-walter</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Tony<br>
<br>
<br>
On 04/13/2017 08:21 AM, <a moz-do-not-send="true"
href="mailto:aslo-request@lists.sugarlabs.org"
target="_blank">aslo-request@lists.sugarlabs.o<wbr>rg</a>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Message: 1<br>
Date: Thu, 13 Apr 2017 08:21:31 +0800<br>
From: Tony Anderson<<a moz-do-not-send="true"
href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a><wbr>><br>
To: Walter Bender<<a moz-do-not-send="true"
href="mailto:walter.bender@gmail.com" target="_blank">walter.bender@gmail.com</a><wbr>>,
Jatin Dhankhar<br>
<<a moz-do-not-send="true"
href="mailto:dhankhar.jatin@gmail.com" target="_blank">dhankhar.jatin@gmail.com</a>><br>
Cc:"<a moz-do-not-send="true"
href="mailto:aslo@lists.sugarlabs.org" target="_blank">aslo@lists.sugarlabs.org</a>"
<<a moz-do-not-send="true"
href="mailto:aslo@lists.sugarlabs.org" target="_blank">aslo@lists.sugarlabs.org</a>>,
Samuel<br>
Cantero<<a moz-do-not-send="true"
href="mailto:scanterog@gmail.com" target="_blank">scanterog@gmail.com</a>><br>
Subject: [ASLO] !<br>
Message-ID:<<a moz-do-not-send="true"
href="mailto:58EEC48B.4070204@usa.net" target="_blank">58EEC48B.4070204@u<wbr>sa.net</a>><br>
Content-Type: text/plain; charset="utf-8";
Format="flowed"<br>
<br>
Great!<br>
<br>
Tony<br>
<br>
On 04/13/2017 01:40 AM, Walter Bender wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
>Let's try to get Sam C., who currently maintains
ASLO into the loop. I<br>
>think he'll have lots of good advice for us.<br>
><br>
>regards.<br>
><br>
</blockquote>
</blockquote>
<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 moz-do-not-send="true"
href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br>
<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>