Question

We're releasing a commercial project in the near future. The plan is to give to the paying users permission to access the project source. Wiki and issue tracking should be preferably free for everyone to see, but that wouldn't be a problem if I was forced to keep it private too.

I know GitHub private repositories and I really like it, but I'm not sure if it would allow me to add every customer as a collaborator. I am also interested in knowing if this approach I'm describing is the best for the scenario I described.

Was it helpful?

Solution

GitHub is perfect for that, look at Unreal Engine 4's recent "Open Source for Customers" approach.

When you give Epic your github username, they automatically add you to their github "Organisation". They have the project there as a private repo, and now I have access to read and clone it.

If I clone it, I have my own private repo copy of it I can work on, and submit pull requests.

I don't believe you need Enterprise to have this feature, if you check their plans you can see:

Collaborators may fork any private repository you’ve added them to without their own paid plan. Their forks do not count against your private repository quota.

OTHER TIPS

so if you want to have the full control of your git repositories,my advices is build your own git repositories manage system:

  1. GitHub Enterprise,available in pre-build ova Virtual Machine format,easy to use and try it free.
  2. stash from Atlassian,another choice should be considered,also you can try it for free.

BitBucket has an entirely different pricing plan you might prefer.

It's every bit as good as GitHub, but lacking the "community" aspect.

Also, free private repo's!

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top