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

State of Repo #568

Open
wadewilliams opened this issue Sep 7, 2019 · 17 comments
Open

State of Repo #568

wadewilliams opened this issue Sep 7, 2019 · 17 comments

Comments

@wadewilliams
Copy link

wadewilliams commented Sep 7, 2019

Just curious how maintained this repo is. No CONTRIBUTORS.md and a lot of open issues. We're happy to help out if help's needed.

@Raisins
Copy link

Raisins commented Sep 9, 2019

The repo is on pause and is currently unsupported. The readme will be updated

@auvipy
Copy link

auvipy commented Nov 8, 2019

I am going to vendor this packge on one of my package named drf-extensions

@iMerica
Copy link

iMerica commented Nov 30, 2019

"On pause" doesn't make sense. Transfer the repo to someone willing to maintain it or ask for maintainers in a pinned Github issue.

@auvipy
Copy link

auvipy commented Dec 1, 2019

"On pause" doesn't make sense. Transfer the repo to someone willing to maintain it or ask for maintainers in a pinned Github issue.

I agree with you. I am planning to create a better version of this package as my recent projects need them.

@lggwettmann
Copy link

lggwettmann commented Feb 23, 2020

Hey guys,

Could you please post this on the ReadMe asap? I installed this in a new project only to find out after I'm almost completely done, that I run into bugs and this repo is unmaintained - and it didn't look like it at first sight.

Let's prevent others from making the same mistake. Thanks.

raunaqss added a commit to raunaqss/django-rest-auth that referenced this issue Feb 25, 2020
According to this issue: Tivix#568. This repository is currently unmaintained. This information should be obvious to new users planning to use this package. Hence making this PR.

Thanks.
@cobyrne09
Copy link

cobyrne09 commented Feb 28, 2020

We need to get ahold of Tivix... they have a support contact. I'll give it a try now.

@iMerica
Copy link

iMerica commented Feb 28, 2020

I'm willing to maintain this project under a few conditions:

  • Transfer this to a new Github group called django-rest-auth or alternatively transfer the repo to me and I'll create it.
  • Remove everyone who has commit access, but is not maintaining the repo. This would make everyone sleep better at night.

Otherwise, I can just publish a fork under a new name (e.g django-rest-auth-redux)

@cobyrne09
Copy link

cobyrne09 commented Feb 28, 2020

@iMerica I think it's best we just start over with a new name. I have little faith that Tivix will implement those steps, considering these discussions have been been going on for six months and we haven't heard a word from them.

@cobyrne09
Copy link

cobyrne09 commented Feb 29, 2020

I received this response from Tivix:


I understand the issue. We don't have capacity to support it internally sadly.

Rather than transfer the maintenance to someone else, our preference would be if you and few other like minded people would like to fork and build / push to pypi something like "django-rest-auth-improved" or something like that, we will support it and mark our repo as deprecated and point all users and issue posters to your repo / pypi package.

Thoughts?

It definitely helps to have their buy-in and will help to have an official message directing users to the new repo. So wether through @iMerica's repo or someone else's, we should proceed with this.

@iMerica
Copy link

iMerica commented Feb 29, 2020

Okay that sounds like a "no" to me. I'll just fork it - it's not really important if they "buy-in" or not. This is open source – users vote with their feet.

@iMerica
Copy link

iMerica commented Mar 1, 2020

Dj REST-AUTH is now live. I'm using it in production on a small project and everything is running smoothly so far.

The public API is identical, just a different namespace (dj_rest_auth) to mitigate any confusion.

All bugs and feedback are welcome in the Github issues of that repo.

@shawngustaw
Copy link

shawngustaw commented Mar 6, 2020

@iMerica can you enable issues on the forked repo? If we can get enough eyes on it we should reach out to Tom to point the docs at your fork encode/django-rest-framework#7147

@iMerica
Copy link

iMerica commented Mar 6, 2020

Thanks for bringing this to my attention. Trying to enable it now.

@mohmyo
Copy link

mohmyo commented Mar 20, 2020

Please, update the repo readme with current status and mention the newer fork dj-rest-auth,
Thanks.

@BarnabasSzabolcs
Copy link

BarnabasSzabolcs commented May 30, 2020

OK, I cross-referenced all the PR's to the new repo, let the PR owners know about the new one. Hopefully lots of valuable contribution will not get lost and will get merged to the maintained codebase. (Some of those PR's I'd also need a lot.)

@iMerica thanks for creating the new repo!

Best of luck,
Barney

@mohmyo
Copy link

mohmyo commented Jul 17, 2020

We are about a year-long and the readme is not updated till now! unbelievable!
Stop the confusion for new ppl coming in and add a clear statement about the repo on the readme file

@weslord
Copy link
Contributor

weslord commented Feb 24, 2022

It looks like a deprecation message with a link to the the actively maintained fork (https://github.com/iMerica/dj-rest-auth) was added to the wrong repo by mistake:

I've duplicated that commit in a PR here: #657

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

10 participants