NOTE

If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.

Describe what you would like us to do:

We are working with Ellen O'Carroll our product owner to get the Community Design Team at Red Hat up and running. I would like to reorganize the Fedora Design subgroup in GitLab to help the Red Hat CDT designers track their work in the space and to support this effort.

This is how the Fedora Design team GitLab set up currently looks like:

• Fedora Group
• Fedora Design Team Subgroup
  • Fedora Design SubSubgroup #1
  • Fedora Design SubSubgroup #2
  • Fedora Design Repo #1
  • ...
  • Community Design Team (CDT) Subgroup
  • CDT Issues repo
  • CDT Private Issues repo

The CDT Private Issues repo is where I think there might be an issue. Mind you, there is not likely to be anything earth shatteringly private in these issues, but this is just a space where we will very occasionally track tasks that are for Red Hat internal tasks that we do only very occasionally. We can get a unified view of both public and private tasks in the CDT subgroup issues tab.

Where the issue is: GitLab's inheritance based group membership means anyone granted high level access who is a community member and not necessarily a RHT employee would have access to the private issues repo.

I think if the GitLab is rearranged this way it would address this:

• Fedora Goup
• Design Subgroup
  • Fedora Design Team Subgroup
  • Fedora Design Subsubgroup #1
  • Fedora Design SubSubgroup #2
  • Fedora Design Repo #1
  • Community Design Team Subgroup
  • CDT Issues repo
  • CDT Private Issues repo

This way I think we can manage the permissions better. The team leadership (myself, Ellen, Madeline, and Emma) can have elevated privs at the "Design" level, and then we can also easily grant non-RHT community members elevated privs for the Fedora Design Team subgroup under that without impacting the CDT repos. Also, we can track and refer to issues across the CDT and FDT subgroups which would be quite nice.

I just don't know how to go about making this change. Ideas?

When do you need this to be done by? (YYYY/MM/DD)

Not a huge rush but we've just started tracking our tasks using the existing setup. I have a couple private issues but it's not earth shattering if they get exposed to individual external contribs for the moment.