You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* add list of maintainers
* minor fixes from review
* volunteers -> people
* second pass (+ more clarity on how to get in the meetings)
* Update MAINTAINERS.md
Co-authored-by: brandon s allbery kf8nh <[email protected]>
---------
Co-authored-by: brandon s allbery kf8nh <[email protected]>
The main goal of the team is to ensure that Cabal is keeping up with the ever-evolving Haskell ecosystem.
16
+
In practical terms this means producing releases of the packages in this repository on a regular basis: we usually have to release at least as often as does GHC due to an intimate connection between the compiler and the build system.
17
+
Hence, the people listed above (in chronological order by when they joined the team) are those who are currently available for carrying out the release procedures.
18
+
19
+
Successful maintenance requires coordination, and the team engages in three main ways:
20
+
21
+
- attending to issues and PRs on GitHub;
22
+
23
+
- discussing Cabal on the [Matrix channel](https://matrix.to/#/#hackage:matrix.org);
24
+
25
+
- meeting biweekly in video calls with agenda prepared asynchronously in a Markdown document, which also holds the meeting notes.
26
+
27
+
Worth noting that the meetings are open to everyone interested in Cabal, especially aspiring and returning Cabal contributors. Ask on Matrix how to join.
28
+
29
+
Most of the current team are volunteers, and we are happy to receive any help.
30
+
If you want to participate in Cabal maintenance as defined above (e.g. take on some release tasks), get in touch: open a GitHub discussion or send a message on Matrix.
0 commit comments