Skip to content

Define where GitLab-maintained component repositories should live

Problem

As we launched the CI components framework we should start dogfooding components as well as converting CI templates to components. We don't have today a place where to put all new components that can be both shared within gitlab-org projects as well as having the wider community using them.

Eventually these public component repositories will be shown in the Community Catalog, as well as the gitlab-org Namespace Catalog.

Details

TODO

  • Agree where GitLab-maintained components should live. Should they all be under gitlab-org? Should we have sub-groups per category (e.g. gitlab-org/security/)?
  • Create the location, if necessary.
  • Move components to this new location and start dogfooding.
  • Ensure no new CI templates are created and create CI components instead.
Edited by Dov Hershkovitch