Jump to: navigation, search


761 bytes removed, 06:30, 4 December 2009
Why does this process matter or why should I care?
The main goal of the feature policy is to make systematic and predictable the process by which community ideas on how Sugar should evolve get transformed into actionable proposals. These ideas—new features—can be requests from the field or individual propositions on how to enhance the Sugar learning platform. '''Note:''' bugs are not features. We use the [ bug tracker] to report and monitor bugs.
Once Furthermore this process describes the idea is described in steps a [[Features/Feature_Template|wiki page]] (following the process described in detail below) and a developer is found who will work on Feature owner needs to fulfill to propose the idea, it can be proposed Feature to be part of a Sucrose release cycle (in the case of platform features) 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 (where modules are referred to as "components" and features are referred to as "enhancements") and, include it in the case of platform features, if finished in time, they will find their way in the a 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]
=== Who is responsible for this process? ===

Navigation menu