Is Scoder the only maintainer for Cython?

[0dminnimda]

Sorry, but are there any other maintainers besides Scoder? Since I think Scoder is busy right now, is there any other way to merge PR? It's not very cool that the contribution has slowed down a lot, if not stopped and will be like this for an unknown period of time ...

Has anyone thought of creating a group of people who will have a little less rights than Scoder, but who will make his life easier with their numbers and therefore their ability to react faster?

Or .. sorry, there is no one to choose from? I mean, there are no people with sufficient skill and experience who would want to maintain Cython?

[William Stein]

Hi,

I started this project around many years ago by wrangling various people into combining their forks into one project (with an actual git repo) and posting it.  I'll try bugging some of those people to see what the situation with the Cython github project is right now.   I'm personally not a committer or able to do anything with the actual Github project, since github didn't exist back when I was involved and writing Cython compiler code.  But surely somebody who does have appropriate privileges will listen to me :-)

 -- William

[Robert Bradshaw]

I'm still around, but don't often have much time these days... which I think is a common problem.

--

---
You received this message because you are subscribed to the Google Groups "cython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cython-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cython-users/10041590-960c-4088-b31d-d93faee82800n%40googlegroups.com.

[Blue]

>  Has anyone thought of creating a group of people who will have a little less rights than Scoder, but who will make his life easier with their numbers and therefore their ability to react faster?

Github has branch protection rules: https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule

A bigger group of people could be created that only have access to merge to some form of `dev` branch. This branch could then be periodically merged into the `master` branch by someone like Scoder, after sufficient tests and reviewing has been done.

Or just more people can get access to `master`, since commits to the master branch don't automatically streamline to PyPI.