GitLab is very powerful in that you can easily create a repo-only project, but also something like a issues-only project or a project with a public issue tracker but a hidden repository and vice versa (hidden can be turned off or only accessible to members).
We should make this easier to use and have an option when creating new projects to choose from several options and immediately configure this in detail.
Proposal
Improve the new project view to allow for easy selection of different project types.
For different visibility levels, this should offer different options. For instance, for public projects it makes sense to show the 'private-repo, open-issues' template, but not for private projects.
A quick mockup of how something like this would work, as example:
Trello templates are actually based off of specific jobs/use cases (https://trello.com/templates). I wonder if it would make sense to align templates with how users might actually use them, instead of features. It is a way for us to add value by suggesting a setup and features based on use case. Someone might not know that a certain feature exists in GitLab and is perfect for the project they are trying to use us for -- but going by use case, we can recommend it to them. Just an idea. Not sure exactly what the uses cases would be.
Current project settings permissions allow project types:
Issue only
Repository only
Combinations of and only: MRs, Pipelines, Container registry, Git LFS
Wiki only
Snippets only
… and combinations of them. Few individual permissions (of top-level pages) are missing since we added them over time.
We should make this convention-based in any case.
GitLab is moving all development for both GitLab Community Edition
and Enterprise Edition into a single codebase. The current
gitlab-ce repository will become a read-only mirror, without any
proprietary code. All development is moved to the current
gitlab-ee repository, which we will rename to just gitlab in the
coming weeks. As part of this migration, issues will be moved to the
current gitlab-ee project.
If you have any questions about all of this, please ask them in our
dedicated FAQ issue.
Using "gitlab" and "gitlab-ce" would be confusing, so we decided to
rename gitlab-ce to gitlab-foss to make the purpose of this FOSS
repository more clear
I created a merge requests for CE, and this got closed. What do I
need to do?
Everything in the ee/ directory is proprietary. Everything else is
free and open source software. If your merge request does not change
anything in the ee/ directory, the process of contributing changes
is the same as when using the gitlab-ce repository.
Will you accept merge requests on the gitlab-ce/gitlab-foss project
after it has been renamed?
No. Merge requests submitted to this project will be closed automatically.
Will I still be able to view old issues and merge requests in
gitlab-ce/gitlab-foss?
Yes.
How will this affect users of GitLab CE using Omnibus?
No changes will be necessary, as the packages built remain the same.
How will this affect users of GitLab CE that build from source?
Once the project has been renamed, you will need to change your Git
remotes to use this new URL. GitLab will take care of redirecting Git
operations so there is no hard deadline, but we recommend doing this
as soon as the projects have been renamed.
Where can I see a timeline of the remaining steps?