Sounds reasonable.

@spot, @jamatos, @qulogic, @ellert ?

I think this is an excellent idea.

I also think that this is an excellent idea. :-)

This sounds reasonable to me too. I appreciate your efforts, and those of the other maintainers you mentioned, and this seems like an appropriate request to make mass rebuilds practical.

You mention not needing the “usual bells and whistles of a proper SIG,” but as far as I can tell the minimum requirement for an “R SIG” is basically just creating a wiki page and adding it to Category:PackagingSIGS. That seems like a worthwhile step for documentation and discoverability, even if the wiki page pretty much says “there is a packaging group, and that’s all.” What do you think?

I had in mind that it was more complicated, but if having a wiki page is the minimum requirement, then I'll gladly write it. :)

(thumbs up, apparently there's no undo :))

Here we go: https://fedoraproject.org/wiki/SIGs/R

Yay, a SIG for pirates!

:thumbsup:

all the usual bells and whistles of a proper SIG

I'm not sure what you mean here - because if you want a FAS / dist-git group that will be added as co-maintainer to all R packages, then you also need 1) a bugzilla account and 2) a mailing list, where 1) will be the bugzilla account for the dist-git group and 2) the email address you need for 1).

To me, that sounds you already need all the whistles and bells?

I meant things like mission statement, plan of action, IRC channel, meetings... About the mailing list, in practice we use the official R-SIG-Fedora list provided by the R Project, and I think that it's best to keep it in that way.

Packager groups require a private list for their emails, since they get all bugzilla emails (including even private / security related ones). Also, all the bugzilla commits tend to drown out non bugzilla threads...

A SIG sounds good to me; I've been quite far behind on my R packages unfortunately.

Apart from the ACKs and the SIG boostrapped in our wiki, is anything else required from our side?

You'll need to file a ticket with fedora-infra similar to this one I filed for the java-maint-sig (:rip:)
https://pagure.io/fedora-infrastructure/issue/8902

IIRC, this involves 4 steps:

1) infra will create a private mailing list that can be associated with the group's bugzilla account
2) you need to set up a bugzilla account for the the private mailing list address you got
3) infra will create a FAS / dist-git group on src.fedoraproject.org that you can manage from accounts.fedoraproject.org
4) infra will associate the bugzilla account you created with the FAS / dist-git group

@iucar ping, ticket in fedora-infra?

Here: https://pagure.io/fedora-infrastructure/issue/10800

It's a great idea :)

@spot, @jamatos, @qulogic, @ellert, @aekoroglu We have a new mailing list (subscribe!), and a FAS group (I just added you all, but Pagure warned me that you probably have to log out and in again to see the change). I asked Kevin for help to mass-add the group to R, rpy, rkward and all the R packages. Please let us know if I'm missing something.

As for the last step, you probably will want to ask fesco to have the new SIG policy also apply to the R SIG:

https://pagure.io/fesco/issue/2837

Closing in favor of https://pagure.io/fedora-infrastructure/issue/10800