Changes

It's sometimes easy to mistake new packages, or  enhancements, for features. Features have a very specific  definition, but here are some questions to ask yourself before engaging the feature process.

It's sometimes easy to mistake new packages, or  enhancements, for features. Features have a very specific  definition, but here are some questions to ask yourself before engaging the feature process.

1. Is this change very visible to end users?

#Is this change very visible to end users?

* In this case "end user" means "someone in the audience for this change," which could be desktop users, developers, or system administrators.  

#* In this case "end user" means "someone in the audience for this change," which could be desktop users, developers, or system administrators.  

2. Does this change require intervention?

#Does this change require intervention?

* This might be a configuration file format change, or something else that will perturb unsuspecting end users.

#* This might be a configuration file format change, or something else that will perturb unsuspecting end users.

* A change that requires a very simple intervention to revert behavior is not necessarily a feature.  

#* A change that requires a very simple intervention to revert behavior is not necessarily a feature.  

3. Is this something that will interest the lay press?

#Is this something that will interest the lay press?

* The lay press in this case includes Linux-oriented sites.

#* The lay press in this case includes Linux-oriented sites.

== What does the feature process ''look'' like? ==

== What does the feature process ''look'' like? ==