<div dir="ltr"><div class="gmail_extra"><div class="gmail_extra">Here is a summary that I came up with from the discussion so far. Does this look good?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Requirements:</div>

<div class="gmail_extra"><br></div><div class="gmail_extra">- Branch / topic based workflow</div><div class="gmail_extra">- Automated testing before merge (required to pass)</div><div class="gmail_extra">- Assign reviewers to topic</div>

<div class="gmail_extra">- Review / approval before merge (required to pass)</div><div class="gmail_extra">- Ability to go back to discussion leading to merge (audit trail)</div><div class="gmail_extra">- Automatic notification on change</div>

<div class="gmail_extra">- Ability to comment on the code (Web GUI preferred)</div><div class="gmail_extra">- All reported bugs should be assessed and assigned</div><div class="gmail_extra"><br></div><div class="gmail_extra">

Nice to have:</div><div class="gmail_extra"><br></div><div class="gmail_extra">- Tight integration with issue (bug) tracking and release process</div><div class="gmail_extra">- Stakeholders for particular pieces identified / in the loop / easy or automatic assignment of</div>

<div class="gmail_extra">reviewers</div><div class="gmail_extra">- Ease of use</div><div class="gmail_extra">- Incentive for reviewers (goal being encouraging more reviews)</div><div class="gmail_extra">- Integration with Wiki</div>

<div class="gmail_extra">- Easy documentation / Markdown /rST support</div><div class="gmail_extra">- Easy way to generate single view of all changes in the Web GUI</div><div class="gmail_extra">- Lightweight proposal process for large changes</div>

<div class="gmail_extra">- Way to track performance regression</div><div class="gmail_extra"><br></div></div></div>