Skip to content
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

Transferring a project to Jazzband when the original author has gone AWOL #150

Closed
richardbarran opened this issue Jun 20, 2019 · 8 comments

Comments

@richardbarran
Copy link

Hi,
I've been following django-sortedm2m, as I have an app of my own that depends on it.

There's has been no development on this project since 2017.

A ticket has been opened to enquire as to the status of the project, and the original author has been pinged several times, but as far as I know he/she has never responded.

So... I believe that the project in question would thrive in the Jazzband universe: it's popular, has several contributors, and people want to contribute code to it today. And such a move has already been suggested by various people on the sortedm2m issues pages.

But there would be - apparently - no approval from the original maintainer, if the codebase was copied/duplicated into Jazzband.

Pypi have a process in place to release and re-use project names when the original owner walks away (PEP 541), but as far as I can tell there is no equivalent set up for Jazzband.

So I want to enquire as to how Jazzband members and roadies feel about taking on a project without the approval of the current maintainer, before I make a formal proposal to move this project over.

I look forward to your comments.

@jezdez
Copy link
Member

jezdez commented Jun 20, 2019

I'm afraid, this will need approval from @gregmuellegger. I'll ping him on Twitter, too.

@gregmuellegger
Copy link

gregmuellegger commented Jun 26, 2019

Feeling rather sorry for blocking all this by lack of time and involvement in the Django-universe in the last years (and basically wasting working hours of other people by not watching my GitHub feeds). So I'm rather happy if it would be adopted.

Go ahead and thanks for taking the time and efforts on you. 🙇

I guess that also needs some other actions from my side for transfering permissions on pypi and others. I'll try to follow the actions - ping me again on Twitter if necessary.

@jezdez
Copy link
Member

jezdez commented Jun 26, 2019

@gregmuellegger In that case, please join the Jazzband GitHub org and simply transfer the repo to the organization using GitHub's own transfer tool in the repo settings. Once that's done, @richardbarran can take it from there.

@jezdez
Copy link
Member

jezdez commented Jun 26, 2019

@gregmuellegger You can join on https://jazzband.co/ by clicking "Login and join" and follow the instructions.

@richardbarran
Copy link
Author

Thanks @gregmuellegger.
I'm happy to help out with the transfer of the project over to Jazzband if necessary (although I'd rather not become the project lead, as I'm already involved in several other projects).

@clintonb
Copy link

@gregmuellegger would you add jazzband as a PyPI maintainer so we can (eventually) create releases? https://jazzband.co/about/releases

@gregmuellegger
Copy link

Done!

@jezdez
Copy link
Member

jezdez commented Jun 27, 2019

The package has been transfered and further todos are tracked in #152. Thank you all for working on this!

@jezdez jezdez closed this as completed Jun 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants