This was taken out of the discussion in #6966. It spells out the _minimal_ requirements
to the maintainer group. However it is left open, how it will be done since that depends on
the set of maintainers and their individual experiences and preferences.
Thank you @nasamuffin for helping me out of the writers block here.
Copying from Discord:
@ilyagr recently accepted a job offer from East River Source Control
(ersc.io). That means we will have two of the five maintainers from
that company (@thoughtpolice is the other one), which is more than the
1/3 that our policy allows
(https://github.com/jj-vcs/jj/blob/main/GOVERNANCE.md#single-company-influence). To
resolve it, we decided to add more maintainers. We're happy to
announce that both @bnjmnt4n and @scott2000 have agreed to join. Thank
you!
We've discussed this a few times among the maintainers. Let's write it
down before it happens. The Mercurial steering committee has a similar
rule, FWIW.
This is the result of a lot of back and forth, the weekly efforts of the
governance working group, consisting of:
- Martin von Zweigbergk (martinvonz)
- Waleed Khan (arxanas)
- Emily Shaffer (nasamuffin)
- Austin Seipp (thoughtpolice; yours truly)
Many thanks as well to emeritus member Khionu Sybiern, who helped kickstart this
whole process.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
