On 26/04/17 12:24, Vít Ondruch wrote:
As I promised earlier , the ruby-sig and ruby-packagers-sig were
established, together with ruby-packagers-sig mailing list . Not sure
precisely how this is going to pan out, but lets try this:
1) I would appreciate if we can transform the list of SIG members 
into the ruby-sig FAS group. Therefore, can I ask interested parties to
apply for this group in FAS? As soon as you apply, I will sponsor you
and I'll select a few of you as additional sponsors.
The group's set to invite-only, could you change it in FAS? (Or invite
me, please: username is "domcleal".)
2) Any of you who is maintaining some interesting package should
about (a) adding ruby-packagers-sig group as a administrator of the
package (b) consider moving the ownership of the package to
ruby-packages-sig (but please I hope it won't end up just as a junkyard
of packages you don't have time to maintain anymore ;) ). As of
membership in ruby-packagers-sig, I propose that the minimal level for
sponsoring into this group should be maintenance of 5 ruby related
package and be packager at least 1 year (possibly with some exception,
especially for full time maintainers).
I've got nine or so packages I'd be willing to move/co-maintain with the
SIG, though I'm unsure if the admin or ownership should be changed (will
wait for your fedora-infra question to be answered).
Would setting ownership or admin automatically provide commit access to
members of ruby-packagers-sig?