Activity Team/Creating a New Activity: Difference between revisions

No edit summary
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
== Developer documentation ==
== Documentation for activity authors ==
 
See [[Activity Team/Developer resources]].


See [[Activity Team/Resources]].


== Checklist for new activities ==
== Checklist for new activities ==


* Create a Gitorious project repository at http://git.sugarlabs.org/ and start hacking on your code! :-)  
* Create a GitHub project repository at http://github.com and start hacking on your code! :-)  
* Request a trac component for your activity at http://bugs.sugarlabs.org/  
* Request a trac component for your activity at http://bugs.sugarlabs.org/  
* Open a trac ticket to request addition to http://translate.sugarlabs.org/ (when your strings are mature)  
* Open a trac ticket to request addition to http://translate.sugarlabs.org/ (when your strings are mature)  
Line 12: Line 11:


* If your Activity is migrating over from the OLPC infrastructure, see: [[Activity_Team/How_to_migrate_from_OLPC|How to migrate from OLPC]].
* If your Activity is migrating over from the OLPC infrastructure, see: [[Activity_Team/How_to_migrate_from_OLPC|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/
* Unless your source code is already available through git, upload a .bz2 source tarball to shell.sugarlabs.org /upload/sugar/sources/honey (e.g., scp to download.sugarlabs.org:/srv/upload/sources/fructose/...)
* Edit http://wiki.sugarlabs.org/go/Development_Team/Source_Code and make sure it's pointing to your latest source tarball


== Before you write a new activity ==
== Before you write a new activity ==