Talk:Features/Policy

They can range from a new capability for a Sugar activity to a global change to the toolkit.

or as part of the on-going Sugar activity update process. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.) Work on new features will be tracked in the wiki and in bugs.sugarlabs.org (where modules are referred to as "components" and features are referred to as "enhancements") and, in the case of platform features, if finished in time, they will find their way in the Sucrose stable release (See 0.88/Roadmap for details of the current release cycle.)

Once the idea is described in a wiki page (following the process described in detail below) and a developer is found who will work on the idea, it can be proposed to be part of a Sucrose release cycle. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.) Work on new features will be tracked in the wiki and in bugs.sugarlabs.org (where modules are referred to as "components" and features are referred to as "enhancements") and, in the case of platform features, if finished in time, they will find their way in the Sucrose stable release (See 0.88/Roadmap for details of the current release cycle.)

Note: For more background on FOSS project development, please refer to Karl Fogel's Producing Open Source Software

Note: bugs are not features. We use the bug tracker to report and monitor bugs.

In the case of features impacting the Sugar platform itself, the person responsible for managing the release is our community-designated Release Manager. (The current Release Manager is Simon Schampijer.)

In the case of features impacting individual activities, the person responsible is the activity maintainer. The list of maintainers is available on the activity page in ASLO.