Project location for internal draft repositories
Do we have a place (namespace) where I can create a project to push rather drafty code, e.g. for illustration?
As an example, I would like to share a jupyter notebook internally that has a few bits and pieces across multiple files. It'd be easiest to pack this up into a git repository and push it into a GitLab project.
I've used my own user's namespace for that in the past, but this only works for repositories that are SAFE to share. For jupyter notebooks working with non-SAFE data, it seems risky to push those to a public location as it's relatively easy to make a mistake and include actual data (or notebook output) in a commit.
In my example, I've illustrated how to load data from Thanos and worked with metrics data not SAFE to publish (AI usage data).
I'd like to be able to share a draft internally only, and e.g. push it to a new project under gitlab-com/gl-infra
, so it can be accessed internally without having to set up permissions correctly.
gl-infra
wide
Proposal: - Create a group
gitlab-com/gl-infra/team-member-repositories
and allow team members to create subgroups/projects for internal use here. - Standardize on
gitlab-com/gl-infra/team-member-repositories/$USER/project-xyz
to signal who owns a project - How to clean up? During offboarding?
scalability
wide
Proposal: - Pretty much the same as the above, but scoped to Scalability
- It'd be nice if we could use
gitlab-com/gl-infra/scalability
as a group (it's a project currently), but any other path likegitlab-com/gl-infra/scalability-projects
also works
User $user namespace
Least favorite option - create private project in my own namespace and explicitly grant access to everyone interested. This has the highest overhead in terms of getting permissions right and it's not open to everyone internally by default.
gitlab-com/gl-infra
Create projects in While this is an option, it would significantly pollute the namespace and is hard to manage. Let's not do this.