On 1/18/18 8:05 AM, Sam Whited wrote: > In that case I am retracting the compliance suites, we'll never get anything > useful out of these if people keep trying to stall and we can't ever move on > without trying to make them absolutely perfect and have every little thing > that every person wants. > > If someone else wants to start working on them, be my guest, but please do > not simply push through the 2018 ones and then leave them forever, this > doesn't need to just have this PR merged and then be published, it needs > someone who is willing to sheperd them through the process every year (or > possibly the same ones for multiple years since the goal posts keep moving).
Although I shan't address the Last Call / pull request back-and-forth because I haven't tracked it, in general the idea behind the compliance suites was that we'd update them every year. Therefore it didn't matter all that much if the suites for Year X weren't "perfect" (whatever that means) because in Year X+1 we could update the recommendations again to incorporate our latest learnings. As Sam says, this means we need someone to put forward a revised suite every year and shepherd it through the process. In olden days I did this, and more recently Sam volunteered. IMHO treating the intrepid volunteer well is especially important in this case, because it's a thankless task and any oversights can be easily fixed the next year. I'm not saying we should override any processes defined in XEP-0001, but I sense that handing of this relatively unimportant XEP has resulted in hard feelings all around, which is unfortunate and was probably avoidable. Just my two cents. Peter
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
