Hi Stefan, On 19 Jan 2018, at 12:39, Stefan Haun <[email protected]> wrote: > I've read through this thread, though I, too, did not track the process > around updating the compliance suite.
I think not having tracked what’s gone on here may paint a somewhat different picture from having been involved. > My observation: > * The Council (or members thereof) think that they are absolutely right and > their actions lie within the boundaries of XSF regulations. > * Sam I frustrated, because the 2018 compliance suite still is not finished > and change requests are still coming in. This is likely right (although it is finished, in the sense of a patch able to get voted through Council was sitting waiting, if Sam was willing to ok it). > This is not his fault, This is also right, is as much as feeling frustrated is everyone’s right.. > but resulted in (in-)actions by the Council. As a result he is demotivated > and wants to drop the task. This the implication here isn’t right. Council are obliged to do a review of XEPs before voting on them, which they did. While the previous Council failed to get this to vote despite a long period of Sam trying, the current Council had all their feedback addressed other than me, whose feedback was also addressed in a pending PR, and it was all set to advance this week. > Formally the Council may be right. They did not violate any established > process. > > But I see a more strategic question: Does losing Sam as editor and maintainer > for the compliance suite justify the current course of action? Sadly, the current course of action isn’t Council’s, but Sam’s. Council (and by that I mean me, as the person who gave the feedback), gave the feedback over a month before the Council vote, and even prepared a PR so Sam had to do no work in order to get it through. Ultimately, everything was in place for the vote to pass, but for reasons on which I can only speculate, Sam decided he wanted to force the vote to fail. > Is the persistence on adding the feedback worth it? In the general case, it is very dangerous for Council members to feel that they are not able to give feedback, or expect it to be addressed - in a discussion a little while ago on-list, Sam agreed here that Council should give their feedback. > If your answer is yes, what's your argument regarding this: Sam has chosen to step back from the suites, and there’s not a lot we can do to force him to continue with them (nor should we), although for my part I’d be very happy if he changed his mind. > On 2018-01-19 03:38, Peter Saint-Andre wrote: >> 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. > > If the answer is still Yes, then who is going to maintain the suite from now > on? I would be happy for Sam to continue authoring these XEPs, which is why I put the effort in to ensuring that this one was ready with the issues addressed before the Council vote, but as I say above - if Sam does not want to keep doing this, this is not something we can control. >> 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. > > +1 > > This is not about which process or person is right. This is an emotional > problem and to solve it, an act of leadership from the Council is needed. > > Please get Sam back on board! I have been trying for some weeks. I now realise that all the discussions trying to resolve this have happened in the Council MUC (the logs for which are available, but I doubt anyone has any inclination to sift through them), which makes it seem to anyone not following the events that this has come out of the blue, but it would be a mistake to believe that to be the case. /K _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
