Closed chrysn closed 1 year ago
Good initiative @chrysn! I completely agree with the 4 eyes principles and development goals :+1:
We should probably give it a few days more to let the rest have a chance to read and give feedback in case they have some input. Other than that you can consider it reviewed and approved by me!
another thought (not sure where else might be good to post this): we should probably go through the current set of PRs and close out any old ones and approve/give feedback on those that we want to merge. issues could probably use a pass as well.
I've tentatively turned on branch protections (requiring the three workflow checks we have right now) and required review (which means we should mark LGTM comments into reviews to work). Let's see if this works out :-)
As we're now multiple people maintaining this, and because I generally prefer to know which rules to play, I'd like to suggest this maintenance manual (especially when I have more rights on something than I'd like to exercise).
If we all like this (for lack of precedent, I'd like to have at least two of the current maintainers' positive review on this before going ahead), we may or may not go through the effort of setting up all the branch protection and checks and what-so-not, but to me, knowing what I may or may not do on my own would be a good starting point.
Note that I don't mention doing releases or other large project changes (like altering the maintenance manual), because these typically come from maintainers anyway -- and thus need a second maintainer to clear them, which is what I think would be good.