The 14-days rule of feature decision making

Also known as the 2-week rule

It is part of the decision making process of the TWikiCommunity, and structures the way new feature proposals are handled.

The clock starts ticking as soon as:

1. The specification has been written
2. A developer commits to implementing the feature

The 14-days rule applies when:

1. The proposal has a developers committed to drive the implementation.
2. Noone has raised any concern against the feature or its spec.
   • Anyone can raise ANY concern.
   • The minute there is concern the clock stops.

The rule is there so that proposals that are nobrainers that noone will argue against or do not care about do not end up rotting. And it also creates an incentive for the community to react. If there is concern then the discussion needs its time to finish. That is why the clock stops.

If people then agree - and this happens often - then there is a consensus decision.

• Q: And if the release meeting agrees, and someone still raise a concern, (within the 14 days)?
• A: The release meeting should not decide unless people have had a chance to evaluate the proposal. Unless it is a total nobrainer.

See details at TWikiReleaseManagementProcess.

-- Contributors: ArthurClemens - 23 Apr 2007

Discussion