Talk:Features/Policy - Revision history

Erikos: /* Propose a Feature into an activity */

2009-12-04T11:07:34Z

Propose a Feature into an activity

← Older revision		Revision as of 07:07, 4 December 2009
Line 7:		Line 7:

	* As activities are not part of the Sucrose do not have to follow the dates of the development cycle. The schedule for Feature inclusion is dependent on the maintainer of an activity. The merging of the Feature Code happens between the Feature Owner and the Activity Mainteiner, too.		* As activities are not part of the Sucrose do not have to follow the dates of the development cycle. The schedule for Feature inclusion is dependent on the maintainer of an activity. The merging of the Feature Code happens between the Feature Owner and the Activity Mainteiner, too.
	* The Activity Feature Process is handled by a designated activity team member. Like the Release Manager is responsible for the Sucrose Feature Process, the activity team member is responsible for managing the Activity Feature Process.		* The Activity Feature Process is handled by a designated activity team member. Like the Release Manager is responsible for the Sucrose Feature Process, the activity team member is responsible for managing the Activity Feature Process. (Another solution is to handle each Feature by the activity maintainer itself).

Erikos: /* Propose a Feature into an activity */

2009-12-04T11:05:34Z

Propose a Feature into an activity

← Older revision		Revision as of 07:05, 4 December 2009
Line 8:		Line 8:
	* As activities are not part of the Sucrose do not have to follow the dates of the development cycle. The schedule for Feature inclusion is dependent on the maintainer of an activity. The merging of the Feature Code happens between the Feature Owner and the Activity Mainteiner, too.		* As activities are not part of the Sucrose do not have to follow the dates of the development cycle. The schedule for Feature inclusion is dependent on the maintainer of an activity. The merging of the Feature Code happens between the Feature Owner and the Activity Mainteiner, too.
	* The Activity Feature Process is handled by a designated activity team member. Like the Release Manager is responsible for the Sucrose Feature Process, the activity team member is responsible for managing the Activity Feature Process.		* The Activity Feature Process is handled by a designated activity team member. Like the Release Manager is responsible for the Sucrose Feature Process, the activity team member is responsible for managing the Activity Feature Process.


	Once the idea is described in a [[Features/Feature_Template\|wiki page]] (following the process described in detail below) and a developer is found who will work on the idea, it can be proposed to be part of a Sucrose release cycle. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.) Work on new features will be tracked in the wiki and in bugs.sugarlabs.org (where modules are referred to as "components" and features are referred to as "enhancements") and, in the case of platform features, if finished in time, they will find their way in the Sucrose stable release (See [[0.88/Roadmap]] for details of the current release cycle.)

	~~'''Note:''' For more background on FOSS project development, please refer to Karl Fogel's [http://producingoss.com/ Producing Open Source Software]~~

Erikos at 11:04, 4 December 2009

2009-12-04T11:04:29Z

← Older revision		Revision as of 07:04, 4 December 2009
Line 4:		Line 4:

	== Propose a Feature into an activity ==		== Propose a Feature into an activity ==
	~~As with the Features~~ for ~~the~~		The Process for inclusion of an Activity Feature into an activity release is similar to that of a Feature for Sucrose. The Feature must have an owner, there must be community consensus etc. There are two main differences:

	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]~~.		* As activities are not part of the Sucrose do not have to follow the dates of the development cycle. The schedule for Feature inclusion is dependent on the maintainer of an activity. The merging of the Feature Code happens between the Feature Owner and the Activity Mainteiner, too.
			* The Activity Feature Process is handled by a designated activity team member. Like the Release Manager is responsible for the Sucrose Feature Process, the activity team member is responsible for managing the Activity Feature Process.

	~~They can range from~~ a ~~new capability for a Sugar activity to a global change to the toolkit.~~

	~~or as part of the on-going Sugar~~ activity ~~update process~~. ~~(The developer will work with~~ the ~~module maintainer, who~~ is ~~ultimately~~ responsible ~~to review and merge~~ the ~~new feature.) Work on new features will be tracked in the wiki and in bugs.sugarlabs.org (where modules are referred to as "components" and features are referred to as "enhancements") and~~, in the ~~case of platform features, if finished in time, they will find their way in the Sucrose stable release (See 0.88/Roadmap~~ for ~~details of~~ the ~~current release cycle~~.)

Erikos at 10:53, 4 December 2009

2009-12-04T10:53:06Z

← Older revision		Revision as of 06:53, 4 December 2009
Line 1:		Line 1:
			= Activity Process for Activities =
			== Propose a Feature ==
			The Feature can be proposed the same way than any other Feature.

			== Propose a Feature into an activity ==
			As with the Features for the

			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].


	They can range from a new capability for a Sugar activity to a global change to the toolkit.		They can range from a new capability for a Sugar activity to a global change to the toolkit.

