[ASLO] ASLO Digest, Vol 85, Issue 21

[Tony Anderson]

Hi Walter,

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.

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.

My remark on Turtle Blocks is that the source does not have a github 
repository under Sugar Labs.

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.

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.

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'.

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.

Tony

On 04/13/2017 09:44 PM, Walter Bender wrote:
>
>
> On Thu, Apr 13, 2017 at 2:36 AM, Tony Anderson <tony at olenepal.org 
> <mailto:tony at olenepal.org>> wrote:
>
>     Hi, Walter
>
>     My statisitics for github links in activity.info
>     <http://activity.info> is 9 of 632 (3 of those to those to the
>     Sugarlabs githbub). Starting from the other end, there
>     are 137 activities in the SugarLabs github. Unfortunately there is
>     no release information in GitHub so it is impossible to know
>     whether the
>     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).
>
>     My plan is to focus testing on these 137 activities (this excludes
>     the core eight which I consider a part of Sugar).
>
>
> 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.)
>
> 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.
>
> 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.
>
> -walter
>
>
>     Tony
>
>
>     On 04/13/2017 08:21 AM, aslo-request at lists.sugarlabs.org
>     <mailto:aslo-request at lists.sugarlabs.org> wrote:
>
>         Message: 1
>         Date: Thu, 13 Apr 2017 08:21:31 +0800
>         From: Tony Anderson<tony_anderson at usa.net
>         <mailto:tony_anderson at usa.net>>
>         To: Walter Bender<walter.bender at gmail.com
>         <mailto:walter.bender at gmail.com>>, Jatin Dhankhar
>                 <dhankhar.jatin at gmail.com
>         <mailto:dhankhar.jatin at gmail.com>>
>         Cc:"aslo at lists.sugarlabs.org
>         <mailto:aslo at lists.sugarlabs.org>" <aslo at lists.sugarlabs.org
>         <mailto:aslo at lists.sugarlabs.org>>, Samuel
>                 Cantero<scanterog at gmail.com <mailto:scanterog at gmail.com>>
>         Subject: [ASLO] !
>         Message-ID:<58EEC48B.4070204 at usa.net
>         <mailto:58EEC48B.4070204 at usa.net>>
>         Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
>         Great!
>
>         Tony
>
>         On 04/13/2017 01:40 AM, Walter Bender wrote:
>
>             >Let's try to get Sam C., who currently maintains ASLO
>             into the loop. I
>             >think he'll have lots of good advice for us.
>             >
>             >regards.
>             >
>
>
>
>
>
> -- 
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/aslo/attachments/20170414/33cb483d/attachment.html>