XMPP Council - 2012-03-14


  1. ralphm waves

  2. MattJ laps at the shore

  3. Kev

    Oh good, we're going to have one of *those* meetings.

  4. stpeter

    heh

  5. Kev

    Right, it's time.

  6. Kev

    1) Roll call.

  7. Kev

    I don't see Tobias online.

  8. Kev

    But he sent apologies, so that's fine.

  9. Kev

    I also don't see a Matt Miller, who also sent apologies.

  10. MattJ

    Ahoy

  11. Kev

    I do see a me.

  12. Kev

    ralphm?

  13. Kev

    He was here five minutes ago!

  14. stpeter

    heh

  15. MattJ

    Give him until :05

  16. MattJ

    We don't have much on the agenda

  17. Kev

    Right.

  18. ralphm

    I already waved

  19. Kev

    2) Message Forwarding

  20. Kev

    Last call's expired, I think, so we should vote on Draftness.

  21. MattJ

    Hmm, I read the feedback but it is out of my infamous short-term memory

  22. Kev

    The only feedback we had in the LC thread was Zash.

  23. Zash

    Noone but me replied?

  24. MattJ pulls it up

  25. MattJ

    Didn't MM?

  26. Kev

    Not in the LC.

  27. Kev

    There were previous threads (linked by Zash).

  28. MattJ

    Hmm, maybe he commented here when we voted on the LC

  29. Zash

    http://logs.xmpp.org/council/120215/#16:20:39

  30. MattJ

    Ok, so we should poke him for his comments

  31. Kev

    And maybe we should provide some sort of guidance for uses of 197.

  32. Kev

    *297

  33. Kev

    MattJ: Shall I leave that to you? :)

  34. MattJ

    Ok :)

  35. Kev

    Excellent.

  36. Kev

    Presumably we then LC it again.

  37. Kev

    ralphm: You happy with this plan?

  38. ralphm

    that sounds reasonable

  39. Kev

    3) http://xmpp.org/extensions/diff/api/xep/0172/diff/1.0/vs/1.1rc1

  40. ralphm

    Although I'm not sure if another LC is needed

  41. Kev

    I'm +1

  42. Kev

    ralphm: I don't think it hurts, and we want to solicit opinion.

  43. MattJ

    +1

  44. ralphm

    +1

  45. Kev

    4) Date of next meeting. 4pm next Wednesday, UK time?

  46. MattJ

    I see what you did there :)

  47. MattJ

    wfm

  48. stpeter

    UK time?

  49. stpeter

    is that the same as this time UTC?

  50. Kev

    stpeter: you claimed it was difficult because of DST, so I was being explicit.

  51. Kev

    Yes, it is for next week.

  52. stpeter

    Kev: wasn't difficult for me at all, but I'm more flexible than Matt is

  53. ralphm

    Just always use UTC.

  54. stpeter

    yep

  55. Kev

    1600 GMT it is :)

  56. ralphm

    I think the difficulty was in figuring out local time, not the actual time of day.

  57. Kev

    Actually.

  58. Kev

    Is it this Sunday they changed? :)

  59. ralphm

    1600 UTC for all others

  60. Kev

    No, the following.

  61. Kev

    So yes, 1600.

  62. Kev

    5) AOB?

  63. ralphm

    US changed a few days ago, we change last weekend of March

  64. stpeter

    a new verson of XEP-0301 will find its way to me soon, according to the author

  65. Kev

    Righty.

  66. MattJ

    Just a note that I have located the MAM XML, have reviewed it and know the changes I want to make, and have it open in an editor to make them

  67. Kev

    We don't need to do anything with that, I think.

  68. stpeter

    I need to address XEP-0047 call for experience feedback

  69. stpeter

    probably there are other tasks I need to complete, too

  70. Kev

    So no AOB, then?

  71. stpeter

    not really

  72. Kev

    Excellent.

  73. Kev

    Thanks all.

  74. Kev bangs the gavel.

  75. stpeter

    yay

  76. MattJ

    Thanks

  77. stpeter

    brb

  78. MattJ

    Is there a board meeting today?

  79. Kev

    Oh, right - I submitted the XSF's application to GSoC btw.

  80. Kev

    We could do with more ideas, still.

  81. stpeter reloads the ideas page

  82. ralphm

    stpeter: I think that byte-for-byte comparison of resourcepart is problematic.

  83. ralphm

    stpeter: e.g. in python, I get unicode objects from my parser

  84. ralphm

    i.e. the attribute values (where they usually appear) are already decoded from their UTF-8 representation

  85. dwd

    MattJ, Yes, there's a board meeting just starting.

  86. stpeter

    ralphm: feel free to post to the list about that -- I tend to agree, but I'm not decided yet

  87. dwd

    ralphm, I agree that actual byte-for-byte is wrong, but I don't think we need go further than codepoint comparison or perhaps canonicalization.

  88. ralphm

    dwd: right

  89. ralphm

    so I sent that message to the list

  90. stpeter

    so I saw, thanks