Once again, thank you for your reply and editing the issue for me.
Being a first time contributor, I find this to be extremely convoluted and daunting to make anew patch. New developers will not know existing developers or HQ members. Further more, the Process page does not mention anything about this system. And I doubt first time contributors will read through pages upon pages of the documentation to figure out how to make a patch.
Being a first time contributor, I find this to be extremely convoluted and daunting to make anew patch. New developers will not know existing developers or HQ members. Further more, the Process page does not mention anything about this system. And I doubt first time contributors will read through pages upon pages of the documentation to figure out how to make a patch.
I think a good in-between is to make all new members of the tracker a "contributor" by default and letting them edit an issue while allowing only developers to request a code review from HQ or leads. This should also help cut down on any code review spam (if that was ever an issue to begin with).