XMPP Council - 2011-02-16


  1. stpeter

    greetings

  2. Kev

    Hey.

  3. stpeter

    how goes it?

  4. stpeter looks around for Council members to poke

  5. stpeter

    Matthew's <status/> says "Walking" :)

  6. Kev

    Busy.

  7. David Banes

    Hi, are these sessions open for 'listen only'?

  8. stpeter

    sure!

  9. Kev

    David Banes: Yes.

  10. David Banes

    OK, I'll listen while having my afternoon tea

  11. Kev

    Tobias: Where's the difftool? I've forgotten

  12. stpeter

    David Banes: you can even say things -- but only Council members have a vote

  13. David Banes

    OK, thnx .

  14. waqas

    Does someone have a link to the agenda?

  15. waqas

    stpeter: Aside: Is the .im registrar in this list at all? http://www.pir.org/get/registrars?order=field_dnssec_value&sort=desc

  16. stpeter

    waqas: we just post it (and discuss topics) on the council@xmpp.org list, anyone can subscribe

  17. ralphm waves

  18. stpeter

    waqas: good point, I'll ask them about DNSSEC support

  19. stpeter

    so have we all recovered from the Summit? :)

  20. remko

    or from not being at the summit

  21. stpeter

    heh

  22. Kev

    I suspect I'll never recover from that.

  23. remko

    Kev: you missed some good pizza and steak ;-)

  24. Kev

    Not helping.

  25. linuxwolf

    and ribs

  26. stpeter

    was the pizza any good?

  27. Kev

    Right, meeting time.

  28. Kev

    1) Roll call.

  29. linuxwolf

    I think I'm here

  30. Kev

    I see a Kevin, one MattM and a Ralph. I don't see a MattJ or a Fritzy.

  31. Kev

    2) Agenda bashing.

  32. Kev

    No? Good.

  33. Kev

    3) http://xmpp.org/extensions/inbox/vcard4.html Accept as a XEP?

  34. linuxwolf

    +1 (-:

  35. ralphm

    +1

  36. ralphm

    I have severe lag

  37. Kev

    There are little inconsistencies here, like saying to dump the <vcards/> wrapper, but then having examples that include it, but I'm happy to publish.

  38. ralphm

    on 2), there were some suggestions. Not sure what to do

  39. stpeter

    Kev: yeah I tried to clean it up while in Brussels but didn't quite finish, I think

  40. linuxwolf

    I'll work with the author or the editor on that

  41. Kev

    ralphm: You mean you have agenda bashing?

  42. ralphm

    Kev: well you said you were adding stuff to the agenda, but I didn't see an updated one.

  43. Kev

    ralphm: I thought it was a given that once I'd said 'these are on the agenda' that I didn't need to send out an updated one.

  44. Kev

    4) http://xmpp.org/extensions/tmp/xep-0198-1.2.html Accept new version?

  45. Kev

    I confess to not having read the diff yet, I need to find where the difftool is and check them. I'll vote on list.

  46. stpeter

    unfortunately it seems that the diff tool is not working

  47. Kev

    Ah, lovely.

  48. Kev

    Ok, so I need to poke iteam about that, then.

  49. Kev

    Either Ralph or Matt want to vote on 198-1.2?

  50. stpeter

    at least it's no longer working for me

  51. linuxwolf

    I need to read the new one again

  52. ralphm

    not yet

  53. Kev

    Ok - you have a fortnight :)

  54. stpeter

    dwd: could you review 198 as well?

  55. Kev

    5) Soon-to-expire XEPs: > http://xmpp.org/extensions/xep-0215.html > http://xmpp.org/extensions/xep-0275.html > http://xmpp.org/extensions/xep-0276.html > http://xmpp.org/extensions/xep-0277.html

  56. stpeter

    dwd: I want to make sure I incorporated everything from your patch

  57. dwd

    I can, but as Kev might tell you, I'm a shade overworked...

  58. stpeter

    dwd: um yeah, I understand

  59. Kev

    Not that there's anything for Council to do about these, unless someone fancies updating them.

  60. stpeter

    I poked the Jingle list and several Collabora contributors about 276

  61. stpeter

    the others could always be resurrected in the future if desired

  62. stpeter

    I just wanted to keep the Council in the loop

  63. Kev

    It only takes an update :)

  64. stpeter

    yep

  65. Kev

    6) Date of next meeting.

  66. stpeter

    waqas: http://mail.jabber.org/mailman/listinfo/council

  67. dwd

    I may choose to resurrect 277 at some stage, but not right now.

  68. Kev

    Next Wednesday, same Bat-time, same Bat-channel?

  69. ralphm

    xep-0277 needs some use cases

  70. stpeter

    dwd: yes I think it's a bit early for the microblogging stuff, and others are more interested in it than I am, it seems

  71. dwd

    ralphm, The big problem is that there are two quite distinct models, and we need to pick one.

  72. stpeter nods to ralphm

  73. ralphm

    also, I am more interested in a slightly broader scope

  74. ralphm

    (than pure microblogging)

  75. stpeter

    Kev: works for me

  76. dwd

    ralphm, macroblogging?

  77. ralphm

    dwd: well, we shove around quite some atom ovre xmpp

  78. David Banes

    fyi - there was a general feeling at SeaBeyond that xep-0277 wasn't a lot of use in it's current form .. just 'sayin

  79. dwd

    ralphm, Like microblogging, except there's a minimum number of characters.

  80. ralphm

    for federation purposes

  81. ralphm

    including activity streams

  82. stpeter adds next week's Council meeting to the calendar

  83. Kev

    Thanks.

  84. Kev

    7) AOB

  85. stpeter

    David Banes: yes that seems to be the general feeling all around

  86. Kev

    Oh, right.

  87. Kev

    GSoC.

  88. stpeter

    ah yes

  89. stpeter

    already? ;-)

  90. Kev

    I'm assuming we're applying again.

  91. Kev

    I saw bear announce that he was going to be admin this year, so I guess Board have discussed this, but I didn't notice the minutes :)

  92. ralphm

    David Banes: I didn't get into good talks with the other people around at FOSDEM to talk much about this, unfortunately

  93. Kev

    In any case, I'd like to check that we don't have another FOSDEM falling-through-the-cracks.

  94. stpeter

    yeah

  95. stpeter

    we also need to think about a North American summit

  96. Kev

    We should think about sorting out proposals etc. in advance of orgs applying, ideally.

  97. stpeter

    (if desired)

  98. stpeter

    Kev: yes

  99. Kev

    Swift is probably in a state to put a couple of proposals up this year. Albeit we'd be terribly elitist about what we wanted in a student :)

  100. Kev

    Simon's spoken to me about wanting to do BuddyCloud proposals under the XSF umbrella.

  101. ralphm

    Kev: how is that bad?

  102. ralphm

    Oh nice

  103. linuxwolf doesn't seem the inherent problem with elitism

  104. Kev

    So I think what we need is for Board to make a decision about who's responsible for this (and maybe it's already done so and I missed the minutes) so I can start beating them over the head to make sure they do everything.

  105. Kev

    I note that I'm idling in the gsoc channel already.

  106. Kev

    When's the next Board meeting anyhow? I couldn't find it in the calendar when I looked yesterday.

  107. stpeter

    Kev: I haven't seen a Board decision about this, and will poke their list about having a meeting next week

  108. Kev

    I think we suffered last year from not being organised enough in advance, so I'd like us to do better this year.

  109. Kev

    And ideally I'd like someone else to be doing it :D

  110. stpeter

    :)

  111. Kev

    (Although I'm happy to be admin again, like last year)

  112. stpeter

    Board list poked

  113. Kev

    Ta.

  114. Kev

    Is the Board list public-membership these days?

  115. stpeter

    Kev: no, but the meetings are held in the open xsf@muc.xmpp.org room

  116. Kev

    Well, this isn't really Council-relevant now.

  117. Kev

    Any other AOB?

  118. Kev

    stpeter: Right, it's just hard to know when the meetings are without listening to the list :)

  119. stpeter

    oh

  120. stpeter

    Kev: right, the calendar should be updated

  121. stpeter

    I have AOB

  122. Kev

    Shoot.

  123. stpeter

    file transfer

  124. stpeter

    there's a whole raft of specs

  125. stpeter

    I think 47 is ready to go

  126. stpeter

    I think we'll want to work on these somewhat sequentially

  127. stpeter

    after 47 I think we could do Jingle IBB = XEP-0261

  128. stpeter

    so I will continue to poke various lists and people about that

  129. stpeter

    perhaps 47 can be on the agenda for next week's Council meeting

  130. Kev

    Ok.

  131. stpeter

    in parallel, I will start a thread about 65 (one major open issue)

  132. stpeter

    and update 234

  133. stpeter

    (to reflect Brussels discussions)

  134. Kev

    By 'on the agenda', you mean there's a new version to vote on, or you'd like to LC it?

  135. stpeter

    new version

  136. Kev

    Ok.

  137. Kev

    It's not an LC when it's already Draft anyway, is it? :)

  138. stpeter

    1.3rc2 for 47

  139. Kev

    But anyway, details.

  140. Kev

    Ok.

  141. stpeter

    right

  142. stpeter

    http://xmpp.org/extensions/tmp/xep-0047-1.3.html

  143. Kev

    Will do. Anything else?

  144. stpeter

    no, that's it from me

  145. linuxwolf

    not this week (-:

  146. Kev

    Excellent.

  147. linuxwolf

    oh, Kev: check your emails, pls (-:

  148. remko

    stpeter: It wasn't authentic pizza or anything, but i'm extremely easy on pizza.

  149. Kev

    I'll sort out minutes when I have some spare cycles. Around 2015

  150. Kev

    linuxwolf: Oh, I've probably missed whatever it is then.

  151. Kev

    linuxwolf: Could you repoke it please?

  152. linuxwolf

    Kev: I can resend…about multi-resource

  153. stpeter is shooting to get below Inbox 7000 today

  154. remko

    linuxwolf:"Prework on multi-resource"?

  155. linuxwolf

    sì

  156. Kev

    Ok, I'll dig that out. It's not in the first page of my inbox so there's no hope of me finding it naturally.

  157. linuxwolf

    (oh noes, evil composed character!)

  158. Kev

    In any case, I think Council's done.

  159. linuxwolf

    /nod

  160. Kev

    Thanks all.

  161. Kev bangs the gavel.

  162. stpeter

    heh

  163. linuxwolf

    adios

  164. stpeter

    I've been thinking more about i18n, too -- need to get working on updated specs

  165. ralphm

    stpeter: I found the sessions on i18n pretty good, but am unsure how "we" should proceed

  166. ralphm

    sure the precis wg is a collection of people

  167. ralphm

    but some hints for contributing meaningfully would be useful

  168. Tobias

    Kev: thanks for the reminder..i'll try to bring in back this evening :)

  169. Kev

    Tobias: Fab, thanks.

  170. ralphm

    I'm not sure how many people had any idea of what to do

  171. stpeter

    ralphm: I'll be providing some guidance about direction soon

  172. stpeter

    ralphm: or at least some further thoughts

  173. Kev

    For reference, I've just seen https://docs.google.com/document/d/1YpQjl8pDTztxlk1eRDgheHq-17vMEcNt3qUCypioW_g/edit?hl=en&pli=1# announced in the gsoc channel.

  174. ralphm

    stpeter: awesome

  175. stpeter

    oh and the .im folks tell me that DNSSEC is on their roadmap, but no specific date yet

  176. waqas

    Ah, thanks

  177. bear

    kev - I didn't announce that I had decided, I said that if the board agreed to do GSoC I could be the org admin

  178. Kev

    bear: Ok, I misread. I was sure I saw "I'm the GSoC admin".

  179. bear

    maybe that was my "trying to be cute and funny" english #fail

  180. ralphm

    why oh why multiple disco identities for i18n

  181. ralphm

    *snif*

  182. stpeter

    ?

  183. ralphm

    well, if you want to provide translated disco identity names, you need to include a seperate element with a xml:lang

  184. ralphm

    wokkel didn't take that into account

  185. ralphm

    I'd design the protocol differently today

  186. ralphm

    like text element(s) separate from all identities

  187. ralphm

    oh well