[edit] Overall goals

"Keep them clean, secure and lean!"

[edit] What are Screenlets-extras?

The individual screenlets

[edit] Coding

[edit] Keeping it secure, private

1. Screenlets shall not include code that makes a system less secure, e.g: No screenlets should ever need admin privileges to run
2. Screenlets shall not include code that exposes the private matters of a user, without EXPLICITLY warning the user that this will happen

[edit] Coding style

1. All screenlets will have to include the proper (C) info. If they fail to do so, they will NOT be included in the package
2. All images must have proper (C) info
3. All screenlets must have the shortened version of the license at the top of every .py file

example:

# This application is released under the GNU General Public License 
# v3 (or, at your option, any later version). You can find the full 
# text of the license under http://www.gnu.org/licenses/gpl.txt. 
# By using, editing and/or distributing this software you agree to 
# the terms and conditions of this license. 
# Thank you for using free software!

# GmailScreenlet (c) 2007 Whise <helder.fraga@hotmail.com>

[edit] Keeping your own branch

Developers are encouraged to keep their own branches on Launchpad. That way, they can:

1. have their own testbed
2. keep their stuff collected for users to download specific screenlets, in stead of installing the whole package
3. still get bug reports
4. get all the goodness that revision control systems provide

After the work is considered partly stable it can go into the 3rd-party-screenlets trunk, editions can be made by other developers, and the screenlet continually improved.

When the development branch reaches maturity, a release will be made. Development will continue on trunk.

[edit] Breaking the rules

Deliberate violation of these guidelines, should they be serious enough, could result in immediate expulsion from the project Screenlets-extras.