Django-rest-framework: Django REST framework as a Github organization

[maryokhin]

I noticed that recently a lot of packages are moving away from the core to different repositories. While I think that is the right way to go, the packages are kind of drifting away in various directions. Of course, I can read the documentation to find the links, but as a casual user I can't just poke around Github and find them. The framework is getting bigger, has docs, a website and now a growing network of packages.
For example, this is Django's organization.

Why I thought it is important now, is because before all the links and package repos have settled down it might be a good idea to think about. You can start throwing shoes at me now :)

[tomchristie]

Yeah def worth considering.
Not sure how I'd feel about it, and adds a whole new question of what does and what doesn't get an org repo, but clearly a possibility.

[tomchristie]

This org should also include the tutorial. https://github.com/tomchristie/rest-framework-tutorial

[xordoquy]

We should think a way so that the code for each end of tutorial's part are provided, not just the last one.

[tomchristie]

We certainly _could_ do, (eg ensure that it is commit-by-commit reproduction of each of the 6 stages, and rebase when needed to keep it up to date) although it would increase it's maintenance load significantly.

Flip side of course is that although we've had higher churn during the 3.0 release it oughta settle down again now with not too many changes.

[sheppard]

FWIW, it looks like GitHub will automatically redirect links to a moved/renamed repository (even after an ownership transfer) - as long as you don't replace it with a new placeholder repository (which would otherwise make sense). The one really awkward thing though is that @tomchristie wouldn't be able to fork the moved DRF repos without breaking the redirects. I tried this out on a test repository:

• Create a repository under my account.
• Move repo to an org account -> Redirect automatically set up
• Create placeholder repo in my repository with same name as original -> No redirect (obviously)
• Delete placeholder repo -> Redirect works again (!)
• Fork org repo to my account -> No redirect (since fork has same name as original location)
• Rename fork so it doesn't match org repo -> Redirect still goes to fork
• Delete fork -> Redirect goes back to org repo.

[xordoquy]

Bumping the issue. Def makes sense. Sentry has moved to an organization a while ago as well.

[tomchristie]

Becoming an org I'm totally happy with. I think we should tie that to a major release. I don't see any particular reason why that couldn't be the next one, or else have it be the one in which the last bits of kickstarter work reach completion, as a milestone marker. "Okay this project belongs to the community now".

I think this issue is distinct from third party packages - I don't really want to see those under the org but we can absolutely do a way better job of surfacing them and keeping it current. A big prominent table in the docs that is automatically populated from django packages would help there.

[xordoquy]

I think I need to think a bit more about how we could handle the 3rd party packages and how we could help them for the version upgrades.

[tomchristie]

I've milestoned this for 3.2.0 for now, but it may drop to 3.3.0.

[ar45]

http://git-scm.com/docs/git-submodule is the way to go for third party apps

[xordoquy]

@ar45 submodules are something different. They are to simulate a single repository when there are several of them.
We don't want to include 3rd parties in the DRF release but make their life easier while DRF evolves.

[tomchristie]

Bumping this for consideration.

[tomchristie]

Strongly considering moving us over to https://github.com/encode

[auvipy]

tom, move forward :+1: that would also highlight the mission of encode

[tomchristie]

Done.

[xordoquy]

Thank you.

[auvipy]

it would be nice to see more drf related projects under encode umbrella :)