Changes

===Friday March 13th 2009 - 17:00 UTC===

===Friday March 13th 2009 - 17:00 UTC===

====Agenda====

====Agenda====

*Adopt activities.sugarlabs.org  

* activities.sugarlabs.org

** Ask permission of activity authors to allow AT members to make releases.

*** the major concern is: w/o that we have less accessible/uptodate activities on aslo in comparing with soas, since packaging "trunk" activities for distros is a common practice, and in common, GNU/Linux distribution is separated from upstream in comparing with addons.mozilla.org (IMHO) which is more like an exhibition of authors' activities

** Ask permission of activity authors to allow AT members to make releases. Without the ability of AT members to make releases, we will have fewer working & up to date activities on ASLO compared with distributions like SoaS (since it's common for distributions to package "trunk" activities).  It's in everyone's interest to have the activities on ASLO be as up to date as possible.

*** Renovate idea of ActivityTeam Stamp of Approval and take care of these activities

** Reintroduce idea of ActivityTeam Stamp of Approval and take care of these activities.

*** [[ActivityTeam#.22Activity_Team.22_user_on_addons.sugarlabs.org|"Activity Team" user on aslo]]

*** Create a special activityteam user on Gitorious?

**** we shouldn't confuse activities authors by intervening to development process [[User:Alsroot|alsroot]] 18:44, 9 March 2009 (UTC)

 

**** common(RO to trunk, but fork/merge) access and ask authors only for releasing permissions - incrementing versions(do not confuse users), releasing(maybe) from cloned repos [[User:Alsroot|alsroot]] 18:44, 9 March 2009 (UTC)

* ActivityTeam adoption of orphaned activities.

** [http://sugarlabs.org/wiki/index.php?title=User:Tomeu/Platform_0.84 Sugar Platform]

** An [[ActivityTeam#.22Activity_Team.22_user_on_addons.sugarlabs.org|"Activity Team"]] user now exists on ASLO so that we can post activities to ASLO without creating a user account for a possibly unreachable author.

*** Use SoaS as a test platform for aslo activities(treat soas like a model of "Standard Sugar Platform")

** We are considering also creating an activityteam user on Gitorious, which authors could give commit permission to in order to allow new releases to be made.  This user could also be used when forking orphaned activities.

*** Blobs in activities on aslo

*** we shouldn't confuse activities authors by intervening to development process [[User:Alsroot|alsroot]] 18:44, 9 March 2009 (UTC)

**** some blobs could be included to Sugar Platform

*** common(RO to trunk, but fork/merge) access and ask authors only for releasing permissions - incrementing versions(do not confuse users), releasing(maybe) from cloned repos [[User:Alsroot|alsroot]] 18:44, 9 March 2009 (UTC)

**** what to do with the others

 

***** if these blobs are activity specific(like C-library in Bounce, not like gst-pluigns-espeak in Speak) oblige authors(we couldn't admit activities that are not runnable on declared platforms) take care about all possible variants on chosen platform(like x86/x86_64 on Linux platform)?

* [http://sugarlabs.org/wiki/index.php?title=User:Tomeu/Platform_0.84 The Sugar Platform]

***** add architecture to aslo platforms?

** Consdier adopting SoaS as the standard test platform for ASLO activities.  Assume that if SoaS works, other distributions will work as well.

****** how it will look like if a kid decided download activity from aslo and had to choose the right choice between Applications(0.82, 0.84), Platforms(Linux, BSD, Mac), Architectures(x86, x86_64, ppc, etc.)?

** Blobs in activities on ASLO.

*** Some of these blobs could be packaged and included in the Sugar Platform (gst-pluigns-espeak in Speak).

*** Others are truly activity specific (like C-libraries in Bounce and Colors). 

**** We can oblige authors (by not approving non-conforming activities) to provide a standard set of variants which we determine.  For example, x86/x64 for Linux.  Another possibility is included standardized build scripts in the XO bundles and making a compiler suite part of the Sugar platform.

**** Alternately, we can add architecture choices to the ASLO platform selection.

***** Might be too complicated for kids to pick correctly.

***** Also requires authors to release multiple .xo bundles and set up cross-compilation.

***** How it will look like if a kid decided download activity from aslo and had to choose the right choice between Applications(0.82, 0.84), Platforms(Linux, BSD, Mac), Architectures(x86, x86_64, ppc, etc.)?

===Friday Feburary 27 2009 - 12pm EST ===

===Friday Feburary 27 2009 - 12pm EST ===