Question about the gRFC review process about proposal HOT 3 CLOSED

cc: @hsaliak

Hi, Kailash and I came up with the gRFC process. The reason is practical: Github's commentary system is difficult to use. There are no threaded conversation aspects, and individual messages cannot be easily linked to. Additionally, if the author rebases the PR while making updates, the commentary is completely lost (except if you saved the emails). Rebasing also happens at the end of the PR sometimes, which means if you squash and merge, all the commentary is lost.

If there was a system like Google's internal code review tools, I think this wouldn't be an issue.

Hope that helps, let me know if you have more questions.

from proposal.

I'd add one more minor reason. We want the mailing list to be something users can follow to be on top of discussions around the project. Following pull requests in this repo to be on top of what is happening adds one more location for users to follow..

from proposal.

Thank you very much, @carl-mastrangelo @hsaliak - that helps a lot :)

from proposal.