Well I am not too sure about this, but as I see it, the more that gets done the better it is for everyone, Moodle included.
You already have certain permissions to do what you are doing with Formal White, however, you need to be aware that it is ultimately the decision of those who work at Moodle HQ, like Sam, who have the last word. Pushing amended code to your GITHUB is good, whether or not it is accepted is another matter entirely. If you do something in the wrong order, someone from HQ will advise you what you should be doing, and how to do it.
I think the reason that Michael said about Peer Review in that particular case, is because it was a change from the normal and needed a 'closer look' before being integrated. Peer review, in this particular case, is about accepting changes which are 'improvements for the better' rather than 'changes for changes sake'. There is a subtle difference.
As for pushing
MDL-29614 as it is, will either be accepted or rejected, with or without amendments.
My advice is, if YOU think it is right, then do it, because it is easier to apologies than it is to get permission.
At the end of the day, you can only do what you can do. If you cannot 'assign yourself' to a tracker issue you created then so be it, you will not be able to see the other settings which allow you to 'submit for integration'. But that said, there is nothing stopping you from doing the changes and pushing them to GITHUB and then ask me to PEER REVIEW it and if OK I can submit it for integration.
So we have the best of both worlds here. Does this sound logical?
As far as
MDL-29830 and MDL-29778 I'll add my comments there. OK?
as for my origins - mia mama era una veneziana