Difference between revisions of "Talk:Features/Policy"
| Line 1: | Line 1: | ||
| + | = Activity Process for Activities = | ||
| + | == Propose a Feature == | ||
| + | The Feature can be proposed the same way than any other Feature. | ||
| + | |||
| + | == Propose a Feature into an activity == | ||
| + | As with the Features for the | ||
| + | |||
| + | 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 [http://activities.sugarlabs.org ASLO]. | ||
| + | |||
| + | |||
They can range from a new capability for a Sugar activity to a global change to the toolkit. | They can range from a new capability for a Sugar activity to a global change to the toolkit. | ||
| Line 7: | Line 17: | ||
'''Note:''' For more background on FOSS project development, please refer to Karl Fogel's [http://producingoss.com/ Producing Open Source Software] | '''Note:''' For more background on FOSS project development, please refer to Karl Fogel's [http://producingoss.com/ Producing Open Source Software] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 06:53, 4 December 2009
Activity Process for Activities
Propose a Feature
The Feature can be proposed the same way than any other Feature.
Propose a Feature into an activity
As with the Features for the
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.
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