3,267
edits
Changes
→Why does this process matter or why should I care?
== Why does this process matter or why should I care? ==
== 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 [http://bugs.sugarlabs.org bug tracker] to report and monitor bugs.
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.
Furthermore this process describes the steps a Feature owner needs to fulfill to propose the Feature to be part of a Sucrose release cycle and to include it in a Sucrose release. We are currently in discussions on how this process can be used by activities, too. As Activities are not part of Sucrose (the Sugar platform), they do not need to follow the release cycle. Stay tuned on updates to this process regarding activities.
=== Who is responsible for this process? ===
=== Who is responsible for this process? ===