XMPP Council - 2011-07-06


  1. stpeter

    hmm, I need to push out revised versions of http://datatracker.ietf.org/doc/draft-blanchet-precis-framework/ and https://datatracker.ietf.org/doc/draft-saintandre-xmpp-6122bis/ before the document deadline next Monday....

  2. Kev

    And ding, 4pm.

  3. Kev

    Are we sitting comfortably? Then let's begin.

  4. Kev

    stpeter: That sounds fun.

  5. stpeter

    yes, fun indeed

  6. Kev

    1) Roll Call

  7. Kev

    I'm here.

  8. Fritzy

    here

  9. linuxwolf

    presente

  10. MattJ

    Here

  11. linuxwolf

    omfg…we actually have a Fritzy! (-:

  12. Kev

    Huzzah.

  13. Kev

    2) Agenda bashing.

  14. stpeter laughs

  15. Kev

    I've noted adding Compliance.

  16. Fritzy

    none

  17. linuxwolf

    AOB, mabye

  18. linuxwolf

    maybe even

  19. Kev

    Ok.

  20. Kev

    3) Accept 1.1rc2 of XEP-0143 ("Guidelines for Authors of XMPP Extension Protocols"). http://xmpp.org/extensions/tmp/xep-0143-1.1.html http://xmpp.org/extensions/diff/api/xep/0143/diff/1.0/vs/1.1rc2

  21. MattJ

    This has been nagging at me for a while

  22. MattJ

    Why do we have agenda bashing /and/ AOB? :)

  23. Kev

    MattJ: I have no idea, and often wondered that.

  24. Fritzy

    that sounds like a topic for AOB

  25. Fritzy

    ;)

  26. MattJ

    Kev, you have the power!

  27. stpeter

    agenda bashing could include removing items, I'd think

  28. linuxwolf

    that's what I was about to say, @Fritzy (-:

  29. Kev

    But I treot Agenda Bashing as Things Wot Require Votes, and AOB as discussion points.

  30. Kev

    In any case...

  31. Kev

    3) Accept 1.1rc2 of XEP-0143 ("Guidelines for Authors of XMPP Extension Protocols"). http://xmpp.org/extensions/tmp/xep-0143-1.1.html http://xmpp.org/extensions/diff/api/xep/0143/diff/1.0/vs/1.1rc2

  32. MattJ

    Fair enough

  33. Kev

    I'm +1.

  34. MattJ

    Me too

  35. MattJ

    I haven't read it in detail so maybe missed anything editorial

  36. Fritzy

    +1

  37. linuxwolf

    I'll vote on list

  38. MattJ

    But I like this XEP and these changes

  39. Kev

    I wonder if it's sensible to reference something else for the instructions on how to submit a patch, just so Peter doesn't require Council approval if he changes his favourite Git workflow, but I don't mind.

  40. Fritzy

    ah, that's probably a good idea for a future revision. ;)

  41. linuxwolf

    /nod

  42. stpeter

    probably not a bad idea for the Council to be aware of how things are done

  43. Kev

    Maybe it's sensible to require approval so Peter can't require authors to jump through hoops :)

  44. Fritzy

    Or "future evil editor"

  45. ralphm

    hello

  46. Kev

    4) Reverting the compliance suites.

  47. Fritzy

    howdy

  48. ralphm

    +1 on #3

  49. Fritzy

    what does that mean exactly (#4)

  50. Kev

    Are we agreed that Peter reverting the compliance suite 6120/3920 references was the right thing?

  51. Kev

    Fritzy: Was typing.

  52. MattJ

    I'm agreed

  53. Kev

    I think we didn't intend the compliance suites to be updated in the first place when we issued the blanket "please update everything".

  54. ralphm

    the reverting is good

  55. linuxwolf

    /agreed

  56. Kev

    Good.

  57. Fritzy

    ok

  58. Kev

    5) Compliance 2012.

  59. Kev

    Do we want compliance suites this year?

  60. MattJ

    +1, IMHO

  61. MattJ

    I've always been a fan of the compliance XEPs, even though not as much has been made of them that could have been

  62. MattJ

    I think they're worth the small amount of effort

  63. linuxwolf

    +1 also

  64. linuxwolf

    they help authors determine what's in, and what they can cut corners on

  65. Kev

    I guess the logical follow-up question is what goes in them :)

  66. linuxwolf

    well, we could use the previous versions as a starting point (-:

  67. Fritzy

    sounds logical

  68. Kev

    I think we skipped 2011, making http://xmpp.org/extensions/xep-0270.html the most recent.

  69. linuxwolf

    then s/392[01]/612\1/g (-:

  70. stpeter

    yes we skipped 2011

  71. linuxwolf

    I don't think we need a new suite every year…but it's worth it now with the new XMPP specs

  72. Kev

    I'd like to strike -16 off the list, and replace it with 191.

  73. Kev

    I don't like -16.

  74. Fritzy

    :)

  75. stpeter

    yeah I don't either

  76. Kev

    Well, 'replace'. 191 is already there.

  77. Kev

    Otherwise, that looks like a fairly sensible base.

  78. Kev

    I'm not sure what else we'd particularly need on there.

  79. linuxwolf

    I'd like to add −201

  80. Fritzy

    should someone copy it up and put it in inbox for next meeting?

  81. linuxwolf

    maybe −296 if I can get it updated (-:

  82. linuxwolf

    Fritzy: +1

  83. linuxwolf

    and thanks for volunteering? (-:

  84. stpeter

    heh

  85. Kev

    I'm not entirely convinced about 201.

  86. linuxwolf

    I am

  87. Kev

    296 seems much more valuable.

  88. linuxwolf

    I have a couple of nits to clean up in 296

  89. linuxwolf

    but I can also see about starting on this compliance 2012

  90. Kev

    Shall we take it to list, then, and you can justify including 201 there? :)

  91. linuxwolf

    (-:

  92. linuxwolf

    it's not a hill for me to die on

  93. MattJ

    I'd be unsure of very recent XEPs in compliance suites

  94. Kev

    MattJ: Yes, me too, except that 296 is documenting best practice.

  95. linuxwolf

    exactly

  96. stpeter types 'cp xep-0270.xml inbox/compliance2012.xml

  97. linuxwolf

    it's something a lot of clients are already doing

  98. linuxwolf

    well, the "good" clients (-:

  99. linuxwolf

    stpeter: hehe

  100. ralphm

    :-D

  101. Kev

    Although maybe referencing experimental XEPs in a compliance suite isn't smart.

  102. Kev

    I wonder if any of the others are.

  103. ralphm

    I fully agree there

  104. linuxwolf

    ok, so then I'll propose 296 move forward? (-:

  105. ralphm

    so I suppose stuff needs to happen before 2012

  106. Fritzy

    haha

  107. Kev

    Right.

  108. linuxwolf

    ralphm: we can start on it, but yes

  109. Kev

    So rough idea for the moment is to make compliance 2012 = 2010 + 6120 -16, and to consider threads and locking on-list?

  110. MattJ

    +1

  111. linuxwolf

    sure

  112. Kev

    Ok.

  113. Kev

    6) Date of next meeting.

  114. Kev

    SBTSBC?

  115. MattJ

    +1

  116. linuxwolf

    +1

  117. Fritzy

    +1

  118. MattJ

    whether I can make it I don't know yet, I won't know until next week

  119. MattJ

    I'll try to send apologies in advance if I can't

  120. Kev

    Ta.

  121. Kev

    7) Any other agenda bashing?

  122. Fritzy

    uh, AOB vs. Agenda Bashing?

  123. Fritzy

    ;)

  124. linuxwolf

    1) a nit in 0297, the namespace is "urn:xmpp:forward:tmp", but it should be "urn:xmpp:forward:0", yes?

  125. linuxwolf

    2) did anyone ever follow up on the xep-0220 discussion?

  126. stpeter

    I did not follow up on dialback

  127. stpeter

    that was my action item

  128. Kev

    linuxwolf: It should be, really, yes, now it's accepted.

  129. MattJ

    +1

  130. MattJ

    to #1

  131. MattJ

    and to following up on 220 as well

  132. linuxwolf

    Kev: I'm starting on an update to carbons, including msg-fwd, and found that little nit (-:

  133. Kev

    Wonderful, thanks.

  134. Kev

    I'll poke the authors.

  135. linuxwolf

    (-:

  136. stpeter

    I'll send the 220 message now before I do a deep dive on i18n madness

  137. linuxwolf

    I can provide you a patch (-:

  138. Kev

    I wouldn't bother, unless you've already done it :)

  139. linuxwolf

    I think I have…in one of my clones (-:

  140. Kev

    I suspect it'd take as long to apply the patch as to write it.

  141. linuxwolf

    Kev: yeah, pretty much

  142. Kev

    Aaaaanything else?

  143. ralphm

    nope

  144. linuxwolf

    nay from me

  145. Fritzy

    nodda

  146. Kev

    I'll try to remember to not include agenda bashing next time, and we can bash on-list, or AOB in the meeting.

  147. Kev

    Right, if we're all done...

  148. Kev

    Thanks all.

  149. Kev gangs the bavel.

  150. stpeter scrolls up to see if needs to do anything with 143 yet

  151. stpeter

    ah no, lw to vote on list

  152. linuxwolf

    stpeter: I didn't read the changes yet, sorry!

  153. stpeter

    no worries

  154. linuxwolf likes to read first, vote second (-:

  155. stpeter

    details, details

  156. linuxwolf

    ok, off to prep for my next meeting...adios

  157. Kev

    Enjoy.

  158. stpeter

    enjoy!

  159. linuxwolf

    today's light…only 3 (-:

  160. stpeter

    heh

  161. stpeter

    ok I looked at the XEP-0220 issues

  162. stpeter

    at least briefly

  163. stpeter

    it is very frustrating

  164. stpeter

    and I have some IETF deadlines so I might need to delay real work on this until Tuesday

  165. Kev

    I'm sure it'll wait.

  166. stpeter

    I am about ready to suggest that Philipp and I need to work on separate specifications of the protocol, and the Council can decide which one it wants to advance -- until then, RFC 3920 will remain the canonical documentation

  167. MattJ

    That would be sad, but if it needs to happen to further the specs, so be it

  168. stpeter

    not sure yet -- I'll try to reach some consensus on the list

  169. stpeter sends a conciliatory note

  170. MattJ

    stpeter, you're a trouble-maker ;)

  171. linuxwolf

    /-:

  172. stpeter

    sorry, I got annoyed

  173. stpeter

    there's no reason to be so snarky

  174. stpeter

    we're all trying to work toegher on this stuff

  175. stpeter

    together, even

  176. MattJ

    +1, your last email is fine by me

  177. linuxwolf

    I think I would have been ruder, myself (-:

  178. stpeter

    and http://about.psyc.eu/Jabber still contains numerous errors, but I don't publicly question their motives

  179. MattJ

    Don't remind me that page exists

  180. MattJ

    It's better than it used to be, at least

  181. MattJ

    Mainly since it no longer has the out-of-context quote of me

  182. stpeter

    ok, enough dialback for today, now I need to crank out a bunch of internationalization work and put together some slides for a presentation about XMPP on Friday before some "smart grid" group

  183. MattJ

    What's the not-so-smart grid?

  184. stpeter

    the dumb grid

  185. stpeter

    how electricity gets to your house :)

  186. stpeter

    people are making it smarter using demand-response technologies and such

  187. MattJ

    Evidently

  188. stpeter

    in fact they're already using XMPP (some of them, anyway)

  189. stpeter

    "price went up, you might want to turn off the clothes dryer" and such

  190. stpeter

    but the folks using XMPP are doing commercial and industrial applications mostly

  191. Kev

    They should purchase Swiften licenses to use as their libraries...

  192. stpeter

    Kev: good idea, I'll let them know ;-)

  193. stpeter

    also some embedded stuff -- actual XMPP-enabled washers and dryers and such

  194. Kev

    They should...

  195. stpeter

    it's a bit crazy ;-)

  196. stpeter

    the sensors stuff is semi-related -- I never saw further replies to those threads, though...

  197. stpeter

    anyway, bbiab

  198. MattJ

    :)

  199. MattJ

    brb, need to relocate to a printer

  200. linuxwolf

    I think it's time for lunch…bbl

  201. stpeter

    lunch is a good idea