Dear coreboot folks,
I’d like to request for a policy on how the coreboot development guidelines are changed.
### Background ###
The discussion in patch set #11784 [1] confused me quite a bit.
Especially, seeing Aaron’s quote of the development guidelines I thought, why is this even discussed.
https://www.coreboot.org/Development_Guidelines#Assembly_Language states: "To keep the code consistent across the different supported platforms, AT&T syntax is to be used through-out the project. We are working actively on replacing the existing Intel syntax code with AT&T syntax. No new Intel syntax code is allowed into the project."
But then, I wondered why I was not aware of that section in the development guidelines [2], and wanted to read up on it. While at it, I also looked through the history, and there I see, that it was only added [3] on the same day.
I thought that editing rights for that page were blocked, because changes without discussion shouldn’t be made.
Further on, I’d like changes to the development guidelines be announced in the official forum, which is this mailing list, so that developers, normally not reading the guidelines every day, are made aware of that.
### Proposal ###
Changes to the development guidelines can only be made, when the following criteria are met.
1. A proposal of the change was sent to the list tagged with [RFC]. 2. The proposal was up for discussion for at least two weeks. 3. If there is no objection, the change can be made. 4. If there is objection, and no agreement can be reached, the proposal(s) should go up for a vote. The vote period should be at least one week. 5. Changes have to be announced to the list.
### Past changes ###
No idea, but I’d think it’d be only fair to revert the changes made this months, and discuss them first.
Thanks,
Paul
[1] https://review.coreboot.org/11784 [2] https://www.coreboot.org/Development_Guidelines#Assembly_Language [3] https://www.coreboot.org/index.php?title=Development_Guidelines&type=rev...