3,267
edits
Changes
Jump to navigation
Jump to search
Line 48:
Line 48: + + + + + + + + + + + + + + + + + + + + + + + +
→How do I propose a feature I'm going to help build or own?
== How do I propose a feature I'm going to help build or own? ==
== How do I propose a feature I'm going to help build or own? ==
In order to be considered an official feature accepted for the next Sugar release, the feature should be formally documented on a separate wiki page which includes the following information.
# Summary of the feature
# A designated owner with a link to Sugar home page. The owner is responsible for:
## making sure the feature is completed according to the schedule
## communicating periodic status
## attending feature status meetings
# Current status
## last updated
## estimated percentage of completion
# Description of the new feature
# Detailed explanation of what the new feature will do and how it will be implemented
# Benefit to Sugar
# Scope
# How To Test
# Dependencies--on other packages or features
# Contingency plan
# Link to documentation
# Important information for release notes
* Put a ''watch'' on your page so you are notified when its category changes. You must be logged in, then click the ''watch'' link at the top of the page.
* A blank template is available at [[Features/Feature_Template]]
== What does the feature form look like? ==
== What does the feature form look like? ==