XSF Discussion - 2013-01-22

  1. stpeter

    bear: I'm making progress on the FOSDEM scheduling...

  2. _mido_


  3. ralphm

    stpeter: good job on the schedule

  4. ralphm

    no sessions after 17:00?

  5. stpeter

    ralphm: actually, I'm adding a break at 14:00 and I'm just about to add another talk on the schedule (for 17:30-17:45)

  6. stpeter

    it's not good to have no break :)

  7. ralphm

    stpeter: ah, they mentioned not actually putting an item for a break

  8. stpeter

    oh really?

  9. ralphm


  10. stpeter

    so how do we handle that?

  11. stpeter

    no break, or just don't list it?

  12. ralphm

    don't list it

  13. stpeter

    sure, that's easy enough :)

  14. stpeter

    ah good, I see that https://fosdem.org/2013/schedule/day/saturday/ is up to date (sort of)

  15. ralphm

    from the list:

  16. ralphm

    I noticed that Jeremy put a "wine lunch break" in the schedule. I don't think that's really necessary. I think the schedule is a lot cleaner if there's an empty slot where lunchtime takes place, rather than a slot that says 'lunch break'. - Philip

  17. stpeter


  18. stpeter

    I'm still way behind on email, although I did get under 1000 messages today ;-)

  19. ralphm

    I guess you are not actually on that list

  20. stpeter

    good, so I have two excuses ;-)

  21. ralphm

    next time I should use an organisational address

  22. stpeter

    sure we can set up fosdem@xmpp.org

  23. stpeter goes back into pentabarf to edit times later in the day

  24. ralphm

    are you putting in a lightning talks slot?

  25. stpeter

    I'm happy to do so

  26. stpeter

    would you like that in the middle of the afternoon, or at the end (or both)?

  27. ralphm

    let's see

  28. stpeter

    we could do 30 minutes of lightning talks after the break (at 14:30)

  29. ralphm


  30. stpeter

    I always like the "stump the experts / general discussion" slot

  31. stpeter

    people find that helpful

  32. ralphm

    Do the colors have a meaning?

  33. stpeter

    I don't think so

  34. ralphm

    oh sure!

  35. stpeter

    ok, I'm going to put that after XMPP 101, then

  36. stpeter

    seems like a good time to get general questions out of the way

  37. ralphm nods

  38. stpeter

    I'll put you in charge of that session ;-)

  39. ralphm

    that'd be good

  40. ralphm

    I'll bring that hat

  41. stpeter


  42. stpeter

    me too

  43. ralphm

    I was thinking (way too late now) that having an XMPP fleece jacket would be nice, too.

  44. stpeter


  45. stpeter

    next year ;-)

  46. stpeter


  47. stpeter


  48. stpeter

    now updating in Penta

  49. stpeter wonders why everything in Penta defaults to FOSDEM11 :)

  50. ralphm


  51. ralphm

    probably a configuration thing that they haven't fully digested

  52. ralphm

    this stuff was created for ccc

  53. stpeter nods

  54. stpeter


  55. stpeter

    all data updated

  56. stpeter

    now we wait for https://fosdem.org/2013/schedule/day/saturday/ to be updated

  57. stpeter

    I assume they have a cron job for that :)

  58. ralphm


  59. stpeter

    I think I didn't add some of the biographies

  60. stpeter

    or didn't receive them

  61. stpeter checks

  62. ralphm

    at least one new item now :-)

  63. stpeter

    do we need to provide email address for all speakers?

  64. stpeter

    I suppose it can't hurt, eh?

  65. stpeter


  66. stpeter

    brb, need tea :)

  67. stpeter

    maybe I'll give a lightning talk about "the challenges of running a large public IM service and what we need to fix"

  68. ralphm


  69. ralphm

    stpeter: do away with the users :-)

  70. stpeter volunteers some people for http://wiki.xmpp.org:12480/web/Summit_13#Short_Talks_and_General_Updates without asking them :P

  71. stpeter


  72. stpeter

    https://fosdem.org/2013/schedule/day/saturday/ is done

  73. stpeter posts to the summit@ list

  74. stpeter

    hi Jef

  75. stpeter

    Jef: see the last talk at the FOSDEM schedule pasted above -- someone is very excited about your File Information Sharing proposal :)

  76. Jef

    stpeter, who is?

  77. Lance

    which xep is that? is it still in inbox?

  78. stpeter

    Diana Cionoiu -- she works http://yate.null.ro/pmwiki/

  79. Jef

    It is still in inboc

  80. stpeter

    Lance: yeah we need to get it out of that damn inbox

  81. Jef

    I 've been having problems with it. I need someone to tell me what's wrong

  82. Lance

    what's the name for it?

  83. stpeter

    Jef: my apologies, I haven't had time to really look at it carefully, but I'll need to do that before FOSDEM

  84. stpeter


  85. Lance

    nice. thanks

  86. Lance starts reading

  87. stpeter

    Lance: thank Jef, he did all the work ;-)

  88. Jef

    lol, it needs much more work

  89. Jef

    I can't find the talk

  90. Lance


  91. stpeter


  92. Jef


  93. Jef

    OMG! she is calling it awesome

  94. stpeter

    oh hmph, they want me to update the speak bios from past years?

  95. Jef

    I think I'm going to cry

  96. stpeter


  97. Jef

    I'm so happy

  98. stpeter

    I am pretty sure she was talking about your proposal -- we had a brief IM chat about it a bit earlier but she had to run before I had a chance to verify :)

  99. Jef

    when will the video be posted?

  100. stpeter posts http://xmpp.org/2013/01/the-fosdem-schedule-is-set/

  101. stpeter

    Jef: we will try to stream it via Hangouts and YouTube (yeah, I know, sorry)

  102. Jef


  103. Lance finishes reading fis

  104. Lance

    not bad. i would have imagined it working over disco though

  105. Jef

    that's how xep-135 does it

  106. stpeter


  107. stpeter

    I need to look at them both :)

  108. stpeter

    135 was just an initial exploration

  109. Jef

    well, certainly Diana has given me a lot of motivation to conclude the work

  110. stpeter


  111. Jef

    I will be sending you something this week, and send me an email whenever you like at: jefry.reyes@gmail.com

  112. stpeter


  113. stpeter

    I will try to review them both tonight

  114. Jef


  115. Lance ponders

  116. Lance

    135 style disco plus http://xmpp.org/extensions/inbox/xml-media-element.html in an identity extension to include the file metadata element

  117. Lance

    meh, the wrapping part borders too much on the ugly side

  118. Jef

    Lance, I thought 135 was ugly, but then I couldn't make fis much less ugly

  119. Jef

    I need feedback on fis

  120. Jef

    Lance, how do you think it could be better?

  121. Lance

    conceptually, you have it at about as good as can be

  122. Lance

    you're doing better traffic wise than disco by allowing metadata inline with listings

  123. Lance

    the xml can be tidied up, proper namespaces, etc

  124. Lance

    i do prefer the disco route because that's the standard way of discovering things and related items, and tools exist to browse it already

  125. Lance

    but meh, whatever. if it works it works

  126. Lance

    the only other thing i see is with the searching, since you would need to just go with a dataform immediately

  127. Lance wishes jabber:iq:search included a node parameter

  128. Jef

    Lance, it is, isn't it?

  129. Jef

    it is included

  130. Jef

    wait.. what do you mean as a node parameter?

  131. Lance

    no, i meant if it allowed you to do <query xmlns="jabber:iq:search" node="urn:xmpp:fis">

  132. Jef


  133. Jef

    is that possible?

  134. Lance

    not with xep-0055 as is

  135. Jef

    xep-55 is a little restrictive

  136. Lance

    which i guessed was why you were making the search query a child of the fis match element

  137. Jef

    a bloody mess

  138. Lance

    is the inbox version your latest draft? or have you made edits since then?

  139. Jef

    no haven't, life has been kicking my butt lately

  140. Jef

    how do you think disco can be included?

  141. Jef

    not for the search I suppose?

  142. Lance

    use disco to walk the file tree and get file names, and use a fis request to get the metadata for a file/directory that you've found

  143. stpeter nods to Lance

  144. Jef


  145. Lance

    the downside to that is it can't provide the file meta during the walk process

  146. Lance

    but, it can provide the minimum you're required, which is just the names

  147. Lance

    well, it can include the full meta data, but that requires an x-form with the xml wrapper element

  148. Lance

    but that's where it starts getting ugly

  149. Jef

    yea... thats what I was trying to avoid, uglyness

  150. Lance nod

  151. Jef nods

  152. Jef strokes his bear and nods

  153. Lance

    i'll whip up some examples to see how things can be tidied up, as is without disco

  154. Jef

    that would be awesome

  155. stpeter perhaps senses a topic to discuss at the XMPP Summit in Brussels :)

  156. Lance

    it will be discussed at fosdem for sure

  157. Jef