Note that the ML should be private since it will receive bug report and potentially security sensitive ones, so having its name matched the FAS group may be a good idea, so that it doesn't conflict with a public list for discussion.

Ah, does that explain why there is both python-devel and python-sig, for instance? Then yes, let's make rust the public one, then a private rust-sig is fine with me. OK, @ignatenkobrain?

@jistone That sounds like a reasonable plan to me.

fine with me, rust-sig for private and rust for public.

ok. I have:

• Added the rust-sig pkgdb group (requires packager to join and has list of rust-sig@lists.fedoraproject.org)
• Added the rust-sig list (closed archiving, requires confim to subscribe).

If you can now create the 'rust-sig@lists.fedoraproject.org' bugzilla address, everything should be setup.

:house_with_garden:

ok. I have:

• Added the rust-sig pkgdb group (requires packager to join and has list of rust-sig@lists.fedoraproject.org)
• Added the rust-sig list (closed archiving, requires confim to subscribe).

If you can now create the 'rust-sig@lists.fedoraproject.org' bugzilla address, everything should be setup.

:house_with_garden: