Line 1: |
Line 1: |
| + | {{Graduate|Walterbender will move this to http://developer.sugarlabs.org in 2016}} |
| + | |
| <noinclude><div class="noprint">{{TeamHeader|Activity Team}}</div></noinclude> | | <noinclude><div class="noprint">{{TeamHeader|Activity Team}}</div></noinclude> |
| | | |
Line 136: |
Line 138: |
| == Testers == | | == Testers == |
| | | |
− | Please see the [[Features/Soas_V4/ASLOxo_Activity_Test_Table|Activity Test-table page]] for tester information. | + | Please see the [[Testing/Activity Test Table]] for tester information. |
| | | |
| == Background information == | | == Background information == |
Line 218: |
Line 220: |
| === A typical update cycle === | | === A typical update cycle === |
| | | |
− | Anyone can contribute a patch to a Sugar Activity. The typical work cycle involves an interaction with the activity (project) maintainer as follows:
| + | Moved to https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#modifying-activities |
− | # make a clone (anyone)
| |
− | # make your changes (anyone)
| |
− | # mail your patch to sugar_devel (anyone)
| |
− | # make changes as per suggestions by the project maintainer and developer community (anyone)
| |
− | # push your changes (anyone)
| |
− | # request a merge (anyone)
| |
− | # write release notes (anyone)
| |
− | # tag the new version in git (project maintainer)
| |
− | # create the .xo and .tar files (project maintainer)
| |
− | # upload .tar to download.sugarlabs.org (project maintainer)
| |
− | # upload .xo to activities.sugarlabs.org (project maintainer) | |
− | # update wiki documentation (anyone)
| |
| | | |
| === OLPC XO game buttons === | | === OLPC XO game buttons === |