GitHub Plans and Accounts - My notes, are they correct?

[shoulders]

Select Topic Area

Question

Body

Hi

I am trying to work out all of the basics of GitHubs plans and accounts and so I did a bit of reading etc and I came up with these TL;DR notes.

Can the community just have a look over them to make sure they are correct and I have not made any mistakes or even just missed the obvious ones.

The idea behind this is so and a single developer I understand where to start and what to do when I need to upgrade.

Thanks in advance

TL;DR

• Public repositories

  • Host open source projects in public GitHub repositories, accessible via web or command line.
  • Public repositories are accessible to anyone at GitHub.com.
  • Collaborators and members for public repositories are always unlimited irrespective of your personal plan (e.g. free, Pro) or your organization's plan (e.g. Free, teams, Enterprise)

• Private repositories

  • Host code in private GitHub repositories, accessible via appliance, web, and command line.
  • Private repositories are only accessible to you and people you share them with.
  • Collaborators and members for private repositories:
    • On a GitHub personal account (Free, Pro), collaborators and members are unlimited.
    • On a GitHub Free Organization, collaborators and members are unlimited.
    • Although collaborators and organization members serve different purposes within GitHub, for organizations subscribed to GitHub Team collaborators must occupy a paid seat in order to access private repositories. Organization members always require a paid seat.
    • If you decide to upgrade your organization from GitHub Free to GitHub Team, you must add a paid seat for each organization member as well as each collaborator for them to keep access.
      • No data will be lost, just access for those who do not have a seat.
      • You only need to buy seats for those users that you want to have access to the organizations repositories going forward, not for everybody who has every made a change or contribution to any of the organization's repositories.
    • Upgrading your account's plan - GitHub Docs - If you'd like additional users to have access to your GitHub Team organization's private repositories, you can purchase more seats anytime.

• Pricing Plans

  • All pricing @ GitHub is done on a per-user basis.
  • Personal accounts and organization seats are classed as separate Billing entities.
  • If you upgrade your personal account from GitHub Free to the GitHub Pro plan then you can:
    • get additional features for your personal Private repositories such as Pages and Wikis
    • you will also get more Git features and various Code workflow enhancements for both your Public and Private repositories.
  • If you use GitHub Team for your organization you will also get enhancements for your Public and Private repositories as-well as improved organization management better granular user role control.

• User Accounts

  • A user account is for one person and some times is referred to as a `Personal Account`.
  • A person only needs one user account. You only need one Facebook account right!
  • This account can be used to host all of a user's project and also be used to login in to organizations.
  • There are currently 2 pricing plans for an `personal` account, Free and Pro.
  • If you are an individual developers with no commercial angle, then you should just use a personal/single account for all of your repositories.
  • If you need more actions, features and that other stuff then you can upgrade your account to Pro.
  • I would use my personal account where I need to fork a repo to push some fixes to someone else's code.
  • A user can own more than one organization.

• Organizations

  • Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once, with sophisticated security and administrative features.
  • GitHub Free allows you to add as many members and collaborators to your organization as you’d like at no charge.
  • There are currently 3 pricing plans for an account, Free, Team and Enterprise.
  • Having an organization for your company ensures that the assets are not controlled by single member of staff under their personal account.
  • You should use an organization for your code if:
    • If you are a company and you are making software.
    • If you are a individual developer or a company that is going to sell software.
    • You will need to collaborate with team members or other entities.
    • Your software project(s) will be large.
  • Features:
    • Allow for collaboration between team members and other entities.
    • Allows more granular permissions for repositories that belong to the organization.
    • An organisation can have public and private members. Public members do not count towards your organizations seats.
    • Allow for for organising repositories by groups such as; Company, Code Language, Software Type, etc.....
  • You can convert your personal account into an organization (but this is not best practice).
  • You can identify an organization easily because thy have a people tab.
  • Organizations can have more than one organization owner to avoid lapses in ownership.

• Teams

  • The concept of Teams in GitHub allows for greater flexibility for collaboration and integration, as well as separation of repositories and permissions.

• Enterprise accounts

  • Are for very large companies, or those teams that need to manage multiple organisations but all under the same company banner.
  • Pricing is done per member, each member requires a seat/license, I am assuming there will always be at leats one member.

• Discounts

  • Discounted plans for GitHub accounts - GitHub Docs - GitHub provides discounts to students, educators, educational institutions, nonprofits, and libraries.

[jessiecollins185]

Nice summary! I had a similar learning curve when setting up repos for pearl lemon games GitHub’s pricing and seat rules can definitely trip you up at first.

[shoulders]

I have a bigger article I have been working on. https://quantumwarp.com/kb/articles/26-programming/1043-my-github-notes