XMPP Council - 2018-07-11

  1. Ge0rG

    My calendar reminded me.

  2. Kev

    Well done Ge0rG's calendar.

  3. SamWhited

    I appear to actually be in the room this week

  4. Dave

    Even I'm here.

  5. jonasw

    I’m, too!

  6. Ge0rG

    !ping SamWhited

  7. SamWhited

    oh wow, I sent that and there was a *lot* of lag, briefly thought it wasn't working after all.

  8. Ge0rG

    I'll have to translocate starting in 20mins, but maybe my crappy mobile client app will suffice for after that.

  9. jonasw

    !summon Dave

  10. jonasw

    !summon daniel

  11. daniel


  12. Ge0rG

    council@muc.xmpp.org/SamWhited responded to ping after 0.6988s

  13. daniel

    My lag is fine

  14. jonasw

    "I’m not 15 minutes late, my lag is just high"

  15. SamWhited

    Ge0rG: second message was fine, so no idea what that was about

  16. SamWhited

    and that one

  17. jonasw

    s2s establishment probably?

  18. Ge0rG

    Are we part of the establishment?

  19. jonasw

    ... didn’t check the clock and was wondering why everyone is here but not talking

  20. jonasw

    and was about to check whether *my* link to this muc was broken

  21. Ge0rG

    Somebody should write a self-ping XEP.

  22. Ge0rG

    Oh, wait. That's on my TODO already.

  23. Dave

    16:00, golly.

  24. Ge0rG

    Dave: you were 9 seconds too early.

  25. Dave


  26. Dave

    1) Role Call

  27. Kev


  28. Dave

    Kev, Diolch.

  29. SamWhited


  30. Ge0rG

  31. daniel


  32. Dave


  33. Dave

    2) Agenda Fiddling

  34. Ge0rG

    Whoops, there is an agenda today. I totally missed that.

  35. Dave

    Any suggestions? Otherwise I'll go along with what Tedd Sterr has provided, since it seems OK.

  36. Kev

    No bashing here.

  37. SamWhited


  38. Dave

    3) PR #664 - XEP-0045: Add implementation note about {jabber:x:conference}x payload - https://github.com/xsf/xeps/pull/664

  39. Kev

    Other than the typo, I don't think this is harmful (but do agree it should have gone to Council vote).

  40. Kev

    +1 sans typo

  41. Ge0rG

    There is a typo in that patch. "there still exist*s* server implementations"

  42. Ge0rG

    +1 sans typo from me as well

  43. daniel


  44. SamWhited


  45. Dave


  46. Dave

    4) PR #672 - XEP-0059: Add 'exact(-index)' attribute to RSM's <count/> and <first/> - https://github.com/xsf/xeps/pull/672

  47. Kev

    I've missed the context on this - anyone got the subject line from standards@ to look at?

  48. Kev

    I'm -1 regardless, but I'd like to see the discussion that prompted it.

  49. jonasw

    I think the discussion was in xsf@

  50. Dave

    I think I have to be on-list for this, I've not seen the discussion and it seems non-trivial.

  51. Kev

    I think the presence of an optional attribute that has no default in case it's missing is enough for me to -1 it in current form, regardless of intent.

  52. Ge0rG

    I think it's overdoing. Add complexity for a very specific corner-case. Not that I'm not guilty of that myself.

  53. jonasw

    Kev, huh, why?

  54. SamWhited

    I'm on list as well, but am leaning towards -1. I need to reread 0059 again first though.

  55. Dave

    Kev, Hmmm. Surely the absence means unspecified, as is the case now?

  56. jonasw

    absence signals "server doesn’t know, doesn’t want to, or does not support this"

  57. jonasw

    I don’t see anything wrong with that conceptually

  58. Kev

    It is currently not unspecified, it's currently specified that it may be inexact, and therefore anyone receiving it has to treat it as inexact.

  59. Kev

    i.e. the current is default exact=false.

  60. Ge0rG

    the current default is exact=maybe.

  61. Dave

    Kev, Ah... Interesting. I see your logic there.

  62. Dave

    daniel, Anything to say/vote before we move on?

  63. Kev

    Regardless, adding a SHOULD for new protocol to a Draft XEP seems like it needs to be done carefully.

  64. daniel

    I don't really have an opinion yet

  65. daniel

    On list

  66. Ge0rG

    on list from me as well

  67. Dave

    5) Stagnant Votes

  68. flow

    I'd like to note that the commit message tries to provide a motivation

  69. Kev

    Am I the only one who thinks that thanking yourself in your own patch is terribly bad form too?

  70. Ge0rG

    flow: "may use an optimized algorithm" is a rather weak motivation.

  71. Dave

    I think at least a few of my votes have expired due to my absence, and I've no idea what else might be outstanding.

  72. Kev

    I still owe a vote on HTTP Upload, which may have expired, but I think there's unaddressed feedback on list that I'd like to see discussed before it advances.

  73. Dave

    I'll commit to updating the Spreadsheet Of Doom over the next couple of days.

  74. Ge0rG

    Kev: yes it is, but we don't have a better way to add contributors to an XEP, or do we?

  75. Kev

    I see comments from Goffi without a response, at least.

  76. Kev

    Ge0rG: I would expect the author or Editor to add a thanks in that case.

  77. Dave

    6) AOB

  78. Ge0rG

    Kev: I haven't seen that happen in practice, yet.

  79. daniel

    > Am I the only one who thinks that thanking yourself in your own patch is terribly bad form too? Yes. But I get where this is coming from and we don't have a good alternative for being listed as a conttubor

  80. Kev

    I have NAOB.

  81. SamWhited

    git blame will list you as a contributor if it's terribly important to you

  82. Ge0rG

    Maybe we need to add it to the XEP Editor README

  83. Ge0rG begins translocation now.

  84. Dave

    So apologies for my extended absence - I've had a collision of things (including a new treasurer appeared and then vanishing on me across an accounts deadline for a charity I help with).

  85. Kev

    We coped, mostly.

  86. Dave

    On the plus side, I taught myself double-entry ledger book-keeping, which is something.

  87. Dave

    But in any case, I'll commit to being more around as from now.

  88. Ge0rG

    That's a bold commitment

  89. Dave

    7) Next Meeting

  90. Dave

    Normal time next week?

  91. Kev


  92. daniel


  93. SamWhited


  94. Ge0rG

    Should be fine

  95. Dave

    I'll actually be on a train, but it should be OK.

  96. Dave

    8) Ite, Meeting Est.

  97. Dave

    Thank all.

  98. Kev

    Thanks all.

  99. Dave

    Thanks all.

  100. flow

    Ge0rG, would it help if I'd elaborate the algorithm for the exact=true case?

  101. Ge0rG

    flow: it sounds like you should do that, on standards@

  102. flow

    I dunno, appears the thing already got -1'ed

  103. Dave

    flow, It'd be more useful if there were some concrete cases where exactitude was essential.

  104. jonasw

    flow, modify the PR, re-submit to council, new vote

  105. Dave

    flow, Well. -1 means "do not advance", and not "never advance".

  106. Ge0rG

    flow: it seems nobody in the council quite grasped why the extension is needed.

  107. Ge0rG

    So providing a deeper motivation on the list will probably increase your chances, or at least shift the feedback from "lack of understanding" to practical / formal issues