I tried to do this in :
http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table#Activity_Test_Results
The criteria are listed at the top of the page.
This is a table matrix on the wiki in a sortable and editable form.
It is also unmaintained since Nov 2010...: (
Thus newer activities and sugar versions are missing.
It would be nice if we could organize volunteers to do testing of
activities, and report them in this manner.
Tom Gilliard
satellit_ on #sugar IRC
On 12/15/2011 03:49 PM, Gary Martin wrote:
On 15 Dec 2011, at 21:55, Samuel Klein <s...@laptop.org
<mailto:s...@laptop.org>> wrote:
* unmaintained or dormantly-maintained but working activities
This one is quite a tough one, activities are distributed across a
seemingly grey continuum, from non-responding authors, to authors who
release in time with the Sugar release schedules.
The term 'working' also needs careful definition given the wide
variety of distros and hardware that Sugar can be run under (testing
platform usually at the discretion of the maintainer). This alone
would be quite a large matrix. With an Activity Team hat on, we should
focus on polishing and maintaining the core of the known quality
learning activities, to act as leading lights, and encouraging other
developers to follow where there time allows. The whole 'let a
thousand flowers bloom' metaphor unfortunately leads to the vast
majority being left to compost.
--Gary
* activities that can be freely distributed but are not [confirmed to
be] under a free-software license
* links to activities that are freely available online (somewhere)
but may not be freely distributable (from an aslo server)
Excluding or obfuscating popular activities only makes ASLO a less
handy service.
At any rate, at the point where the ASLO software says to an uploader
"that file already exists in our databsae" it should be able to show
that person the metadata related to the file: who has uploaded it,
why it is not visible, &c.
SJ
On Thu, Dec 15, 2011 at 3:47 PM, Gary Martin
<garycmar...@googlemail.com <mailto:garycmar...@googlemail.com>> wrote:
On 15 Dec 2011, at 17:44, Gonzalo Odiard <gonz...@laptop.org
<mailto:gonz...@laptop.org>> wrote:
But I don't think is a good idea add a activity without a
maintainer.
+1
Activities without maintainers seem like a spiral to the bottom
of the quality bucket - I'd personally not want to recommend the
ASLO site to a teacher if we were knowingly promoting and
uploading unmaintained activities. As an Open Source license
(required by ASLO) allows anyone to potentially pick up
maintenance, perhaps ASLO could be tweaked to hide all activities
without a confirmed, named, maintainer by default?
--Gary
Gonzalo
On Thu, Dec 15, 2011 at 2:32 PM, Sebastian Silva
<sebast...@somosazucar.org <mailto:sebast...@somosazucar.org>>
wrote:
Actually if the license permits it, there isnt a necessity
to await confirmation by original author, although it would
be nice to ask, IMHO
El 14/12/11 19:46, Rafael Ortiz escribió:
On Wed, Dec 14, 2011 at 7:42 PM, Alan Jhonn Aguiar Schwyn
<alan...@hotmail.com <mailto:alan...@hotmail.com>> wrote:
It's ok uploading those to aslo, if they have OSI
compliant Licences, pointing to original devs, also
if they provide a good sugar experience. More info
here:
http://wiki.sugarlabs.org/go/Activity_Library/Editors/Policy#Guidelines_for_accepting_an_activity
Ok. The "importants" are in ASLO.. maybe there are some
that not..
I could test some and upload them. But corresponds me
to do that? I do not want to override the original
developers ..
it's necessary to ask first the original devs.
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
<mailto:Sugar-devel@lists.sugarlabs.org>
http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
<mailto:Sugar-devel@lists.sugarlabs.org>
http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
<mailto:Sugar-devel@lists.sugarlabs.org>
http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
<mailto:Sugar-devel@lists.sugarlabs.org>
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Samuel Klein identi.ca:sj w:user:sj +1
617 529 4266
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
