XMPP Council - 2010-04-12


  1. Kev has joined

  2. Tobias has left

  3. Tobias has joined

  4. Tobias has left

  5. Tobias has joined

  6. Tobias has left

  7. Tobias has joined

  8. Tobias has left

  9. Tobias has joined

  10. Fritzy has joined

  11. Fritzy

    Kev: feel like making me a moderator?

  12. Kev

    Nope.

  13. Kev

    I don't think Prosody does moderators atm.

  14. Kev

    Or, well, not admins, anyway.

  15. Tobias has left

  16. ralphm has joined

  17. ralphm

    hello fans!

  18. Kev

    Howdy.

  19. Fritzy

    ralphm: are you saying we blow?

  20. Kev

    ralphm: please sign up as a mentor for gsoc.

  21. Kev

    http://socghop.appspot.com

  22. ralphm

    Fritzy: nah ;-)

  23. ralphm

    Kev: unlikely

  24. Kev

    It's your Council-ly duty to vote on the apps :p

  25. ralphm

    Kev: do I need to be a mentor for that?

  26. ralphm

    i.e. I sign up but not actually be a mentor?

  27. Kev

    You need to have the mentor flag set in the application.

  28. Kev

    You don't have to mentor a project

  29. ralphm

    right

  30. MattJ has joined

  31. Kev

    Blimey, everyone who's coming is here before 7.

  32. Kev

    Best leave it a minute for spectators to turn up, anyway

  33. Kev

    And we're there, let's start.

  34. Kev

    1) Roll call.

  35. Kev

    Kev, Nathan, Matt, Ralph here.

  36. ralphm

    woot

  37. Kev

    Remko sends apologies, as does Peter.

  38. MattJ

    (/me saves a comment about thinking Prosody doesn't do MUC admins for later :) )

  39. Kev

    2) Agenda bashing?

  40. Kev

    I have some, but I guess I can manage that myself.

  41. Fritzy

    not this time

  42. Kev

    3) XEP-0060 : Publish-Subscribe Accept version 1.13? http://xmpp.org/extensions/tmp/xep-0060-1.13.html Diff: http://xmpp.org/extensions/diff/api/xep/0060/diff/1.12/vs/1.13rc15

  43. ralphm

    I started a complete review of the changes

  44. Fritzy

    There's at least one error in the spec. In particular publish-only should not be able to configure the node as indicated.

  45. ralphm

    I do have some comments

  46. ralphm

    publish-only sounds like an odd thing

  47. Fritzy

    do I need to vote -1 in order to get such a correction in there?

  48. Kev

    Fritzy: that would be usual.

  49. Kev

    I'm -1 because of the config bug, but only because of that, I believe.

  50. ralphm

    I didn't notice before that publisher information (section 7.1.2.3) is not in SHIM, but in an attribute

  51. Fritzy

    ralphm: I've been doing thinking about publish-only, and I do see use cases for it.

  52. MattJ

    Likewise

  53. ralphm

    Fritzy: really? If you just get another JID you /can/ subscribe?

  54. ralphm

    or would it be useful if you have a non-open node?

  55. Fritzy

    ralphm: only potentially -- depends on the auth model.

  56. MattJ

    ralphm, the latter

  57. Fritzy

    right

  58. ralphm

    ok

  59. ralphm

    I'm not against it

  60. ralphm

    just wondering

  61. Kev

    ralphm: the use case suggested (back in September last year!) when this was added was for stuff like myfacefriendsnet

  62. Kev

    Where you'll allow some service to put photos in your photo stream, but not read what else is there.

  63. ralphm

    Kev: the temporal aspect is not too important for me :-)

  64. Fritzy

    contributing to a vote/suggestion box would be another use case.

  65. Kev

    Right.

  66. Fritzy

    cool, we're all in agreement then

  67. ralphm

    ok, but then maybe it should be explained more a bit, that it's only useful with a non-open node

  68. Kev

    I admit I'm much happier with IQ gone from this.

  69. ralphm

    Kev: indeed

  70. Kev

    ralphm: it could be, but equally if you choose to use it, you probably have a use case.

  71. ralphm

    I'm a bit curious about the removal of batch options

  72. Fritzy

    -1 due to the ability for publish-only affiliations to configure the node.

  73. Kev

    The XEP doesn't *need* to tell people why they might use it ;)

  74. ralphm

    because it is unclear what happens for earlier clients

  75. Kev

    I'm +1 once the config thing is fixed (so -1 for the few hours it'll take Peter to fix that :))

  76. ralphm

    Kev: then it can be added as a security concern, for open nodes

  77. Fritzy

    ralphm: maybe that's prep work for the iq thing?

  78. Kev

    ralphm: that's fair.

  79. Kev

    ralphm / MattJ: are you voting tonight,or onlist?

  80. Fritzy

    was batch only removed to make iq delivery easier?

  81. ralphm

    Fritzy: I don't mind the removal per se, but I'm unsure what older clients would do

  82. ralphm

    they would basically fail and have no useful fallback without recoding

  83. MattJ

    Kev, I think I'm +1, but I wanted to re-read, so I'll vote on-list ASAP

  84. Kev

    OK.

  85. Kev

    ralphm: were you voting tonight or on-list?

  86. ralphm

    on-list

  87. Kev

    OK.

  88. ralphm

    I have some more comments

  89. ralphm

    here or on list?

  90. Kev

    4) XEP-0163: PEP Accept version 1.2? http://xmpp.org/extensions/tmp/xep-0163-1.2.html Diff: http://xmpp.org/extensions/diff/api/xep/0163/diff/1.1/vs/1.2rc4

  91. Fritzy

    +1

  92. MattJ

    +1 also

  93. ralphm

    I'm +1 on XEP-0163

  94. Kev

    I was +1 on this last time around, so I imagine I'm +1 now too :)

  95. Kev

    Excellent.

  96. Kev

    5) GSoC

  97. Kev

    Not much to say - all of Council are mentors now, I've asked Jack to make sure Board all sign up, and we've put a few project people through, if they have applications for those projects.

  98. Kev

    I'll be sending a mail in a little bit to ask people to start voting on the proposals. I think that's it.

  99. Kev

    6) Next meeting.

  100. Kev

    Same time next week?

  101. ralphm

    yeah

  102. Fritzy

    sure

  103. Kev

    Good enough for me.

  104. Kev

    7) AOB?

  105. ralphm

    Welcome Fritzy!

  106. Fritzy

    Thanks. :)

  107. Kev

    Ah yes, that.

  108. MattJ

    Yes, welcome :)

  109. Kev

    Thanks to Fritzy for joining the madhouse.

  110. Kev

    So, we're done then, I think.

  111. Fritzy

    I'm really excited to a part of this!

  112. Kev

    Thanks all.

  113. Fritzy

    cool. ciao

  114. Kev bangs the gavel.

  115. ralphm

    thanks all!

  116. Kev

    I'll write up some minutes and send them out at some point before too long.

  117. Fritzy

    Until we meet again.

  118. MattJ

    Kev, have you tried making people MUC admins? If it fails, it shouldn't

  119. Kev

    No, I just thought we couldn't do it for some reason.

  120. ralphm

    Kev: can you edit the room config?

  121. MattJ

    None that I know - just lacking automatically making service admins owners

  122. MattJ

    Oh

  123. Kev

    ralphm: I can, why?

  124. ralphm

    (as that's another way of adding moderators)

  125. Kev

    It's an extensive configuration.

  126. MattJ

    Whatever happened to the hats proposal?

  127. Kev

    MUC 3.0

  128. MattJ

    Simplicity is key :)

  129. ralphm

    MattJ: It needs to be written up still

  130. Kev

    Someone should sort that out. I don't think I have time, although I'd love to do so.

  131. ralphm

    I haven't gotten hold of hildjj yet

  132. ralphm

    but I haven't tried very hard lately

  133. MattJ

    It would help pubsub too at this point, it seems :)

  134. ralphm

    MattJ: yeah

  135. jkhii has joined

  136. ralphm has left

  137. jkhii has left

  138. MattJ has left

  139. Tobias has left

  140. Tobias has joined

  141. Tobias has left

  142. Tobias has joined

  143. Tobias has left

  144. Fritzy has left

  145. Fritzy has joined

  146. Fritzy has left

  147. Fritzy has joined

  148. Fritzy has left