-
Notifications
You must be signed in to change notification settings - Fork 640
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
Change of maintainers for checker and kernel #7346
Comments
Pending on some IRL chat with @barras to know what his plans wrt to Coq are. |
I already said that somewhere, but I believe that we need to involve as many persons as possible for the kernel and for the checker. Only one main owner does not reflect the complexity of the kernel internals, as devs typically have knowledge over a subset of the several components from the kernel (e.g. universes, inductive types, VM, conversion...). |
If these subsets correspond to different files it is easy using GitHub |
Separate maintainers for univ stuff | VM and native stuff | other kernel stuff sounds reasonable. |
Mitigates coq#7346. [skip ci]
Mitigates coq#7346. [skip ci]
This has been mostly solved. @barras is still listed as a secondary maintainer of the kernel if he ever wants to come back but we don't depend on him. |
@barras is listed as the primary maintainer for the checker (and @maximedenes as the second one) and as the secondary maintainer for the kernel (and @maximedenes as the primary one) but he hasn't answered to #7032 (which basically amounts to a "No"). He has also never participated to the development since it moved to GitHub and his last commit predates the 8.5 release. So it means that we are currently without a primary maintainer for the checker and a secondary maintainer for the kernel.
Possible candidates: @mattam82 @ppedrot @SkySkimmer
coq/.github/CODEOWNERS
Lines 55 to 56 in 72d6d5e
coq/.github/CODEOWNERS
Lines 91 to 92 in 72d6d5e
The text was updated successfully, but these errors were encountered: