Talk:Features/Policy: Difference between revisions

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.

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

@@ 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.
@@ 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:''' 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].