Line 7:		Line 17:

	'''Note:''' For more background on FOSS project development, please refer to Karl Fogel's [http://producingoss.com/ Producing Open Source Software]		'''Note:''' For more background on FOSS project development, please refer to Karl Fogel's [http://producingoss.com/ Producing Open Source Software]


	~~'''Note:''' bugs are not features. We use the [http://bugs.sugarlabs.org bug tracker] to report and monitor bugs.~~

	In the case of features impacting the Sugar platform itself, the person responsible for managing the release is our community-designated Release Manager. (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].

Erikos at 10:38, 4 December 2009

2009-12-04T10:38:13Z

← Older revision		Revision as of 06:38, 4 December 2009
Line 10:		Line 10:

	'''Note:''' bugs are not features. We use the [http://bugs.sugarlabs.org bug tracker] to report and monitor bugs.		'''Note:''' bugs are not features. We use the [http://bugs.sugarlabs.org bug tracker] to report and monitor bugs.

			In the case of features impacting the Sugar platform itself, the person responsible for managing the release is our community-designated Release Manager. (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].

Erikos at 10:33, 4 December 2009

2009-12-04T10:33:39Z

← Older revision		Revision as of 06:33, 4 December 2009
Line 7:		Line 7:

	'''Note:''' For more background on FOSS project development, please refer to Karl Fogel's [http://producingoss.com/ Producing Open Source Software]		'''Note:''' For more background on FOSS project development, please refer to Karl Fogel's [http://producingoss.com/ Producing Open Source Software]


			'''Note:''' bugs are not features. We use the [http://bugs.sugarlabs.org bug tracker] to report and monitor bugs.

Erikos at 10:30, 4 December 2009

2009-12-04T10:30:57Z

← Older revision		Revision as of 06:30, 4 December 2009
Line 2:		Line 2:

	or as part of the on-going Sugar activity update process. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.) Work on new features will be tracked in the wiki and in bugs.sugarlabs.org (where modules are referred to as "components" and features are referred to as "enhancements") and, in the case of platform features, if finished in time, they will find their way in the Sucrose stable release (See 0.88/Roadmap for details of the current release cycle.)		or as part of the on-going Sugar activity update process. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.) Work on new features will be tracked in the wiki and in bugs.sugarlabs.org (where modules are referred to as "components" and features are referred to as "enhancements") and, in the case of platform features, if finished in time, they will find their way in the Sucrose stable release (See 0.88/Roadmap for details of the current release cycle.)


			Once the idea is described in a [[Features/Feature_Template\|wiki page]] (following the process described in detail below) and a developer is found who will work on the idea, it can be proposed to be part of a Sucrose release cycle. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.) Work on new features will be tracked in the wiki and in bugs.sugarlabs.org (where modules are referred to as "components" and features are referred to as "enhancements") and, in the case of platform features, if finished in time, they will find their way in the Sucrose stable release (See [[0.88/Roadmap]] for details of the current release cycle.)

			'''Note:''' For more background on FOSS project development, please refer to Karl Fogel's [http://producingoss.com/ Producing Open Source Software]

Erikos at 10:24, 4 December 2009

2009-12-04T10:24:49Z

← Older revision		Revision as of 06:24, 4 December 2009
Line 1:		Line 1:
			They can range from a new capability for a Sugar activity to a global change to the toolkit.

	or as part of the on-going Sugar activity update process. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.) Work on new features will be tracked in the wiki and in bugs.sugarlabs.org (where modules are referred to as "components" and features are referred to as "enhancements") and, in the case of platform features, if finished in time, they will find their way in the Sucrose stable release (See 0.88/Roadmap for details of the current release cycle.)		or as part of the on-going Sugar activity update process. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.) Work on new features will be tracked in the wiki and in bugs.sugarlabs.org (where modules are referred to as "components" and features are referred to as "enhancements") and, in the case of platform features, if finished in time, they will find their way in the Sucrose stable release (See 0.88/Roadmap for details of the current release cycle.)

Erikos: Created page with 'or as part of the on-going Sugar activity update process. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.)…'

2009-12-04T10:21:04Z

Created page with 'or as part of the on-going Sugar activity update process. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.)…'

New page

or as part of the on-going Sugar activity update process. (The developer will work with the module maintainer, who is ultimately responsible to review and merge the new feature.) Work on new features will be tracked in the wiki and in bugs.sugarlabs.org (where modules are referred to as "components" and features are referred to as "enhancements") and, in the case of platform features, if finished in time, they will find their way in the Sucrose stable release (See 0.88/Roadmap for details of the current release cycle.)