Requesting a New GitHub Org

Google manages quite a few organizations on GitHub (go/github/orgs), and with the amount of open source code that we release, we regularly get requests for new ones. But adding new orgs comes with both management and monetary costs.

When a new organization is warranted, we’re happy to help set that up and assist you in using it effectively. But a project may be better suited for one of our existing GitHub orgs, or perhaps a different source control system altogether.

IMPORTANT: To request a new organization, write a detailed document that addresses the following questions.

Why is a new organization needed?

Describe your intended use of the organization in detail. Explain why your goals cannot be achieved with new repositories in an existing org (go/github/orgs).

Keep in mind that projects can always be moved out into a separate organization down the road. This is in fact exactly what happened with kubernetes, bazelbuild and others, all of which started out in one of our shared organizations. Repository moves between organizations are relatively seamless – GitHub will automatically redirect web and git traffic, and everything on the repo itself (stars, forks, issues, pull requests) remain intact.

Who is going to be responsible for this organization?

Identify two full time Googlers that will be responsible for this organization. These two persons, and generally only these two (not including “Google GitHub Owner”), should be added as owners of the organization (see go/github-org-owners#owners). They will be responsible for setting up the organization profile, inviting the rest of the team to join the organization, making sure the entire team understands the rules of engagement for GitHub, etc. Make sure that these two people understand these responsibilities and have the time and resources to dedicate to it.

If and when we receive new go/releasing requests that ask for a repo in this organization, we will delegate the “GitHub Owner” approval bit to these owners. If you would prefer, you can also setup a group which we will assign that bit to.

If and when organization owners leave Google, you should have a plan in place to replace them with someone new. If an org becomes truly abandoned and we’re unable to find someone to maintain it, we will likely look at turning it down and moving the repos elsewhere.

How large do you anticipate this org being?

  • How many people will you be adding to the org at launch? Within six months?
  • How many repos will you be adding at launch? Within six months?
  • How heavily is this org going to be promoted? Is this something big like TensorFlow or a more low-key release?

Do you anticipate needing private repositories?

Googlers’ use of GitHub is generally restricted to open source projects, which means at some point all projects should be publicly available. However, there are legitimate uses for private repositories, such as timing the release of a new project with a particular announcement.

Depending on your exact needs, there are a few different options for handling private repositories, documented at go/github-billing. If you do anticipate needing private repos, please explain why and which private hosting option you are considering.

Follow go/github-org-owners

Confirm that you’ve read and will comply with go/github-org-owners, and let us know if you have any questions about those policies.

Once the document is complete, send it to emailremoved@ and CC your director, who will need to confirm their commitment to staffing and supporting this organization.

Except as otherwise noted, the content of this page is licensed under CC-BY-4.0 license. Third-party product names and logos may be the trademarks of their respective owners.