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

  1. 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.
  2. If there are no objections from committers, the process is accepted.  The draft notation is removed.
  3. 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

  1. 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.
  2. 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.
  3. The proposer then submits the proposed change to the dev mailing list for consideration.
  4. 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
  5. The proposer removes drafts and comments the documentation with any major findings still missing there.
  6. 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.
  • No labels

1 Comment

  1. Adjust this document to remove voting, based on objections:

    "In general, my strong advise to any young community is to avoid formal votes as a plague. At its core ASF runs on natural, not forced consensus. Any time there's a natural consensus -- you really don't need a vote. Any time there's a formal vote as a forcing function to a consensus -- you inevitably end up creating winners and losers. You really don't need that. At least not while the community is still young (and even when it grows up -- you don't *really* need it)."

    (Link to e-mail thread: