Bug #67

Task #2: Identify module owners and team leads

Improve policy on project owner responsibilities

Added by Colin Snover over 5 years ago. Updated over 5 years ago.

Status:New Start date:06/14/2012
Priority:Normal Due date:
Assignee:Dylan Schiemann % Done:

0%

Category:-
Target version:-

Description

Right now it feels like there is a lot of territoriality with regards to who can or can not set priorities/milestones/etc. on components, who can land patches on components, etc. I believe that any person that is a member of the contributors group has been vetted enough that they should be able to just go ahead and set priorities, etc. on any component if they have a good reason for doing so, rather than saying it is the strict decision of the component owner, since it is difficult for owners to always know everything that people are having trouble with and the easiest way to communicate that is with a priority shift. I think we are all responsible enough not to go crazy with this that it is not a big deal, and this will help contributors feel less uneasy about contributing to other components instead of staying in their own little box. This is a team, after all.

History

Updated by Kitson Kelly over 5 years ago

I assume you mean committers group, versus contributors group?

The only thing that we should consider is some sort of "checkin war" or something silly. While I agree there is some level of territoriality, there has to be some level of structure. There should at least be an opportunity for the component owner to be involved, but that should prevent progress.

Colin Snover wrote:

Right now it feels like there is a lot of territoriality with regards to who can or can not set priorities/milestones/etc. on components, who can land patches on components, etc. I believe that any person that is a member of the contributors group has been vetted enough that they should be able to just go ahead and set priorities, etc. on any component if they have a good reason for doing so, rather than saying it is the strict decision of the component owner, since it is difficult for owners to always know everything that people are having trouble with and the easiest way to communicate that is with a priority shift. I think we are all responsible enough not to go crazy with this that it is not a big deal, and this will help contributors feel less uneasy about contributing to other components instead of staying in their own little box. This is a team, after all.

Also available in: Atom PDF