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

Django REST framework as a Github organization #2162

Closed
maryokhin opened this Issue Nov 29, 2014 · 17 comments

Comments

Projects
None yet
6 participants
@maryokhin
Copy link
Contributor

maryokhin commented Nov 29, 2014

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

This comment has been minimized.

Copy link
Member

tomchristie commented Nov 29, 2014

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 tomchristie added the Process label Nov 29, 2014

@tomchristie tomchristie referenced this issue Dec 3, 2014

Closed

Maintainers for Q1, 2015 #2190

5 of 5 tasks complete
@tomchristie

This comment has been minimized.

Copy link
Member

tomchristie commented Dec 18, 2014

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

@xordoquy

This comment has been minimized.

Copy link
Collaborator

xordoquy commented Dec 18, 2014

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

@tomchristie

This comment has been minimized.

Copy link
Member

tomchristie commented Dec 18, 2014

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

This comment has been minimized.

Copy link
Contributor

sheppard commented Feb 13, 2015

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

This comment has been minimized.

Copy link
Collaborator

xordoquy commented Jun 1, 2015

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

@tomchristie

This comment has been minimized.

Copy link
Member

tomchristie commented Jun 1, 2015

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

This comment has been minimized.

Copy link
Collaborator

xordoquy commented Jun 1, 2015

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 tomchristie added this to the 3.2.0 Release milestone Jun 2, 2015

@tomchristie

This comment has been minimized.

Copy link
Member

tomchristie commented Jun 2, 2015

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

@tomchristie tomchristie modified the milestones: 3.2.0 Release, 3.3.0 Jun 3, 2015

@ar45

This comment has been minimized.

Copy link

ar45 commented Aug 13, 2015

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

@xordoquy

This comment has been minimized.

Copy link
Collaborator

xordoquy commented Aug 13, 2015

@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 tomchristie removed this from the 3.3.0 Release milestone Sep 17, 2015

@tomchristie

This comment has been minimized.

Copy link
Member

tomchristie commented Mar 22, 2017

Bumping this for consideration.

@tomchristie tomchristie added this to the 3.6.3 Release milestone Mar 22, 2017

@tomchristie

This comment has been minimized.

Copy link
Member

tomchristie commented Mar 22, 2017

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

@auvipy

This comment has been minimized.

Copy link
Contributor

auvipy commented Mar 28, 2017

tom, move forward 👍 that would also highlight the mission of encode

@tomchristie

This comment has been minimized.

Copy link
Member

tomchristie commented Mar 31, 2017

Done.

@xordoquy

This comment has been minimized.

Copy link
Collaborator

xordoquy commented Mar 31, 2017

Thank you.

@auvipy

This comment has been minimized.

Copy link
Contributor

auvipy commented Apr 1, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment