regarding a 'set of projects' it would be neat if we could reserve fedora-coreos* named projects to be accessible to the group members only and disallow anyone outside of the group from creating fedora-coreos* projects. I don't know if that's technically possible though.

We don't have a way to do this auotmatically right now.

I can manually make you a project/namespace and manually give users perms to that namespace/project. Would that be usefull now?

Or shall I just let you know when/if we can do this?

We don't have a way to do this auotmatically right now.
I can manually make you a project/namespace and manually give users perms to that namespace/project. Would that be usefull now?

Even if we can't automatically do this can we still set up a group that we then manually sync (can run a command to sync them). That way we can manage membership to the group and then it's easy us to ask you to just sync them without naming specific names.

Or shall I just let you know when/if we can do this?

Maybe the above in between solution would work for now?

We don't have a sync script right now. We don't currently have plans or resources to make one.

We don't have a sync script right now. We don't currently have plans or resources to make one.

I'm not talking about an automated solution.. It could literally be a bash script that:

• get members of FAS group X
• add members of FAS group X to projects A,B,C
• remove any members that aren't in FAS group X from projects A,B,C

@bowlofeggs can you link me to the docs you are making for adding users to communishift ?

On Thu, 2019-09-26 at 15:57 +0000, Dusty Mabe wrote:

@bowlofeggs can you link me to the docs you are making for adding
users to communishift ?=20

They don't exist publicly yet, and may not for a few weeks.

This looks like it needs to have an assignee write a script to do this.

👍

Should we close this one until we figure out how communishift will come back to life?

Due to many outstanding issues in resources, time and other factors (outlined in https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/Q74QYG54MNBCY7UX2GITPAZYKHD6BYFH/ ) we are unable to move forward with setting up an OpenShift cluster at this time. It is unclear how long in the future it may be until this is possible, so we are closing this ticket. We apologize for this inconvenience.