273
edits
Changes
New page: <noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show...
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}
{{TeamHeader|ActivityTeam}}</noinclude>
When you plan to take a task from the list, please sign and date it using four tildes
<pre>˜˜˜˜</pre>
When a task is complete, strike it out using
<pre><strike>task</strike></pre>
==Community==
* Announce availability of ATeam contacts page to mailing lists. [[User:Wade|Wade]] 17:26, 12 January 2009 (UTC)
* Query ATeam members about skills, interest, time commitment. [[User:Wade|Wade]] 17:26, 12 January 2009 (UTC)
* Look for at least one additional coordinator.
* Contact former + current activity developers. [[User:Wade|Wade]] 17:26, 12 January 2009 (UTC)
** Ask about moving activities to git.sugarlabs.org (or mirroring).
** Ask about joining the ActivityTeam or coming to meetings.
==Infrastructure==
* Make activities.sugarlabs.org (or addons.sugarlabs.org) work.
* Bug IT to get us admin accounts for SL services.
** Downloads
** Trac (component creation etc)
* Ask IT about activity repository mirroring. A read-only Git repository on SL which automatically pulls from a remote repository.
* Flesh out structure for ActivityTeam wiki.
** Where does the Activities list from the SL home page go?
** How should development information be structured?
** In the (temporary) absence of activities.sugarlabs.org, should we create per-activity Wiki pages? Should we anyway?
==Development==
* Move projects owned by ATeam members over to git.sugarlabs.org and downloads.sugarlabs.org.
* Help SoaS and distro packagers to get as many activities as possible working on plain Sugar (outside the XO software environment).
* Build a list of "Rescue" activities: Ones which have not been worked on in a while but are close to being usable.
* Build a list of "Help Wanted" activities: Great ideas or existing projects which need to be sugarized.
* Generate spec for Web, SWF activities and deliver to DevelopmentTeam.
{{TeamHeader|ActivityTeam}}</noinclude>
When you plan to take a task from the list, please sign and date it using four tildes
<pre>˜˜˜˜</pre>
When a task is complete, strike it out using
<pre><strike>task</strike></pre>
==Community==
* Announce availability of ATeam contacts page to mailing lists. [[User:Wade|Wade]] 17:26, 12 January 2009 (UTC)
* Query ATeam members about skills, interest, time commitment. [[User:Wade|Wade]] 17:26, 12 January 2009 (UTC)
* Look for at least one additional coordinator.
* Contact former + current activity developers. [[User:Wade|Wade]] 17:26, 12 January 2009 (UTC)
** Ask about moving activities to git.sugarlabs.org (or mirroring).
** Ask about joining the ActivityTeam or coming to meetings.
==Infrastructure==
* Make activities.sugarlabs.org (or addons.sugarlabs.org) work.
* Bug IT to get us admin accounts for SL services.
** Downloads
** Trac (component creation etc)
* Ask IT about activity repository mirroring. A read-only Git repository on SL which automatically pulls from a remote repository.
* Flesh out structure for ActivityTeam wiki.
** Where does the Activities list from the SL home page go?
** How should development information be structured?
** In the (temporary) absence of activities.sugarlabs.org, should we create per-activity Wiki pages? Should we anyway?
==Development==
* Move projects owned by ATeam members over to git.sugarlabs.org and downloads.sugarlabs.org.
* Help SoaS and distro packagers to get as many activities as possible working on plain Sugar (outside the XO software environment).
* Build a list of "Rescue" activities: Ones which have not been worked on in a while but are close to being usable.
* Build a list of "Help Wanted" activities: Great ideas or existing projects which need to be sugarized.
* Generate spec for Web, SWF activities and deliver to DevelopmentTeam.