10,579
edits
Changes
Jump to navigation
Jump to search
Line 17:
Line 17: − + − + − + − + − + +
→Roles
=== Roles ===
=== 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.
In addition to the Release Manager, there are five 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 owner may want to follow the development and provide feedback throughout the process;
* the proposer (or "owner") of the idea is the one that proposes the feature and completes the new feature proposal as described below. The owner may want to follow the development and provide feedback throughout the process;
* 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 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 maintainer of the module is the one that reviews any code that needs to be merged for a feature;
* The community provides feedback throughout the process, but especially at the stage where by we decide which new-feature proposals to pursue.
* the design team is responsible for ensuring the overall consistency and quality of the Sugar experience; They will provide feedback during the process; 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.
As noted above, the Release Manager is the one that sets and enforce the policy for features, including setting dates, formalizing processes, etc.