Public Project / Default Permissions with GitLab

Question

I compare Gitorious with Gitlab, and although I like Gitlab a lot, it has a very fundamental problem. For each new repository, the creator needs to manage those who have access to this repository.

Our model is pretty simple: if you have access to gitlab, you have access to most repositories. Only a few repositories will be closed, and we won’t even need them in gitlab. Flexible support for this model, but I have not seen any way to do this on gitlab.

Can this be done? If so, how?

Answer 1

Public repositories are what developers were resistant to adding support for. They do not want gitlab to be a competitor to github. See https://github.com/gitlabhq/gitlabhq/issues/12

Team support is something that is still under development. Let's hope that your requests will be realized at some point. See: https://github.com/gitlabhq/gitlabhq/issues/739

Until the best support for the team is realized, the best option would be to use a script: https://gist.github.com/1722391 to add users to all projects. This is the approach that I am currently using.

or use the new rake commands to bulk add users:

rake add_user_to_project_teams[email] # Add user to as a developer to all projects rake add_users_to_project_teams # Add all users to all projects, system administrators are added as masters 

Answer 2

There are also two Rake tasks for Gitlab that can control the mass addition of users to the repository:

 rake add_user_to_project_teams[email] # Add user to as a developer to all projects rake add_users_to_project_teams # Add all users to all projects, system administrators are added as masters 

Answer 3

Gitlab fork has appeared, allowing public repositories: https://github.com/ArthurHoaro/Public-GitLab

Answer 4

Community projects allowed with GitLab 6.2.

Public projects were the most sought-after feature in the GitLab user group, see http://gitlab.uservoice.com/forums/176466-general/suggestions/3159951-allow-public-repositories