Warehouse: Transfer abdonned project PyQRCode - PEP-541

Created on 3 Jun 2018 · 12Comments · Source: pypa/warehouse

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 https://github.com/mnooner256/pyqrcode/issues/52
My fork: https://github.com/heuer/pyqrcode/tree/develop

My PyPi-Account: heuer

Thanks a lot.

Source

heuer

👍4

Most helpful comment

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 on 22 Apr 2019

👍2

All 12 comments

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 on 13 Aug 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!

ericmjl on 20 Aug 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.

di on 20 Aug 2018

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

ericmjl on 21 Aug 2018

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

mfrasca on 30 Mar 2019

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 on 22 Apr 2019

👍2

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.

yeraydiazdiaz on 2 Jun 2019

😕1

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

heuer on 2 Jun 2019

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

mfrasca on 2 Jun 2019

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

ericmjl on 2 Jun 2019

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 ?