On 19 January 2018 at 13:58, Stefan Haun <[email protected]> wrote: >> While the >> previous Council failed to get this to vote despite a long period of >> Sam trying, > > > In my view, this is the key reason for being in the current situation. > Was this failure to get the vote in time addressed or taken into account? > Did somebody apologize for delaying the vote or making Sam miss the > end-of-2017-deadline?
3/5 of the current Council were on the previous one, including both Sam and me. Kev is one of the minority (along with Georg) who can blame the previous Council without hypocrisy. Sam did indeed work hard to try to get the XEP through the process in the last Council, but I don't think any of us really took into account that the process to push a XEP from Experimental through Proposed and into Draft takes a substantial amount of time, and is very heavily reliant on everyone in Council voting fairly rapidly. The worst case, I think, is seven weeks: A week before the Council meet. A vote on issuing the Last Call (and moving to Proposed), which, if Council members aren't prepared, drops onto voting "on list", and can potentially then rely on a two week timeout. A two week Last Call. A second vote, this time to move to Draft. Again, this can lead to a two-week timeout. Of this, if the Council term expires after the first vote has been called, everything restarts. The majority of this time is down to late (or no) voting by Council members. This is why I'm trying to issue an agenda 24 hours in advance, to help Council members prepare properly, so they're able to vote in the meeting and avoid the delays. I'm also trying to recap outstanding votes in the meetings to try to encourage voting within a week. I think there's some evidence of this working, but the fact remains that it only takes one person to forget to vote and a vote takes two weeks. (And worse, it's *very* easy to then not notice the two weeks is up and let it drag on to three or more, because we have no formal tracking - making it somewhat understandable that it's very easy to miss voting). As Chair, I am very much aware of what the problems are here, and I'm trying to address these. It is not very convenient that a restart can cause a further 6 weeks of delay. But if the rest of the process is working - that is, if everyone on Council are doing their job and being prepared to vote - then it's going to be a 2-3 week process with a potential 2 week delay in it happens to cross a Council boundary. I don't think that Council people not doing their job (even if this is made harder than it should be) should mean we get to pick and choose which bits of process we follow. But that said, I'd reiterate that our process is not set in stone. It is as easy to alter as any other XEP (in this case it'd need a vote by Board, mind). Dave. _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
