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

Transfer abdonned project PyQRCode - PEP-541 #4121

Closed
heuer opened this issue Jun 3, 2018 · 12 comments
Closed

Transfer abdonned project PyQRCode - PEP-541 #4121

heuer opened this issue Jun 3, 2018 · 12 comments
Assignees

Comments

@heuer
Copy link

heuer commented Jun 3, 2018

PyQRCode seems to be unmaintained.

I contributed code two years ago and I like to take over the project since all requests (email and issue reports) to the current owner end up in nothing.

See mnooner256/pyqrcode#52
My fork: https://github.com/heuer/pyqrcode/tree/develop

My PyPi-Account: heuer

Thanks a lot.

@ericmjl
Copy link

ericmjl commented Aug 13, 2018

If appropriate, I would like to record my support here for @heuer to take over the project. @heuer has been more responsive than the original developer, has been active on the issues tracker, and has developed a new version of the package that is only awaiting a new PyPI release.

@ericmjl
Copy link

ericmjl commented Aug 20, 2018

Hi @di, I hope this doesn't come across as being pushy here. As I'm new to the this PEP541 thing, I was just wondering what the process and timeframes are for transferring a repository? Again, not trying to be pushy here, I just wanted to understand the process a bit better as it's being implemented.

Thanks in advance for all of your efforts!

@di
Copy link
Member

di commented Aug 20, 2018

@ericmjl The process has been agreed upon in PEP 541, but hasn't been implemented yet.

Right now we are working on adding the necessary admin features to be able to take action on PEP 541 requests, to do so in a fair way to all users, and to be able to organize them in a way that is not incredibly time-consuming for the volunteers who will be responding to them (e.g.: #3231, #4011, #4022).

Since this is an entirely volunteer-driven project, it's not really possible to provide a timeline. I can say that these issues are my current highest priority, when I am able to find the time to work on them.

What you've done so far is exactly the right thing to do, and I'll be happy to address your request once said features are in place.

@ericmjl
Copy link

ericmjl commented Aug 20, 2018

@di, thanks for pinging in, and for the clarification! 😄 Also, thanks a ton for the work that you've been doing!

@mfrasca
Copy link

mfrasca commented Mar 30, 2019

one more user, supporting the request. or considering moving away from PyQRCode.

@yeraydiazdiaz yeraydiazdiaz self-assigned this Apr 22, 2019
@yeraydiazdiaz
Copy link
Contributor

Hello @heuer, I have sent @mnooner256 an email asking to clarify his position regarding this package. Hopefully we will hear from him soon and move this request forwards.

Thank you for your patience while we deal with these issues.

@yeraydiazdiaz
Copy link
Contributor

Hello @heuer, @mnooner256 has replied to my email and stated his intention to continue working on PyQRCode, thus no ownership transferral is possible.

At this point I can only suggest creating a fork and publishing a project under a different name.

I will now close this issue. Thank you for your patience.

@heuer
Copy link
Author

heuer commented Jun 2, 2019

Thanks for your work, @yeraydiazdiaz!
I am glad that Michael responded and is willing to maintain the project.

@mfrasca
Copy link

mfrasca commented Jun 2, 2019

my "confused" statement: because the last commit by the current official maintainer is still 3 years old.

@ericmjl
Copy link

ericmjl commented Jun 2, 2019

Yes, this is great news! Thanks for clarifying, and for handling this request!

@om26er
Copy link

om26er commented Jan 16, 2020

ping @mnooner256, is there an update on your plans, do you still plan to continue development of PyQRCode or maybe are willing to transfer maintainership to people interested ?

@di
Copy link
Member

di commented Jan 16, 2020

Hi folks, please have this discussion on the projects tracker instead. Thanks.

@pypi pypi locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants