Welcome everyone to the Metron project. One of the first points that we need to decide on is how you'd like to run your development. In particular, most Apache projects use either Commit-Then-Review or Review-Then-Commit. Either one works and they each have pluses and minuses and unfortunately it can turn in to a religious war of the vi vs emacs level. *grin*
Commit-Then-Review lets committers make changes to the git repository and everyone watches the commits@metron list review the changes. Review-Then-Commit requires any changes to be uploaded to github or Jira and +1'ed by a different committer before it gets pushed to Metron's master branch. The advantages are: * CTR * Patches by committers don't get blocked waiting for review. * It enables the project to move faster. * RTC * All changes are looked over before they are pushed, so some problems caught beforehand. * Less churn on master branch as review comments force changes. Thoughts? Owen
