Group is created : https://accounts.centos.org/group/sig-isa/
I'll create a new gpg keypair and I'll publish public keys to https://www.centos.org/keys/ today or next week. (and update this ticket too)

WRT a dedicated space on https://sigs.centos.org, let us know where the git repository hosting mkdocs is hosted (but probably worth creating one first, so tied to next question) : it's documented on https://sigs.centos.org/guide/documentation/

Same for Gitlab namespace request : https://sigs.centos.org/guide/gitlab/
So select the "simple" or "complex" case scenario from documentation and we can then create namespace like https://gitlab.com/CentOS/ISA and either grant you "owner" at that level (simple case) or use some more complex (like for Automotive SIG)

Dedicated ISA key is ready and published key published on https://www.centos.org/keys/#isa-sig
Let me know about gitlab and we'll proceed

I think we'll start with a simple case scenario for gitlab. Generally speaking, we'll have a /rpms namespace and access control is pretty flat for now. If we need to transition to something more complex eventually, we can.

I'll look at creating a documentation repo once we have the gitlab namespace.

Created : https://gitlab.com/CentOS/isa and mapped to sig-isa ACO/FAS group as owner.

Thanks for the quick turn-around so far!

On the CBS side, I think we're going to start with a project called packages-optimized for CentOS Stream 9. We may have others, but that will get us going for now.

packages-optimized and packages-baseline tags and targets are created in CBS

Thanks @bstinson , I see indeed that tags following the naming convention were created :

isa9s-packages-baseline-candidate
isa9s-packages-baseline-el9sbase-build
isa9s-packages-baseline-release
isa9s-packages-baseline-testing
isa9s-packages-optimized-candidate
isa9s-packages-optimized-el9sopt-build
isa9s-packages-optimized-release
isa9s-packages-optimized-testing

Closing so now this ticket