XMPP Council - 2019-11-07

  1. Kev Just reviewed https://xmpp.org/extensions/xep-0423.html . Just in case I don't make today's meeting, I'm premptively +1 on moving 0.3 to Draft.
  2. Ge0rG Phew.
  3. Dave Cridland OK.
  4. Dave Cridland 1) Roll Call
  5. Kev 2, bacon.
  6. Dave Cridland Had 2 bacon ones for lunch today, with extra thick bacon. Yummy.
  7. Dave Cridland Ge0rG, Link Mauve, jonas’ ?
  8. Ge0rG Kevin Bacon?
  9. Ge0rG ,o/
  10. Link Mauve Yes, I’m here.
  11. jonas’ .
  12. jonas’ am here
  13. Dave Cridland Well, that's a full house.
  14. jonas’ Bacon Buger!
  15. Dave Cridland 2) Agenda Bashing
  16. jonas’ Bacon Burger!
  17. Link Mauve I’m hungry now.
  18. Link Mauve After failing at making mochi. :(
  19. Dave Cridland I'm assuming we just have XEP-0423 to Draft.
  20. Ge0rG Let's add something to the agenda just for the sake of it
  21. Dave Cridland Let's not.
  22. Dave Cridland 3) Item for a vote:
  23. jonas’ I’m +1 on XEP-0423 to Draft
  24. Dave Cridland a) Advance XEP-0423 to Draft.
  25. Ge0rG +1 on XEP-0423 to Draft
  26. Dave Cridland jonas’, Patience.
  27. Link Mauve I’m +1 on XEP-0423 to Draft.
  28. Link Mauve I’m +1 on advancing XEP-0423 to Draft.
  29. Kev +1. And a big thank you to Ge0rG for sticking with this. This is, I think, the most useful CS we've had in as long as I can remember - I think having some sort of nuance really helps.
  30. Link Mauve Indeed!
  31. Dave Cridland Tempting to veto for dramatic purposes, now.
  32. Dave Cridland But no, best not.
  33. Ge0rG Dave Cridland: you could on-list instead and wait until the 20th.
  34. Dave Cridland +1 to advance to Draft. And I agree with Kev, this has been a lot of effort for Ge0rG, but it's resulted in a much better document than we've had for a long time.
  35. Ge0rG Even the 21st.
  36. Ge0rG And announce your vote right before Alex closes the polls.
  37. Ge0rG And then it will get delayed by the MTA and...
  38. Dave Cridland Thanks also to the rest of Council for the extra meeting and being prepared for it.
  39. jonas’ I, too, am happy with the result, but I’m not with (nearly) burning out all CS editors
  40. jonas’ I, too, am happy with the result, but I’m not with (nearly) burning out all CS editors/authors
  41. Dave Cridland So, for the record, a unanimous decision to move CS-2020 to Draft.
  42. Link Mauve \o/
  43. Ge0rG I must admit, there was a period of some days after I started work on 423, where I felt burned out as well.
  44. Dave Cridland 4) Next Meeting
  45. Link Mauve Next week Wednesday as usual?
  46. Link Mauve 16:00Z
  47. Ge0rG +1 for next Wednesday
  48. jonas’ wfm
  49. Dave Cridland Yes, I think so. I'd note that if there is anything to vote now, we'll have to either be able to vote immediately or it'll have to be re-raised by the next Council.
  50. Dave Cridland 5) AOB
  51. jonas’ none from me
  52. Link Mauve None from me either.
  53. Dave Cridland Other than saying how pleased I am to see lots of candidates for Board and Council, nothing from me.
  54. Dave Cridland OK.
  55. Dave Cridland 6) Ite, Meeting Est
  56. Dave Cridland Thanks all.
  57. Link Mauve Thanks all for this exceptional meeting!
  58. jonas’ thanks Dave et al.
  59. jonas’ this was a good move indeed
  60. jonas’ pep., do you want to do the honours?
  61. pep. sure
  62. jonas’ :)
  63. pep. Dave Cridland, what was wrong from not having this meeting and putting it on list? Council members "just" needed to react quickly and not two weeks after :)
  64. Kev Meetings focus the mind, sometimes. We could have onlisted, but this way worked, so ... :)
  65. jonas’ pep., yesterday there was no version to vote on yet
  66. Ge0rG pep.: the Last Call technically only ended last night, and there was the pending PR
  67. jonas’ so there had to be a meeting which started the vote
  68. pep. Ge0rG, ok
  69. jonas’ it was a lucky accident that everyone voted in the meeting and not on-list
  70. Kev We could have started the vote yesterday, on 'whatever version is published tomorrow morning', and all on-listed, but ... this way was better, I think.
  71. Kev Even if I'm not a fan of extra meetings I have to attend :)
  72. Dave Cridland Me neither, but I'm not a fan of starting a vote on a version that's unpublished just for the purpose of ensuring a timetable.
  73. Kev jonas’: I think 'lucky accident' is understating the effort people put in (mostly Ge0rG) to make sure it could happen.
  74. Ge0rG Kev: it was a kind of lucky accident nevertheless, because my calculation of the moment when to submit the XEP was off by two weeks.
  75. jonas’ Kev, sorry, yes
  76. jonas’ I didn’t mean to diminish that
  77. jonas’ I was looking at it from a concurrency architectural perspective, where a certain sequence of events is almost always an accident
  78. jonas’ I’m too deep in concurrent code at the moment
  79. pep. hmm, I have no minutes to link to yet.
  80. pep. I guess I'll just state that
  81. jonas’ pep., you can link to the logs of this room
  82. Kev Linking to minutes is a very recent thing and is just a nicety, I think. There's nothing requiring it.
  83. pep. Kev, sure
  84. Kev (Assuming you mean referencing when it was approved by Council)
  85. pep. yes
  86. Kev I mean, I think it's a /good/ nicety, but if it's proving an issue here...
  87. pep. Just makes it easier to check back what happened when/why
  88. Kev Yes, I think it's a good thing.