Features/Policy: Difference between revisions

Line 4:

= Why does this process matter or why should I care? =

The main goal of the feature ~~process~~ is to ~~phrase out~~ the ideas on how Sugar should evolve ~~that are floating around in the community~~. These ~~can~~ be requests from the field or individual propositions on how to enhance the learning platform.

The main goal of the feature policy is to systematize 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. They can range from a small detail regarding a Sugar activity to a global change to the toolkit.

Once the idea is ~~written out~~ in a wiki page (following the process described in detail below) and a maintainer is found who will ~~be working~~ on ~~this feature~~, it can be proposed to be part of a Sucrose release cycle. ~~The~~ work on ~~that feature~~ will be tracked ~~during~~ the ~~cycle and~~ if finished in time it will find ~~it's~~ way in the Sucrose stable release.

Once the idea is described in a [[Features/Feature_Template|wiki page]] (following the process described in detail below) and a maintainer is found who will work on the idea, it can be proposed 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. In either case, work on new features will be [http://bugs.sugarlabs.org tracked] 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.

== Who is responsible for this process? ==

~~The~~ person responsible for managing the release~~, the~~ Release Manager~~, is designated by the community to fulfill the task~~. The current Release Manager is [http://wiki.sugarlabs.org/go/User:Erikos Simon Schampijer].

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 [http://wiki.sugarlabs.org/go/User:Erikos 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 [http://activities.sugarlabs.org|ASLO].

= What is a feature? =

@@ Line 4: / Line 4: @@
 = Why does this process matter or why should I care? =
-The main goal of the feature process is to phrase out the ideas on how Sugar should evolve that are floating around in the community. These can be requests from the field or individual propositions on how to enhance the learning platform.
+The main goal of the feature policy is to systematize 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. They can range from a small detail regarding a Sugar activity to a global change to the toolkit.
-Once the idea is written out in a wiki page (following the process described in detail below) and a maintainer is found who will be working on this feature, it can be proposed to be part of a Sucrose release cycle. The work on that feature will be tracked during the cycle and if finished in time it will find it's way in the Sucrose stable release.
+Once the idea is described in a [[Features/Feature_Template|wiki page]] (following the process described in detail below) and a maintainer is found who will work on the idea, it can be proposed 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. In either case, work on new features will be [http://bugs.sugarlabs.org tracked] 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.
 == Who is responsible for this process? ==
-The person responsible for managing the release, the Release Manager, is designated by the community to fulfill the task. The current Release Manager is [http://wiki.sugarlabs.org/go/User:Erikos Simon Schampijer].
+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 [http://wiki.sugarlabs.org/go/User:Erikos 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 [http://activities.sugarlabs.org|ASLO].
 = What is a feature? =