607
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − The [[ReleaseTeam|release team]] role is to help the community to reach a consensus on which features, modules and activities to include.+ − === New activities ===+ + + + + + + + + + Line 17:
Line 26: − − Informations to provide when proposing a new activity: − − * Short description of the features. − * Screenshots or screencasts. − * Are you willing to follow the [[Roadmap#Schedule|Schedule]]? − * System components the activity depends on. − * Members of the developer team. − * Status of internationalization. − * Code repository. − * Bug tracking system.
→New features proposal
== New features proposal ==
== New features proposal ==
At the beginning of each release cycle, maintainers will write a proposal for each major new feature they plan to develop. These will be discussed on the Sugar mailing list, revised on the base of the feedback and made available on the wiki.
At the beginning of each release cycle, maintainers will write a proposal for each major new feature they plan to develop. The [[ReleaseTeam|release team]] role is to help the community to reach a consensus on which features, modules and activities to include.
=== New activities ===
To propose a new activity send mail to the [http://lists.laptop.org/listinfo/sugar sugar mailing list], providing the following informations:
* Short description of the features.
* Screenshots or screencasts.
* Are you willing to follow the [[Roadmap#Schedule|Schedule]]?
* System components the activity depends on.
* Members of the developer team.
* Status of internationalization.
* Code repository.
* Bug tracking system.
Criteria for approval will be:
Criteria for approval will be:
* Use the sugarlabs infrastructure.
* Use the sugarlabs infrastructure.
== Module release ==
== Module release ==