Activity Team/Meetings: Difference between revisions

Line 12:

====Agenda====

*Adopt activities.sugarlabs.org

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

** 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

*** 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]]

*** Create a special activityteam user on Gitorious?

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

** Form editors/admins groups to support aslo's activities

Line 20:

Line 23:

*** some blobs could be included to Sugar Platform

*** what to do with the others

** Ask permission of activity authors to allow AT members to make releases. Create a special activityteam user on Gitorious?

*** 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

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

@@ Line 12: / Line 12: @@
 ====Agenda====
 *Adopt activities.sugarlabs.org
-** Renovate idea of ActivityTeam Stamp of Approval and take care of these activities
+** 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
+*** 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]]
+*** Create a special activityteam user on Gitorious?
 ** Use SoaS as a test platform for aslo activities(treat soas like a model of "Standard Sugar Platform")
 ** Form editors/admins groups to support aslo's activities
@@ Line 20: / Line 23: @@
 *** some blobs could be included to Sugar Platform
 *** what to do with the others
-** Ask permission of activity authors to allow AT members to make releases.  Create a special activityteam user on Gitorious?
-*** 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
 ===Friday Feburary 27 2009 - 12pm EST ===