is it worth to move django-oauth-toolkit into oauthlib org?

[JonathanHuot]

Hi jazzband-roadies,

Two years ago, the idan/oauthlib was moved to the newly created oauthlib github org. The goal was to have more contributors and to give the project more activity. So far, we have released 6 versions with a lot of bug fixes and new features, see https://github.com/oauthlib/oauthlib/releases.

However, we are always looking for contributors, and one discussion was started there https://github.com/oauthlib/oauthlib/issues/678.

Because oauthlib/oauthlib is only a framework, most of the developers are using it without knowing it, and they are usually trying to fix problems in the downstream applications (django-oauth-toolkit, flask-dance, requests-oauthlib, and so on) instead of the upstream framework (oauthlib).

If django-oauth-toolkit and other downstream applications can be under the same github org, I'd expect more developers have a look there and propose features implementations at the right place. Also, the oauthlib framework contributors could also participate to the downstream applications more easily.

So, the question is: for the best of the two github orgs, is it worth to move jazzband/django-oauth-toolkit into oauthlib/django-oauth-toolkit ?

Thanks

[auvipy]

IMHO, if it gets more care there, I think it should be.

[jezdez]

I've replied in https://github.com/oauthlib/oauthlib/issues/678 and asked @jleclanche to get approval from all Jazzband members and contributors who have contributed since the move to Jazzband. Here's the list: https://github.com/jazzband/django-oauth-toolkit/compare/master@%7B04-18-18%7D...master