flask-classy
flask-classy copied to clipboard
apiguy
flask-classy continuing development and maintenance
Hello guys,
flask-classy is awesome, however, I don't know why @apiguy haven't responded for a while with PR and issues.
So I forked the project and add more features, supports for it here at: https://github.com/teracyhq/flask-classful
and the updated documentation here at: http://flask-classful.teracy.org/
One thing remains is that I don't have flask-classy pypi credentials to updating it on pypi.
I hope that @apiguy will see this and provide me the credentials to update on pypi.
Or maybe I'll change the flask-classy to something like: flask-class to publish on pypi.
Let's see how we could come up with this project.
@hoatle Hi, nice to see you're taking over maintenance of this. With regards to the PRs against this repo, have any or all of them been merged in to your fork?
@OOPMan yes, I think I merged some and added some more updates, please checkout the commits here at: https://github.com/teracyhq/flask-classy/commits/develop
@hoatle Great. Just wanted to check as I will probably be adding your fork to a project I'm working on...
@OOPMan yes, and you should access the update the latest docs at: http://flask-classy.teracy.org/ (on master branch) and http://flask-classy.teracy.org/develop/ on develop branch
I've pinged @apiguy on Twitter as well regarding this. I'll also use @hoatle's fork in my projects from now on.
@hoatle Thank you for inheriting the project. I have a question about PyPI registration. Do you have any intention to register your fork as another package name? I don'k now if you can use @apiguy 's PyPI account.
I think it is more convenient if the package can be found on PyPI.
@lucidfrontier45 ,
@hoatle would need access to @apiguy to publish under the same name (even though doing so would absolutely be the best) or start a claiming process. It would be better if @hoatle could be invited to this repo of course.
@hoatle You can open a support request for Pypi to claim ownership of a abandoned project by visiting http://sourceforge.net/p/pypi/support-requests/ and creating a new support request. Looking at https://mail.python.org/pipermail/distutils-sig/2014-September/024841.html they will they try to contact @apiguy and if they fail they might grant ownership transfer
That said, it might be simpler to create a new fork named flask-classier (or something) :8ball:
I suggest you just rename your work and that's that. Maybe call it flask-classful for maximum confusion in the ecosystem.
FYI, pypi ownership transfer issue was accepted https://sourceforge.net/p/pypi/support-requests/591/
FYI, v0.8.0 has just been released https://github.com/teracyhq/flask-classy/blob/master/CHANGELOG.md#2016-02-16-hoat-le-hoatleteracycom
To clarify, it seems that you have not yet been granted pypi access? And the "0.8.0 released" does not mean "released on pypi", but rather "tagged in github"?
@mapleoin yes, I meant github tagged, it will be pypi released when I got pypi ownership transfer.
https://sourceforge.net/p/pypi/support-requests/591/ closed with response:
The owner has responded that this is not an abandoned project.
Did the pypi guys ignore the absence of activity on this repo ? I fail to see how this is not abandoned considering the lack of commits for over a year and a half.
thank you guys, let's go with flask-classful then, I'll update on this issue when it's done.
hello guys, let's make it clear with this change. Please let me know if there is any problem with the changes here: https://github.com/teracyhq/flask-classful/pull/13 ?
hello guys, rename done:
pypi: https://pypi.python.org/pypi/Flask-Classful docs: http://flask-classful.teracy.org/
Awesome, when any of us get some time we could also submit it to http://flask.pocoo.org/extensions/ http://flask-menu.readthedocs.org/en/latest/