Moving from Jazzband to an independent organization.

[dopry]

We've moved Django OAuth Toolkit from Jazzband to it's own organization. While Jazzband is wonderful for helping bring exposure to projects in need of maintainers, it comes with some constraints that have adversely impacted development.

Specifically,

• CI taking hours or days to run because the entire Jazzband organization shares a github action quota.
• Unable to manage repo settings due to restrictive rights management applied to project maintainers in the jazzband org.

We're going to fly solo for a while, while evaluating efforts like Django Commons as a possible new home. In the interim, I hope to explore a more Django cookie cutter like approach to maintaining OSS projects. With multiple organizations following and working together to develop common best practices for managing organization and projects in a way that grows community and creates continuity of maintainership. Personally, I believe there are a lot of advantages to having a multitude of independent GH organizations for various projects. Community isn't a GH organization. It is us.

This week,, I'll be busy working on the migration of the various project related assets this week and then we can get releases moving again.

If you feel you can lend a hand or help in any way, contributors are always welcome and encouraged to pitch in.