10,505
edits
Changes
→Who is responsible for this process?
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].
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].
=== Roles ===
In addition to the Release Manager, there are four other distinct roles in the new-feature process: the proposer of the idea; the developer of the idea; the maintainer of the relevant module and the Sugar community.
* The proposer (or "owner") of the idea is the one that proposes the feature and completes the new feature proposal as described below;
* The developer of the idea is the one that implements the idea and, where applicable, follows the process to include it in a release;
* The maintainer of the module is the one that reviews any code that needs to be merged for a feature; and
* The community provides feedback throughout the process, but especially at the stage where by we decide which new-feature proposals to pursue.
As noted above, the Release Manager is the one that sets and enforce the policy for features, including setting dates, formalizing processes, etc.
= What is a feature? =
= What is a feature? =