-
Notifications
You must be signed in to change notification settings - Fork 724
Add list of maintainers #11195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add list of maintainers #11195
Conversation
c83dbfd to
836b122
Compare
836b122 to
ef70590
Compare
|
great lord, what's wrong with whitespaces?.. |
|
Added space at the end of the first line. |
ffaf1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Many thanks for having written this!
The list is a bureaucratic necessity, Cabal is of all the people putting in the work
|
BTW, @mpickering is on a long vacation right now. |
|
Hey all! I did a second pass and kindly ask you to take another look! |
b909751 to
628a742
Compare
628a742 to
60eaa1c
Compare
|
More out of curiosity... but does this also mean that only the people listed here explicitly as maintainers have decision making power wrt cabal proposals? https://github.com/stable-haskell/cabal-proposals?tab=readme-ov-file#3-decision-meeting |
Co-authored-by: brandon s allbery kf8nh <[email protected]>
|
@hasufell the document you cite operates with the notion of "Cabal developer", which is broader than "Cabal maintainer" as defined in this PR. If you think it's not clear enough, the discussion should probably be moved to a separate issue, as this PR defines a very narrow group with a very specific job description: releasing Cabal. There's probably a lot of possible interactions between this notion and other interested parties. |
|
Thank you for think of me @ulysses4ever, I am happy to be added to some kind of list if it's useful (but also not so bothered to make a PR myself). |
|
@mpickering sounds good, see #11216 |
@Mikolaj @ffaf1 @geekosaur please, let me know what you think. My idea was to avoid formal criteria like "participated in K out of last N meetings" (there was a valid concern about the exclusionary nature of synchronous events) and instead to focus on release procedures (but meetings count too :-)).
@mpickering do you want to be on this list? I think you absolutely qualify. Just wanted to ask you first.
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: