Hello,
GitHub free plan won’t allow enforcing rules on private repos
Check here:
It’s not a blocker. But I want to start this topic.
Can / should we make website / infra repos public when they will be usable?
Are we OK to have all repos public in the bemanproject org?
I don’t see a reason to have private repo, but I also don’t see the need to ban them out-right.
There’s no secret we will be hiding in the website repo, I would say we should make it public. It would also be easier for external contributors to contribute small changes like typo-fixes.
One use case I can think of is if someone wanted a private repo to start development before revealing to the world. But I think they could do it under their own name and xfer later. It does make the rules a bit of a big bang later.
Bigger topic though is would it be worth it to have a paid account for the project. If there are other advantages than this and the costs aren’t crazy it might be worth considering. I mean we’ve allocated $$ for marketing…
The only thing I can think of is codespace caching, that is a paid-only functionality that caches GitHub codespaces (basically vscode on the web) so that it takes minimal time to launch. But I don’t know if any member is actively using codespace. Also, we are essentially buying a development environment for contributors through this service, which may be prone to abuse.
Other than that, (for public repos) GitHub Actions is free (and there’s currently no reason to use any advanced runners), Github Pages is free, the base GitHub functionality as source code management and code review is free, GitHub package is free if we are interested in Host docker images for cross-compiler CI test - #5 by river . I can’t think of a good reason to get a paid org account.
This is valid, but I think the free-tier for private repos are good enough for a bootstrap.
One use case I can think of is if someone wanted a private repo to start development before revealing to the world. But I think they could do it under their own name and xfer later. It does make the rules a bit of a big bang later.
@Jeff-Garland , someone can do this with private repo inside Beman org. But we cannot enforce rules like PR reviews etc. Basically, anybody can merge anything, regardless of the CODEOWNERS file. But the usage of private repos is possible, and if it’s about a PoC, then probably we don’t care about such rules.
Bigger topic though is would it be worth it to have a paid account for the project.
Right. Here is a comparison - Pricing · Plans for every developer · GitHub
Private repos on free account cannot have:
Quick check: 21USD per user/month is too much is we need to multiply by 50 (I hope I understand their pricing logic).
oh my, that’s a lot of $s
Edit: We probably qualify for GitHub for Nonprofits
But again I don’t think this is worth it…
I don’t really see us having a long-lasting GitHub private repo…
I think we should drop for the moment this topic. It’s too expensive.
