Activity Team/Getting Involved: Difference between revisions

Garycmartin (talk | contribs)
No edit summary
Line 9: Line 9:
As an activity developer in most cases you need only [[Taxonomy#Glucose:_The_base_Sugar_environment|glucose]] module(its included to ''sugar-glucose'' or ''sugar'' packages).
As an activity developer in most cases you need only [[Taxonomy#Glucose:_The_base_Sugar_environment|glucose]] module(its included to ''sugar-glucose'' or ''sugar'' packages).


Place your activity to ~/Activities/'''activity-name'''.activity directory.
== If you want to create your own activity ==


To test your activity in sugar environment:
What you need to do to create or share your activity.
* use ''sugar'' command to run sugar as a regular window manager
 
* use ''sugar-emulator'' command to run sugar in window mode(in Xephyr), could be useful to test your activity in current environment without re-loginning.
==== Start coding ====
 
* '''Create''' an account on http://git.sugarlabs.org and '''log in'''. Add your public SSH key to [http://git.sugarlabs.org/account your account].
* '''Create a new project''' (http://git.sugarlabs.org, projects, new). Make your project name lowercase, e.g. pippy, turtleart, paint. Put it in '''category "activities"'''.
* [[Activity_Team/Git_FAQ#How_do_I_create_a_new_project.3F|Initiate]] your project
* Use can copy/paste [http://git.sugarlabs.org/projects/hello-world Hello World] activity to get an example of usual files hierarchy.
* You can place your activity to ~/Activities/'''activity-name'''.activity directory.<br>To test your activity in sugar environment:
** use ''sugar'' command to run sugar as a regular window manager
** use ''sugar-emulator'' command to run sugar in window mode(in Xephyr), could be useful to test your activity in current environment without re-loginning.
* '''Start''' coding :)
 
==== Share your activity ====
 
If you want to share your activity for broad audience(it could be not final release):
 
* Open a ticket on [http://dev.sugarlabs.org dev.sugarlabs.org] to create component for your activity e.g. [http://dev.sugarlabs.org/ticket/788]
* Using ''setup.py'' from activity root directory, create .pot file
* '''Add''' the pootle user as a committer (from the "add committer" link on the mainline page) and send mail to [[User:SayaminduDasgupta|Sayamindu]] to point [http://translate.sugarlabs.org/ pootle](sugar translation environment) to new remote.
* Open a ticket on [http://dev.sugarlabs.org dev.sugarlabs.org] to add your activity to [http://translate.sugarlabs.org/ pootle] e.g. [http://dev.sugarlabs.org/ticket/810]
* '''Upload a xo bundle'''(use ''setup.py'' to create bundle) to [http://addons.sugarlabs.org/ addons.sugarlabs.org].
** Be sure to include a couple of screenshots of your activity in action.
** [[Activity_Library/Glossary#Public_activity|Nominate]] your activity to the public


==Join the Activity Team==
==Join the Activity Team==
Line 27: Line 48:
If you are an independent developer who is interested in working on a Sugar activity, please introduce yourself and your project in an email to sugar-devel@lists.sugarlabs.org.
If you are an independent developer who is interested in working on a Sugar activity, please introduce yourself and your project in an email to sugar-devel@lists.sugarlabs.org.


==Quick Start==
==Help the Activity Team==
 
If you'd rather just start coding '''right now''', it's easy to do!   
If you'd rather just start coding '''right now''', it's easy to do!