This repository has been archived by the owner on Jun 17, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 189
transfer ownership ? #6
Comments
This needs to happen. @dnozay have you found a version that works with Django 1.7? |
@christopherhan - haven't checked - still on 1.6 for my current work. |
@christopherhan my fork works on django 1.7. |
Sorry to hijack this thread but: @Fantomas42 might you enable the issues on your fork? It's gaining traction since it was listed at django-packages. Also a honest +1 to transfer the ownership. Or may be setup an organization for this? |
@tutuca this fork is done only to maintain the project. Pull-request are open, but not the issues. Because I don't want to stack the issues forever, without solutions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi @brosner,
when I look at https://pypi.python.org/pypi/django-tagging, there is no
real way to see where the project is actually maintained.
I see from the network graph that more is happening on @Fantomas42's fork,
but there is no issue tracker there. It would be great if the repo was
transferred to folks that are maintaining it. And if the SVN repo on google + package metadata was updated with new location. @insin may be able to help with that.
several ways to achieve that:
https://help.github.com/articles/how-to-transfer-a-repository
Is that something you think is possible?
Thank you,
damien
The text was updated successfully, but these errors were encountered: