Thanks again, great to get this feedback.

Since I started with this project I noticed that every company is a different world, so there are many cases, may not use partial reviews, another ones love it, the idea is to have a pretty flexible platform for any company. Let's assume you don't want to get any feedback until you finish your 2 weeks works, that's fine, you can just ignore any review you get meanwhile, but sometimes it could be really useful (may not be your case maybe :), which is also fine!)

Considering the issues you mentioned with Gerrit:

• we don't assume, you just set up your rules in your company settings. We are working to integrate with as many tools as possible, so you can have even more flexibility: you can integrate with Jenkins for your build status, Trello/Pivotal for your functional context and issues management, and so on.
• In our comments and issues you can mention (@username) anyone in the team, add images by just drag and drop them, include code snippets, links and much more by using the same Github markdown.
• Our ticket system is richer but again, we integrate with the one that your team already uses (Trello, Pivotal, Jira, etc etc). You can create an issue an associate to an specific line, so if you change that line without closing it we can alert you that maybe the issue was fixed but you forgot to close it (common administrative problem) [some of them are not ready yet!]
• Own QA Plugin to easily repot issues and link them with your code in a very easy and straightforward way
• Own CLI tool to use our business rules engine from your terminal (like git merge-gc, runs all the internal validations and then calls git merge)

Basically, we are trying to create a collaborative solution to handle the whole code quality of your project (dev + QA). In order to do this, we want to: * Improve the current code review experience (there are many things to improve in the process) * Integrate QA in the process (associate cards + issues to the code so you can manage and have everything in the same place + get QA approval before deploying into production) * Create a quality incident system: define critical paths for your repos, so we let you know when anything changed there, automatic pull requests assignments based on skills and workload and much more! * Integrate with deployment tools: you will be able to know which cards are already merged and deployed and the corresponding environment (easier way to test + debug your code)

Please let me know if this clarifies our vision :) I would love to answer any other question/feedback! I do really appreciate again your feedback and time!

Thanks!