Activity Team/Packaging
From Sugar Labs
Contents |
Common issues
Publish source tarballs for each release
If your activity is part of Fructose you should just follow Module Release instructions.
- Generate a source tarball as follows. It will be placed inside the dist/ directory.
./setup.py dist_source
- Upload it on the web. If you need a server to upload it to, please open a ticket on http://bugs.sugarlabs.org, under the shell.sugarlabs.org component, to request a shell account. Remeber to attach your public ssh key. When you have access, create a directory under /upload/sources/honey for your activity and copy the tarball in it.
- Update the Honey table on the Source Code page with a link to the latest version. Feel free to add an entry if your activity is not yet listed.
Create a trac component for your activity
Packagers needs to be able to report problems about your activity. Please open a ticket on http://bugs.sugarlabs.org, under the trac component, to request creation of a component for your activity.
Check copyright and licensing
- Many translations lacks copyright and licensing info completely or they provide just a boilerplate.The package maintainer should edit the .pot file to replace these:
SOME DESCRIPTIVE TITLE THE PACKAGE'S COPYRIGHT HOLDER PACKAGE
When that is done, they should get in contact with each translator to make them adopt that improved boilerplate and themselves replace these:
FIRST AUTHOR <EMAIL@ADDRESS> YEAR
When doing above, it makes good sense to also tidy the gettext hints to have proper info too, but that is just nice-to-have for semi-automated processing, not crucial as the licensing problem.
