These are just some ideas for governance policy, which is outside my pay grade, but I wanted to note them down for future discussion/consideration:
I think anyone with commit access to Starshot should be able to:
Commit things like hotfixes, typo fixes, minor README addenda, etc. to main directly and unilaterally, without first submitting a PR.
Roll patch-level releases unilaterally.
These would, I think, be in the interest of keeping Starshot fast-moving. The lack of an upgrade path means we have more freedom to move fast and hopefully not break things.
I would also advocate for making the "RTBC process" discretionary. In other words, folks with commit access to Starshot should be trusted to review and commit anything they think is ready to go, even if it's their own work. Peer review is certainly good practice, and should be recommended, but it need not be required. We can always revert a bad commit, or make follow-up changes to fine-tune things.
These are just some ideas for governance policy, which is outside my pay grade, but I wanted to note them down for future discussion/consideration:
I think anyone with commit access to Starshot should be able to:
maindirectly and unilaterally, without first submitting a PR.These would, I think, be in the interest of keeping Starshot fast-moving. The lack of an upgrade path means we have more freedom to move fast and hopefully not break things.
I would also advocate for making the "RTBC process" discretionary. In other words, folks with commit access to Starshot should be trusted to review and commit anything they think is ready to go, even if it's their own work. Peer review is certainly good practice, and should be recommended, but it need not be required. We can always revert a bad commit, or make follow-up changes to fine-tune things.