Jump to content

Activity Team/Creating a New Activity: Difference between revisions

From Sugar Labs
Dfarning (talk | contribs)
m create page
 
Dfarning (talk | contribs)
m Add outline
Line 1: Line 1:
stub
For new Activities:
    Create a Gitorious project repository at http://git.sugarlabs.org/ and start hacking on your code! :-)
    Request a trac component for your activity at http://dev.sugarlabs.org/
    Open a trac ticket to request addition to Pootle our translation system (if your strings are mature)
    Add your Activity to http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap if you want to be on the SoaS distro
 
If your Activity is migrating over from the OLPC infrastructure:
    See How to migrate from OLPC.
 
When releasing an existing Activity:
    If you have one, update your wiki page at http://wiki.sugarlabs.org/go/Activities/<actvity-name>
    Upload your new .xo bundle, screenshots, notes to http://activities.sugarlabs.org/
    Upload .bz2 source to shell.sugarlabs.org /upload/sugar/sources/honey
    Edit http://wiki.sugarlabs.org/go/Development_Team/Source_Code and make sure it's pointing to your latest .bz2

Revision as of 15:13, 30 August 2009

For new Activities:

   Create a Gitorious project repository at http://git.sugarlabs.org/ and start hacking on your code! :-) 
   Request a trac component for your activity at http://dev.sugarlabs.org/ 
   Open a trac ticket to request addition to Pootle our translation system (if your strings are mature) 
   Add your Activity to http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap if you want to be on the SoaS distro 

If your Activity is migrating over from the OLPC infrastructure:

   See How to migrate from OLPC. 

When releasing an existing Activity:

   If you have one, update your wiki page at http://wiki.sugarlabs.org/go/Activities/<actvity-name> 
   Upload your new .xo bundle, screenshots, notes to http://activities.sugarlabs.org/ 
   Upload .bz2 source to shell.sugarlabs.org /upload/sugar/sources/honey 
   Edit http://wiki.sugarlabs.org/go/Development_Team/Source_Code and make sure it's pointing to your latest .bz2