Fixing features

This page is currently OPEN for suggestions on fixing the Feature Process. Comments will close, at least temporarily, on June 15, 2011, so that feedback can be assessed and we can move on to next steps.

Fixing the Feature Process

A good number of people think that the Feature Process, as it exists currently, is broken. This page is an attempt to start gathering feedback, information, specific examples, suggestions, flames, praise, or anything else you'd like to leave.

I (Robyn) will leave this wiki page open for commentary through 2011-06-15. After that, I'll attempt to concatenate some of the information into a readable format by 2011-06-20, and start figuring out what next steps should be, if any.

Please remember: This is a wiki page, BE BOLD! Feel free to add additional sections, information, etc. as you see fit. If people want to use the discussion tab, go for it.

About the Feature Process

Here are some handy links to Feature Process-related wiki pages.

• Feature schedule / Milestones (General, not specific to F16 dates or any other release)
• Feature Policy background
• Feature Acceptance policy
• What happens to features during the course of the release cycle
• Feature Policy Process and diagram
• Feature Policy Questions

Comments, Suggestions, Flames taken HERE.

Please put your comments in below. Adding your signature is helpful, as it allows for follow-up without having to sort through wiki history.

Problem Areas

• Your comment here. Use the signature button to sign your name, to make follow-up easier. --Rbergero 13:13, 1 June 2011 (UTC)
• We really have multiple goals with features and the requirements for them should be different:
  • Features that require package maintainers to coordinate with each other (NetworkManager updates, systemd, programing language updates)
  • Features that we want release noted and to hit marketing (new version of blender/inkscape/other self-contained app)
  • Some features have some degree of cross-over (gnome3, kde4 for instance) as they're both major end user changes and require coordination with others
• Features that fall into the first category (requiring maintainers to coordinate with each other) arriving late in the cycle but being approved either as (1) part of another feature or (2) because we don't consider the burden it might place on other maintainers.

Things that work

Do you think that some particular things work *well* in the Feature process? List them here -- the goal should be to fix the things that are broken, and keep the things that work well.

• Your comment here. Use the signature button to sign your name, to make follow-up easier. --Rbergero 13:13, 1 June 2011 (UTC)

Specific examples of where the Feature Process failed

Specific examples help out quite a bit. If you have any, please list them here.

• Your comment here. Use the signature button to sign your name, to make follow-up easier. --Rbergero 13:13, 1 June 2011 (UTC)

Suggestions Welcome

Have any ideas on how to improve the feature process? List them here!

• Your comment here. Use the signature button to sign your name, to make follow-up easier. --Rbergero 13:13, 1 June 2011 (UTC)

Other comments

Comments that don't fall into any of the above categories can land here.

• Your comment here. Use the signature button to sign your name, to make follow-up easier. --Rbergero 13:13, 1 June 2011 (UTC)