One can use the branch protection rule to restrict who can merge PRs into 
the protected branch: 
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#restrict-who-can-push-to-matching-branches

But of course this only takes care of the technical side. It can of course 
still happen that someone oversees an issue in a PR or that the standard of 
"good code" differ slightly. I guess for this only communication, writing 
documentation and, for the base level, linter help.

On Friday, 11 November 2022 at 11:48:52 UTC+1 vdelecroix wrote:

> Dear all,
>
> I am one of the maintainer of cypari2. Contrarily to Jeroen and Luca
> who left, I am not a number theorist and not a specialist of PARI/GP.
> I took over the maintainance responsability because it felt like a
> good thing for the math community and because PARI development happens
> in a nearby lab and Bill Allombert is constantly helping.
>
> I had other tasks to do these days and was not very pro-active. Some
> members of sagemath, though not registered as sagemath/cypari2 admin,
> decided to start integrating merge requests even though these merge
> requests were not adequate (eg version bump inside a merge request and
> code that depended on a development branch of cysignals). It took me a
> lot of headache to rewrite git history and end up with a clean
> release. I am very frustrated that it took me a full day rather than
> an hour to finalize this release. Moreover, the forced push to the
> master branch is not nice to the contributors of cypari2.
>
> Do you have suggestion on how such things could be avoided with
> cypari2 being on github under the sagemath group?
>
> Best regards,
> Vincent
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d889a3aa-07c5-4f23-8fca-47d6d1dfec0en%40googlegroups.com.

Reply via email to