Superceded (in part) by Committer's Zone policy of lazy consenus.
FINERACT Is Currently A Top-Level Project In The Apache Software Foundation.
Find below our processes, which of course are subject to change.
Bootstrapping the processes
- All process documents are first written in confluence and marked as drafts. A committer proposes the draft process for discussion on the dev mailing list.
- If there are no objections from committers, the process is accepted. The draft notation is removed.
- If there are objections, the proposer and the originators of the objections discuss and adjust the proposal. Return to step 1.
Changing the process
Once a process exists, it may need to be evolved. This is how
- For small changes, the contributor who wishes to propose a change to the process writes a comment on the confluence page describing the desired diff.
- For large changes, the contributor who wishes to propose a change to the process creates a child of the existing page with the new content and marks it at the top as a draft or change proposal.
- The proposer then submits the proposed change to the dev mailing list for consideration.
- Once the proposer believes the discussion has concluded, the proposer adjusts the documentation (if necessary) to reflect the consensus as he or she understands it.
later addition: we have adopted lazy consensus see details on Committer's Zone
- The proposer removes drafts and comments the documentation with any major findings still missing there.
- The proposer notifies the rest of the community of any significant changes via the dev mailing list. Insignificant changes require no notification – the proposer should apply his or her own discretion.