Github Repository Organization

Separate repositories for separate things

Create separate git repositories for projects that are independently-developed or only loosely coupled with each other.

Same repository for same things

Have a significantly new version of your model or project? Please use

Many similar projects can be grouped under their own “organization”

Since tags or folders within organizations is an outstanding feature request on GitHub, code managers should consider moving projects with multiple repositories ot their own “organization”. This creates a dedicated domain where people can find these projects rather than having to sift through many irrelevant ones.

This is also a good practice for organizations with more than a dozen or so projects.

There are many good discussions of what should be in separate repositories versus the same on Stack Exchange and other mediums

Transparency

Please make sure it is obvious who is contributing to the project and who they are affiliated with. To that end:

  • Ensure team-members populate their name, email, and headshot.
  • Make team membership public

Resources

Related Projects

Relevant Articles

Adding a Project

What to do if you are interested in having a project listed here.

Github Workflow

Recommended practice for Github workflow.

Open Source Licensing

The short and sweet of software licensing.