#5704 New FAS group for dotnet team
Closed: Fixed 7 years ago Opened 7 years ago by rhea.

Hi there,

could you please create a new fas group for DotNet?

This group would be invite-only for packagers - we are slowly but surely getting close to having necessary tools to be able to create proper packages and could use this to restrict access to pagure.

Best regards,
Radka


Is this just going to be a group to track members of the team?
Or do you plan to use it as a pkgdb group (ie, it will own packages and you have all members of the group able to commit, etc).

pkgdb groups have more requirements and setup than just a fas tracking group....

Yes it will, however we are mostly RH employees and pretty much almost none of us are in the packager group. Would this require us to join the packagers group? And what would be other requirements? I have to admit that I have failed to find any information about groups owning packages... so I was going off of the assumption that one member would have it on their neck.

Could you please point me to some reference then? =]

From the documentation at http://pkgdb2.readthedocs.io/en/latest/groups.html

There are some requirements for the FAS group:

name must end with -sig
must be of type pkgdb
must require people to be in the packager group
must have a mailing list address
must require sponsoring

Doing this will make sure that membership turnover for owning the packages is much easier and also that watching and committing is simpler.

Thank you, in that case we can just take our current group dotnet-sig (I just edited the details to match the requirements) and i'll get our guys (including myself) to go through the checklist and all those things :)

You will need a (private because it may get information on security bugs) mailing list.

We could use the existing dotnet-sig for this, but since it will be private it might not be good for newcomers, etc. So we could do another list, whatever you prefer.

Okay another private mailing list would be cool then, I don't know what are the best naming conventions in this case, which one should remain public and which one private?

We definitely want one public mailing list.

How about leaving the current list alone and making a new 'dotnet-packagers' private list for the pkgdb group?

ok. I have created the dotnet-packagers list. That will need to be set as the list for the fas group. You will also need to create a bugzilla account with the list email address (it will send the confirm to the list, but you can catch that in the moderation queue).

I think that takes care of everything here, if not please re-open or let us know.

:droplet:

@kevin changed the status to Closed

7 years ago

Login to comment on this ticket.

Metadata