>>>>> I propose that each FESCo member should try to work on at least one >>>>> package review per week. Each week at the FESCo meeting, we'll ask >>>>> members which reviews they've worked on in the past week. >>>>> >>>>> It won't be _mandatory_ -- >>>> >>>> [snipped] >>>> As a rule of thumb it's ok, but it should not be mandatory. I think the >>>> FESCo members are already having a lot of work to do and I'm not sure if >>>> everybody has enough spare time for reviews. >>> >>> Absolutely. Besides, if you do call it 'mandatory' you have to start >>> defining what would happen if people don't comply, and the whole thing >>> just gets silly. >>> >>> I'm talking about a 'recommended practice', and just asking people each >>> week which packages they've looked at. Nothing more. >>> >>> And even though people are busy, it shouldn't actually take _that_ long >>> to make progress on reviewing a single package, each week. >>> >> >> http://tinyurl.com/4kt682 >> 1,212 open Package Review bugs > > Woa, > > Thats an amanzing number, I'll put in, or rather repeat, my 2 cents here. > Fedora, like any opensource community, is all about give and take, about tit > for tat. > > I've submitted many, many new packages (100+ I guess) and I've *never* had > any problems in getting them reviewed. > > Of those 1200 pachages awaiting review, 100 block FE_NEEDSPONSOR, so 1100 > are normal reviews submitted by people which are already contributers! Lets > say every contributer has on average 2 packages waiting for review, then 2 > have 550 contributers for whom the review queue is a problem, if all of > those 550 submitters would review only 2 packages, then the entire normal > review queue is gone! There's also 100 odd packages with a fedora-cvs flag of some sort set so should either be done and the bug needs closing or nearly done. Peter -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
