5,705
edits
Changes
Jump to navigation
Jump to search
Line 12:
Line 12: − − − − − − − −
→Agenda
====Agenda====
====Agenda====
*Adopt activities.sugarlabs.org
*Adopt activities.sugarlabs.org
** Ask permission of activity authors to allow AT members to make releases.
** 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
*** 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
*** Renovate idea of ActivityTeam Stamp of Approval and take care of these activities
*** Renovate 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]]
*** [[ActivityTeam#.22Activity_Team.22_user_on_addons.sugarlabs.org|"Activity Team" user on aslo]]
*** Create a special activityteam user on Gitorious?
*** 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)
**** 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)
**** 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)
** [http://sugarlabs.org/wiki/index.php?title=User:Tomeu/Platform_0.84 Sugar Platform]
** [http://sugarlabs.org/wiki/index.php?title=User:Tomeu/Platform_0.84 Sugar Platform]
*** Use SoaS as a test platform for aslo activities(treat soas like a model of "Standard Sugar Platform")
*** Use SoaS as a test platform for aslo activities(treat soas like a model of "Standard Sugar Platform")
*** Blobs in activities on aslo
*** Blobs in activities on aslo
**** some blobs could be included to Sugar Platform
**** some blobs could be included to Sugar Platform
**** what to do with the others
**** 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)?
***** 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)?
***** add architecture to aslo platforms?
***** add architecture to aslo platforms?
****** 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.)?
****** 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.)?
** aslo internals
** aslo internals
*** Form editors/admins groups to support aslo's activities
*** Form editors/admins groups to support aslo's activities