Skip to content

Conversation

@ulysses4ever
Copy link
Collaborator

@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:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

@ulysses4ever ulysses4ever force-pushed the add-maintainers branch 2 times, most recently from c83dbfd to 836b122 Compare August 29, 2025 04:41
@ulysses4ever
Copy link
Collaborator Author

great lord, what's wrong with whitespaces?..

@geekosaur
Copy link
Collaborator

Added space at the end of the first line.

Copy link
Collaborator

@ffaf1 ffaf1 left a 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

@Mikolaj
Copy link
Member

Mikolaj commented Aug 30, 2025

BTW, @mpickering is on a long vacation right now.

@Bodigrim Bodigrim linked an issue Aug 31, 2025 that may be closed by this pull request
@ulysses4ever
Copy link
Collaborator Author

Hey all! I did a second pass and kindly ask you to take another look!

@ulysses4ever ulysses4ever added the squash+merge me Tell Mergify Bot to squash-merge label Sep 2, 2025
@mergify mergify bot added the ready and waiting Mergify is waiting out the cooldown period label Sep 2, 2025
@hasufell
Copy link
Member

hasufell commented Sep 2, 2025

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]>
@ulysses4ever
Copy link
Collaborator Author

@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.

@mergify mergify bot added the merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days label Sep 4, 2025
mergify bot added a commit that referenced this pull request Sep 4, 2025
@mergify mergify bot merged commit 781ebea into master Sep 4, 2025
97 checks passed
@mergify mergify bot deleted the add-maintainers branch September 4, 2025 21:43
@mpickering
Copy link
Collaborator

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).

@ulysses4ever
Copy link
Collaborator Author

ulysses4ever commented Sep 15, 2025

@mpickering sounds good, see #11216

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days ready and waiting Mergify is waiting out the cooldown period release squash+merge me Tell Mergify Bot to squash-merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CLC] Clarify list of maintainers

7 participants