-
Notifications
You must be signed in to change notification settings - Fork 40
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
Are you looking for a new maintainer? #135
Comments
I think I'm the only (non-active on this project) maintainer left. I'm happy to add you since this isn't relevant enough to me any more that I can devote any significant amount of time to it. |
Actually, it doesn't appear that I have admin privileges on this repos, only commit/tag/etc. privileges. On pypi I have maintainer access but can't manage the account. I'm happy to help however I can with transferring access on pypi. At least on github you can just fork the repo and be done with it. |
I'm |
@ashb Can you follow the procedure layed out in https://www.python.org/dev/peps/pep-0541/#how-to-request-a-name-transfer ? If you do that and post a link to it I can at least write in support of it. It took me a while to get in touch with the actual project owner a few years ago and I imagine it'd be even more difficult now. So that combined with the only listed maintainer supporting the request should (hopefully) facilitate things greatly. |
What is your conclusion here: Will you continue development here or in a fork? I was just hit by #115 but I think I found a fix and could open a PR. |
I'm going to continue dev, yes, but I was hoping to not have to rename the module. |
This is great news @ashb as I am just starting out with sphinx-argparse and was a little dissapointed about the status of this repo. It would be a shame if it stayed unmaintained. Good luck with taking over and don't feel yourself forced to rush it! Not having to rename will benefit everyone, even if now everything takes more time! All the best! Jojo |
👍 |
@ashb why don't you start working in a fork of this github repo, consolidating/merging various PRs that have accumulated here. Whether or not pypi will eventually grant you permission to take over is unrelated to the above. The most important part is to ahve one repo where the back-log of patches/PRs is being processed and where development can continue. Thanks for stepping up! |
FWIW, it might make life easier for PyPI folks, if there's a replacement ready -- because then it's less of "I intend to revive the project" and more of "I have revived the project, and would like the PyPI name". |
Yes, good idea. Starting over at https://github.com/ashb/sphinx-argparse |
In case anyone is looking for an alternative rendering, and that's well maintained, check out https://pypi.org/project/sphinx-argparse-cli/, which I created after enquiring about similar here #134 |
@gaborbernat Happy to use/help with your fork rather than having another. In 134 you said:
Is that still the case? Does it work for normal commands just as well as this module does? |
Yes it does. 👍 |
It's more of a new implemention than fork 😁 |
@dpryan79 Are you able to grant me permissions on https://readthedocs.org/projects/sphinx-argparse/ please? |
Hi there,
Love this project, and we use it on apache/airflow where it's great.
I notice that there are a number of open PRs, and I understand the burden of being an open-source maintainer, so I'd like to volunteer to help address some of these, get them merged/closed etc and then eventually released.
So I'm wondering if you are looking for help maintaining this project @alex-rudakov?
(I hope I wasn't to presumptuous in asking)
The text was updated successfully, but these errors were encountered: