XMPP Council - 2013-01-02

  1. Tobias has left

  2. Tobias has left

  3. Tobias has left

  4. Tobias has left

  5. Zash has joined

  6. Zash has left

  7. Zash has joined

  8. m&m has joined

  9. Neustradamus has left

  10. Neustradamus has joined

  11. ogashiwa has joined

  12. ogashiwa has left

  13. ralphm has joined

  14. ogashiwa has joined

  15. ralphm waves

  16. Kev

    Hi Ralph.

  17. MattJ has joined

  18. Tobias


  19. Kev

    m&m: You here?

  20. Kev

    It is time.

  21. m&m

    I am now

  22. MattJ


  23. Kev

    Good afternoon ladies and gentlemen, and welcome to this year's first installment of ... The EX EM PEE PEE Council.

  24. Kev

    1) Roll call.

  25. Kev

    I'm here.

  26. m&m


  27. Tobias


  28. Kev

    ralphm: Still here?

  29. ralphm


  30. Kev


  31. Kev

    2) http://xmpp.org/extensions/inbox/mep.html Accept as XEP?

  32. Kanchil

    Kev: http://xmpp.org/extensions/inbox/mep.html: XEP-XXXX: MUC Eventing Protocol

  33. MattJ has left

  34. m&m

    no objections

  35. ralphm


  36. MattJ has joined

  37. Kev

    I had a couple of niggles with this, but nothing blocking.

  38. MattJ


  39. Kev

    (Niggles like the Note: box being wrong, and a typo of MEP becoming NEP)

  40. ralphm

    Kev: sure thing

  41. Tobias


  42. MattJ

    Sorry, I have a bad connection atm, may pop in and out

  43. MattJ

    Kev, oh good, just editorial?

  44. MattJ

    Of the various approaches to MEP that we've ever had, this has always been my favourite

  45. Kev

    I think so, although I'm shattered today so maybe I've just forgotten.

  46. Kev

    It's the only approach that can fundamentally work, I think - although there are lots of things that need to be cleared up.

  47. Kev

    When room history is limited to stuff a day old, MEP should be limited as well, it interacts with Fast Reconnect, etc.

  48. ralphm

    I still have to read it in detail, and a great thing to discuss in a few weeks

  49. Kev

    And when you publish to your PEP node, that should be autopushed to your MEP nodes, presumably.

  50. stpeter has joined

  51. stpeter

    happy new year

  52. Kev

    But yes, clearing this stuff up in Brussels would be a good use of time there.

  53. Kev

    Hi Peter, HNY.

  54. waqas has joined

  55. Kev

    3) http://xmpp.org/extensions/inbox/hats.html Accept as Experimental?

  56. Kanchil

    Kev: http://xmpp.org/extensions/inbox/hats.html: XEP-xxxx: Hats

  57. ralphm


  58. ralphm

    good to see this in writing now

  59. m&m

    also no objections

  60. Kev

    I don't have any fundamental objections to this, although I think that (3) is probably the wrong choice for the format.

  61. MattJ

    +1 to hats

  62. Kev

    I'm glad it doesn't cover some of the madnessess that I've heard discussed for hats over the years.

  63. stpeter

    ralphm: it took only 2 or 3 years, I think

  64. m&m


  65. Kev

    3, I think.

  66. ralphm

    I had been thinking of a wrapper around the custom element, but I still have to think that over

  67. stpeter

    ralphm: yeah, I need to give it some more thought too

  68. Kev

    I think you have to assume that clients aren't going to understand the hats themselves in most circumstances.

  69. Tobias

    the example form maps a hat to nicknames? shouldn't it map hats to real jids?

  70. ralphm

    Kev, right

  71. Kev

    Tobias: A reasonable question.

  72. stpeter

    Tobias: quite possibly

  73. Tobias

    stpeter, when removing a had, you at least remove by jid in your example

  74. Kev

    Tobias: Is that blocking?

  75. waqas

    I had a whole bunch of minor questions and issues, but those can go on the ML after these get published :)

  76. ralphm

    Another fine topic for discussion in Brussels

  77. waqas

    (I was attempting to implement both the specs)

  78. Tobias

    Kev, nope..could be fixed during experimental imo

  79. Tobias

    waqas, in which client? ;)

  80. waqas

    Tobias: Servers have to do everything first

  81. ralphm

    For hats I expect many application-specific hats, that generic clients won't do much with, except maybe show their name.

  82. Tobias

    waqas, mimimimi.....

  83. stpeter

    waqas: I'm not surprised -- I wrote the hats spec in a hurry and haven't touched it in several weeks

  84. ralphm

    Like for games

  85. Kev

    OK, so that's everyone happy with this, I think.

  86. Tobias

    could be combined with bits of binary to add small icons for hats, etc.

  87. Kev

    Tobias: No, I think that's MEP :)

  88. Kev


  89. Kev

    4) Date of next meeting.

  90. Kev

    Next Wed, usual time?

  91. Tobias


  92. MattJ


  93. ralphm


  94. Kev


  95. m&m

    double-you eff em

  96. Kev

    5) Any other business?

  97. waqas

    m&m: That could be interpreted incorrectly..

  98. m&m

    none from me

  99. stpeter updates the calendar

  100. Kev

    stpeter: Thanks.

  101. stpeter wanders off for tea, brb

  102. Kev

    OK, with no other business I guess we're done.

  103. m&m

    same here

  104. Kev

    Thanks all.

  105. m&m

    tea, that is

  106. Kev bangs the gavel.

  107. ralphm


  108. ogashiwa has left

  109. MattJ

    Oh, note... stpeter wrote in the call for talks that council would select from submissions

  110. MattJ

    I haven't personally had time to review them yet, shall we aim to do that next week?

  111. ralphm


  112. Kev

    I'm completely not on top of FOSDEM stuff.

  113. Kev

    I'm happy to review stuff (although don't recall seeing enough submissions for stuff to not fit anyway), but I'd greatly appreciate if someone could tell me what to review :)

  114. ralphm

    I think with the start of the new year we should give this new attention

  115. ralphm

    I believe the submission deadline for the FOSDEM flyer is nearing

  116. ralphm looks that up

  117. ralphm

    oh we set a deadline of 31 December

  118. MattJ


  119. Kev

    Have we got enough talks to fill the time?

  120. Kev

    I'm happy enough to put a talk in if we're short and someone can think of anything interesting for me to say.

  121. Kev

    But have nothing particularly burning to say.

  122. Kev

    I'm guessing we'll start with the usual XMPP 101 with some combination of Remko/Peter/me one way or another.

  123. Tobias

    those are for FOSDEM right?

  124. Tobias

    not for summit, the talks

  125. Kev


  126. Tobias


  127. ralphm

    I count 7 proposals on the summit ml

  128. ralphm

    not sure if people have sent requests directly to peter

  129. MattJ

    How much time do we have in the devroom this year?

  130. ralphm looks

  131. ralphm


  132. ralphm

    and the hard dead-line for the submission of our schedule for the devroom is January 10

  133. MattJ

    So we have plenty of room I gather

  134. ralphm


  135. ralphm

    it is nice to not have to cram things in a schedule

  136. MattJ

    Some years we fill gaps with lightning talks, which generally get filled

  137. MattJ

    People always have something to say when given the chance :)

  138. ogashiwa has joined

  139. stpeter wanders back in after much IRL discussion

  140. Tobias has joined

  141. ogashiwa has left

  142. m&m has left

  143. ogashiwa has left

  144. ogashiwa has joined

  145. ogashiwa has left

  146. Neustradamus has left

  147. Neustradamus has joined

  148. Zash has left

  149. ogashiwa has left

  150. Zash has joined

  151. stpeter has left

  152. waqas has left

  153. MattJ has left

  154. MattJ has joined

  155. MattJ has left

  156. MattJ has joined

  157. ogashiwa has left

  158. ogashiwa has left

  159. ogashiwa has joined

  160. stpeter has joined

  161. ogashiwa has left

  162. MattJ has left

  163. Neustradamus has left

  164. Neustradamus has joined

  165. Tobias has left

  166. Tobias has left

  167. Tobias has joined

  168. ralphm has left

  169. m&m has left

  170. Zash has left

  171. stpeter has left