Commit Access

Kai Wasserbäch <[email protected]> Sun, 23 Nov 2025 20:36:12 +0100
Newsgroups gmane.comp.video.mesa3d.devel
Message-ID <[email protected]>
Hey everybody,
this might be touchy subject, but I wanted to ask how it is decided who has access to Marge. And, I guess, how this 
decision is communicated to the general public.

I am just a lowly contributor to Mesa and would not ask for direct access ever, but I have seen people "appear", that 
somehow magically got the right. Admittedly: it seems to turn out, that they are known to established contributors, but 
I find the overall process to be a bit haphazard. I am sure you (as the people who control the access to the Mesa 
project) have some "back channel", where you discuss all this, but I would prefer public announcements on at least 
`mesa-dev` that say "Some Cool Developer <[email protected]> joined $company to help with $driver".

So long story short: can you make the addition of devs a bit more transparent, please? Thanks!

Cheers,
Kai

P.S.: I avoided mentioning the last person I've noticed on purpose. I really don't want a discussion on gender. I 
couldn't care less about the gender of any contributor. As far as I am concerned: we are all humans. So anyway: please 
don't drag that in here. Thank you. I really just want to talk about transparency on who has commit rights and why. 
(Though I might be a bit late, since Mesa's rights have been controlled by corporate entities for a very long time. 🤷‍♂️)
OpenPGP_signature.asc (application/pgp-signature, 236 B)
-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQQHGGOoanjvCkOaaid97R0LvoA5AgUCaSNiLAUDAAAAAAAKCRB97R0LvoA5AmRg
AP4yGHUM70HBhM1Q1BB5NluMeX2O4SEGNpjMBAcfqLOTOAEAuBsIRJ23fRa5qvV4Yvl4A2gK6NMe
lfq7UoWUwWkBwAc=
=gXiu
-----END PGP SIGNATURE-----