On Sun, May 6, 2018 at 10:00 PM Tony Anderson <t...@olenepal.org> wrote:
> Hi, Walter > > Is there a link to a description of the proposed new server? I assume that > what you mean is that a new physical server will become host to ASLO. > Naturally, I am much more interested in the capabilities of the service > than the server. > I am referring to https://aslo3-devel.sugarlabs.org (I see James answered you while I was typing this.) > It is really hard for me to see any connection between activity.info and > an activity service (which supplies information about activities and > downloads the bundle on request).I assume these consistency tests are made > before a new activity version is released and is part of the process of > creating a github repository. > The database for ASLO3 is derived from the activity.info files. But those data need cleaning up. This is why we have not gone live with the new server. > The python script can use a loop on the list of bundles: > > for activity in activities: > > #use zipfile to read the activity.info file > > #count or test for any property > > #report (e.g. print ) result of test by activity > > #report summary of loop execution > > > I do not have any idea of what you are referring to by a screenshot. I > certainly hope there is no intent to add a screenshot to an activity > bundle. It may be fun to revel in storage available on a PC but the > overwhelming number of our users have XO laptops with very limited storage. > This is similar to the trend to make Sugar more dependent on the internet. > For example, sudo apt-get install sucrose is difficult to accomplish in a > room with 40 laptops and no internet, the current situation in Rwanda with > the Positivo laptop. > We use screenshots in the activity portal. They need not be included in the bundles. > > Tony > > On Monday, 07 May, 2018 09:35 AM, Walter Bender wrote: > > This particular discussion was about activity.info because the student is > working on getting the activity server on line and cleaning up the > activity.info files is an essential step. > >> I interpret https://github.com/sugar-activities as an attempt to provide >> a separate place for Sugar activity repositories based on >> download.sugarlabs.org/activities. The number of activities mentioned is >> consistent with the current content of ASLO. (see >> http://activities.sugarlabs.org/activities/) >> > > Yes. We have an on-going effort to migrate to a new activity server which > is both easier to maintain and a richer experience for our users. > >> A simple python script can process the activity.info in activity bundles >> very quickly. Simply download every activity bundle and then use import >> zipfile to read the activity.info file and check it for whatever is >> interesting. I generally use ls -1 *.xo > list to create a file. The python >> script can easily form a list of activities from this file. >> > > We are concerned about a number of inconsistencies with the data, > including license, summary, screen shots, etc. > > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Walter Bender Sugar Labs http://www.sugarlabs.org <http://www.sugarlabs.org>
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel