Re: [Sugar-devel] FW: scratch on aslo

2011-12-19 Thread Bert Freudenberg

On 17.12.2011, at 11:39, Bernie Innocenti wrote:

 On Sat, 2011-12-17 at 00:11 -0500, Samuel Klein wrote:
 I understand why Scratch isn't hosted on aslo at present, but it would
 be nice if it were hosted in a fashion that supported discovery of and
 review/discussion of it.  Scratch is Sugar's most popular programming
 activity, after all... 
 
 A few months ago it sounded like the Media Lab was going to correct the
 binary license of Scratch. Has anyone heard back from them?
 
 Cc'ing Mako and Claudia who might know the right person to ask.



https://lists.launchpad.net/scratch/msg00301.html

- Bert -


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-17 Thread Bernie Innocenti
On Sat, 2011-12-17 at 00:11 -0500, Samuel Klein wrote:
 I understand why Scratch isn't hosted on aslo at present, but it would
 be nice if it were hosted in a fashion that supported discovery of and
 review/discussion of it.  Scratch is Sugar's most popular programming
 activity, after all... 

A few months ago it sounded like the Media Lab was going to correct the
binary license of Scratch. Has anyone heard back from them?

Cc'ing Mako and Claudia who might know the right person to ask.

-- 
Bernie Innocenti
Sugar Labs Infrastructure Team
http://wiki.sugarlabs.org/go/Infrastructure_Team

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-16 Thread Samuel Klein
I understand why Scratch isn't hosted on aslo at present, but it would be
nice if it were hosted in a fashion that supported discovery of and
review/discussion of it.  Scratch is Sugar's most popular programming
activity, after all...


On Thu, Dec 15, 2011 at 7:09 PM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

 **


 http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table#Activity_Test_Results

 This is a table matrix on the wiki in a sortable and editable form.
 It is also unmaintained since Nov 2010...: (


+1 for better organization of things that take dedicated, periodic
investments of time.

But simply allowing people to build a catalog of all activities that have
ever been useful to anyone takes minimal effort (mainly, a one-time
simplification of the current submission process).

SJ
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-15 Thread Sebastian Silva
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
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-15 Thread Gonzalo Odiard
But I don't think is a good idea add a activity without a maintainer.

Gonzalo

On Thu, Dec 15, 2011 at 2:32 PM, Sebastian Silva
sebast...@somosazucar.orgwrote:

  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 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 
 listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel



 ___
 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


Re: [Sugar-devel] FW: scratch on aslo

2011-12-15 Thread Gary Martin
On 15 Dec 2011, at 17:44, Gonzalo Odiard 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 
 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 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
 http://lists.sugarlabs.org/listinfo/sugar-devel
 
 
 ___
 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
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-15 Thread Samuel Klein
I would find ASLO more useful if it had a Search all feature that allowed
people to find
* unmaintained or dormantly-maintained but working activities
* 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.comwrote:

 On 15 Dec 2011, at 17:44, Gonzalo Odiard 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 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 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 
 listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel



 ___
 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


 ___
 Sugar-devel mailing list
 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


Re: [Sugar-devel] FW: scratch on aslo

2011-12-15 Thread Alan Jhonn Aguiar Schwyn

I would find ASLO more useful if it had a Search all feature that allowed 
people to find
* unmaintained or dormantly-maintained but working activities
* 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.


Yes.. it can be more useful.. +1  ___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-15 Thread Gary Martin
On 15 Dec 2011, at 21:55, Samuel Klein 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 
 wrote:
 On 15 Dec 2011, at 17:44, Gonzalo Odiard 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 
 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 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
 http://lists.sugarlabs.org/listinfo/sugar-devel
 
 
 ___
 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
 
 ___
 Sugar-devel mailing list
 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


Re: [Sugar-devel] FW: scratch on aslo

2011-12-15 Thread Thomas C Gilliard

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

Re: [Sugar-devel] FW: scratch on aslo

2011-12-15 Thread Sebastian Silva

El 15/12/11 18:24, Alan Jhonn Aguiar Schwyn escribió:
I would find ASLO more useful if it had a Search all feature that 
allowed people to find

* unmaintained or dormantly-maintained but working activities
* 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.


Yes.. it can be more useful.. +1

+1

Here's the ASLO development information:

http://wiki.sugarlabs.org/go/Activity_Library/Devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-14 Thread Rafael Ortiz
On Wed, Dec 14, 2011 at 7:24 PM, Alan Jhonn Aguiar Schwyn 
alan...@hotmail.com wrote:

  Hi,

 Scratch there are in:
 http://activities.sugarlabs.org/es-ES/sugar/addon/4249

 But was removed: http://download.sugarlabs.org/activities/4249/

 Was removed for a discussion about his License..

 There are some activities that not are in ASLO..

 For example, all the activities that was in:
 http://wiki.laptop.org/index.php?title=Activities/All/lang-esoldid=262569

 That activities, can be uploaded to ASLO? Some not have now a maintener..
 but some works..


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

Regards!

 Alan

 --
 Date: Wed, 14 Dec 2011 19:04:34 -0500
 From: meta...@gmail.com
 To: sugar-devel@lists.sugarlabs.org
 Subject: [Sugar-devel] scratch on aslo


 Scratch doesn't seem to be on ASLO.  On the other hand, when I sign in and
 try to upload it, I am told the file is already in the system.   Can
 someone link me to it?

 It is ***really hard*** to find the link to upload an activity.  Can this
 be added in a few more places?  If you don't think to hover over nav
 elements I don't think there is any other way to discover it.
 http://activities.sugarlabs.org/en-US/developers/addon/submit

 It is unclear how to submit someone else's activity for inclusion.  There
 are some popular activities not in aslo, particularly spanish-language ones
 (cf. xojuegos.com); this would be a nice feature, even if the resulting
 work gets an unverified copyright stamp.

 SJ

 ___ 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


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-14 Thread Alan Jhonn Aguiar Schwyn

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

  ___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-14 Thread Gonzalo Odiard
On Wed, Dec 14, 2011 at 9:24 PM, Alan Jhonn Aguiar Schwyn 
alan...@hotmail.com wrote:

  Hi,

 Scratch there are in:
 http://activities.sugarlabs.org/es-ES/sugar/addon/4249

 But was removed: http://download.sugarlabs.org/activities/4249/

 Was removed for a discussion about his License..


Yes. Then we have the last packaged activity here
http://wiki.laptop.org/go/Scratch




 There are some activities that not are in ASLO..

 For example, all the activities that was in:
 http://wiki.laptop.org/index.php?title=Activities/All/lang-esoldid=262569

 That activities, can be uploaded to ASLO? Some not have now a maintener..
 but some works..


Most of these activities are in aslo, and other are unmaintained and
probably don't work.
If you have any good activity outside of aslo, should contact to the
maintainer and request inclusion.

Gonzalo




 Regards!

 Alan

 --
 Date: Wed, 14 Dec 2011 19:04:34 -0500
 From: meta...@gmail.com
 To: sugar-devel@lists.sugarlabs.org
 Subject: [Sugar-devel] scratch on aslo


 Scratch doesn't seem to be on ASLO.  On the other hand, when I sign in and
 try to upload it, I am told the file is already in the system.   Can
 someone link me to it?

 It is ***really hard*** to find the link to upload an activity.  Can this
 be added in a few more places?  If you don't think to hover over nav
 elements I don't think there is any other way to discover it.
 http://activities.sugarlabs.org/en-US/developers/addon/submit

 It is unclear how to submit someone else's activity for inclusion.  There
 are some popular activities not in aslo, particularly spanish-language ones
 (cf. xojuegos.com); this would be a nice feature, even if the resulting
 work gets an unverified copyright stamp.

 SJ

 ___ 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


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-14 Thread Alan Jhonn Aguiar Schwyn

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 ..___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] FW: scratch on aslo

2011-12-14 Thread Rafael Ortiz
On Wed, Dec 14, 2011 at 7:42 PM, Alan Jhonn Aguiar Schwyn 
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
http://lists.sugarlabs.org/listinfo/sugar-devel