So, there's 2 ways we can set this up:

1. Just setup go-sig pseuto user. This would allow you to have a list that gets cc'ed on all bugs, etc.

2. Setup a real go-sig group where the sig can be point of contact/admin on packages and adding/removing people from the group allows them to commit. This would also have a (private) mailing list.

Let me know and I will get it setup. Sorry for the delay here. ;(

Heh I don't know, can't we have both? I'd like it to be a bit like Perl SIG, where bugs are CCed to the mailing list and people from the group can have commit rights on any packages. It looks like #2 I guess.

ok. It should be setup from our side, but there's a few more steps for you.

1. Go to bugzilla.redhat.com and make a new 'go-sig@lists.fedoraproject.org' account. It will send the intial token/password to the list, but it should be caught in moderation, so you can read it there and then delete it.

2. Add folks to the go-sig fas group and email list as you like (but note that the list is set to be private because it can be cc'ed on security bugs).

3. Set go-sig to be admin (to allow it to manage who can commit) or just commit (to get cced on bugs).

Let us know if you need anything further.

Couple of questions:

• I added my team in FAS, will they automatically show up in https://src.fedoraproject.org/group/go-sig after a while?

• I created the 'go-sig@lists.fedoraproject.org' account but no message appeared on the moderation.

• I didn't understand part 3: "Set go-sig to be admin (to allow it to manage who can commit) or just commit (to get cced on bugs). " Where should I set go-sig to be admin or commit?

Couple of questions:

I added my team in FAS, will they automatically show up in https://src.fedoraproject.org/group/go-sig after a while?

They will show up in the group as soon as they logout and back on. Group membership is checked at login time.

I created the 'go-sig@lists.fedoraproject.org' account but no message appeared on the moderation.

Might take a little bit, sometimes bugzilla is slow.

I didn't understand part 3: "Set go-sig to be admin (to allow it to manage who can commit) or just commit (to get cced on bugs). " Where should I set go-sig to be admin or commit?

On the packages you want it to control commit acls for or where you want it to get cc'ed on bugs.
ie, the packages managed by the sig.

Oh yes I already started the last part then, it's all good. The only problem is that the processus is manual and we can't mass add admin rights for all Golang packagis :/

Thanks for all your help!