Changes

Jump to: navigation, search

Features/Policy

631 bytes added, 12:16, 30 November 2009
Why does this process matter or why should I care?: clarifications
= Why does this process matter or why should I care? =
The main goal of the feature process policy is to phrase out systematize the process by which community ideas on how Sugar should evolve that are floating around in the communityget transformed into actionable proposals. These can 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 described in a [[Features/Feature_Template|wiki page ]] (following the process described in detail below) and a maintainer is found who will be working work on this featurethe 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. The In either case, work on that feature new features will be [http://bugs.sugarlabs.org tracked during ] and, in the cycle and case of platform features, if finished in time it , they will find it's 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 In the case of features impacting the Sugar platform itself, the person responsible for managing the release, the is our community-designated 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 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? =

Navigation menu