XSF Discussion - 2015-11-16


  1. daurnimator

    http://blog.fastmail.com/2015/11/16/shutting-down-our-xmpp-chat-service/ :(

  2. fippo

    darunimator: yeah. I still <3 rob. mostly for his work on jabberd2 and his "dummies guide to digest-md5"

  3. ralphm

    Some discussion here: https://news.ycombinator.com/item?id=10572597

  4. daniel

    Btw is the fastmail blog being slashdotted right now or is it just my shitty Vietnamese provider having an issue with that?

  5. Ge0rG

    daniel: sounds like its your ISP

  6. Ge0rG

    loaded in <1s here

  7. daniel

    Ge0rG: OK thanks

  8. Ge0rG

    and again people are spreading FUD about XMPP....

  9. daniel

    if I remember correctly from what users told me fastmail just lacked a lot of features. so no surprise users are migrating to other services

  10. Ge0rG

    yeah, they didn't keep up-to-date

  11. Ge0rG

    that will happen to yax.im one day as well, unless I start supporting all the things needed by conversations, but not by yaxim ;)

  12. arune

    Ge0rG: do you follow the stats on your server of the usage yaxim vs conversations vs xabber?

  13. Ge0rG

    arune: nope. I might do a version query of all online clients once again.

  14. goffi

    hi

  15. Ge0rG

    hi goffi

  16. ralphm

    Ironic that this news brings about more tweets than the supposed number of users of FastMail's XMPP service.

  17. Link Mauve

    I know one of them.

  18. Ge0rG

    one of the twitterers?

  19. Link Mauve

    One of the FastMail XMPP users.

  20. Link Mauve

    He stopped self-hosting because he wanted a service that would last, without having to take care of it.

  21. Ge0rG

    and that's what he get.

  22. ralphm

    I don't blame FastMail for stopping support for their service if they have that low number of users

  23. Flow

    now with prosody-modules in debian, self hosting a prosody should be even easier

  24. Flow

    e.g. for me it means nearly zero maintenance overhead, just an "apt-get update && apt-get upgrade" once in a while (and I'm even considering automating it)

  25. Zash

    There are 9 modules in that package...

  26. Ge0rG

    make it moar!

  27. Zash

    8 actually

  28. Zash

    and two which enable support for carbons v0 and I have no idea why they included that

  29. MattJ

    File bugs

  30. Zash

    [...] the Debian package only includes modules that have been tested and used by the maintainers of the package. Please open a bug against the package with wish-list priority to request the addition of extra modules.

  31. mathieui

    “XMPP is overcomplicated, solving nothing IRC can't solve already ( imho, of course )” the things find myself reading…

  32. Zash

    mathieui: Let me introduce you to the only useful thing on Twitter: https://twitter.com/AvoidComments

  33. foss81405971

    Hehehe. People rabidly defend their old haunts. IRC gives us such great things like *.net *.split.

  34. Kevish

    IRC has a lot going for it, and you can't avoid netsplits if you want the kind of model they're dealing with (continuing to operate in the face of network partitioning).

  35. mathieui

    what it has going for it is userbase

  36. Zash

    mathieui, and that's the only thing that really counts..

  37. foss81405971

    Well, I haven't read the whole batch of RFCs, but understand about redundant links, and mesh networking. As far as userbase, the trolls on the "help" forums, are more guttural, and just what you'd suspect, not higher level, with more knowledge, as on newer protocols. For me, it's the WHOM that is the userbase.

  38. Zash

    Having read the IRC RFC(s?), I much prefer the XMPP ones.

  39. foss81405971

    If you doubt me, go asking about XMPP to IRC gateways, on IRC "help" forums. You'll wish you had NOT! BTW, methinks that generally, due to "connections per IP" rules, unless it's worked out with IRCops, et al, one would only be able to have their own private XMPP to IRC gateway. I've seen public servers with such, but not been able to unlock the powers which, might just be abandonware.

  40. Flow

    MattJ: What about my stanza ids in MAM patch? Just asking for the current state. Blocking things like this makes it hard to advance :(

  41. MattJ

    Flow, sorry, I've been away, and have had computer issues - I'm pretty much back now, and MAM is one of my current top priorities

  42. Flow

    MattJ: Glad to year. Let me know if you need anything. You said in your github comment there where some issues but didn't mentioned them. May I ask which issues you see with the current patch?

  43. Zash

    Github discussions >:(

  44. Flow

    Zash: Hate em too, but someone though it would be a good idea to use github

  45. Flow thinks xmpp.org should replace the MLs with discourse (which can be also used like MLs)

  46. Flow

    And maybe something like liquid feedback to get a sense on what the community thinks and to figure out what the consensus is

  47. ralphm

    I think we already have plenty ways to figure out what the community thinks

  48. ralphm

    And I don't think discussion issues are easily solved by adding/changing technology

  49. Flow

    ralphm: I don't that is true. This is just like saying e.g. changing your VCS from CVS to git wouldn't be beneficial for your project.

  50. Flow

    *don't think

  51. Flow

    It's hard to get an overview of the different opinions on e.g. "deprecating X" threads

  52. Kevish

    Don't you just read the thread?

  53. Flow

    especially if those threads continue for a long time

  54. Flow

    Kevish: Sure, but I don't remember everything from the thread if I look at it X weeks later

  55. Flow

    I had to re read everything

  56. Kevish

    Until someone decides to break the thread for some daft reason, as happened with IBR, but people can post in inappropriate threads on a forum too.

  57. Flow

    Kevish: Not as easily in e.g. discourse as it would be in some mail clients

  58. Kevish

    Surely the same is true with a forum that you need to read all the posts in a thread?

  59. Flow

    Kevish: For that I would use a liquid feedback system for

  60. Flow

    which gives you a good overview on what a community thinks

  61. Flow

    but still provides the community to figure out different solutions and change existing ones

  62. Flow

    until consensus is reached

  63. Flow

    (well until hopefully consensus is reached)

  64. Zash

    Or we could meet in a room and yell at each other until there is concensus :)

  65. Flow

    old school :)

  66. Zash

    I know this group that has their bi-annual member meetings on a web forum.

  67. Zash

    It's not very good.

  68. SamWhited

    Juser is moderated? Can I get added as a member or something by whomever the mod on that is?

  69. Kevish

    Should just be able to join it, I think.

  70. SamWhited

    I'm subscribed, but my messages are still being moderated, I think. Maybe there's another step.

  71. SamWhited

    I don't think I've ever actually posted before...

  72. Zash

    Maybe it just takes a while to iterate over the subscribers

  73. SamWhited

    I've been subscribed for a long time; just never posted.

  74. Laura

    hey folks

  75. simon

    hey laura.

  76. Laura

    Ok, last one! Who do we have today?

  77. adam waves

  78. Laura

    Hey adam and simon

  79. Laura

    Any raplhm or Will?

  80. Will

    Will here

  81. stpeter

    hiya

  82. Laura

    Ok, well no Ralphm but let's start!

  83. Laura

    Hi stpeter

  84. Laura

    *bangs gavel* Let’s start the meeting! Ok, last meeting of this Board, so a slightly different format: Agenda for today 1. Roll call and agenda agreement 2. Website - are we ready 3. Review commitment list from last time 4. Review items for discussion 5. AOB

  85. Will

    +1 on agenda ;-)

  86. stpeter

    I think ralphm might be online-ish because I've received a few emails from him so far today

  87. Laura

    Ha! Item #1 is covered - so let's move on

  88. Bunneh

    Laura: HTTP Error 404 :(

  89. Laura

    Bunneh ?

  90. Laura

    Item #2 Website!

  91. Bunneh

    Laura: HTTP Error 404 :(

  92. Laura

    simon / adam?

  93. Zash

    Feel free to kick Bunneh

  94. stpeter

    will do

  95. simon

    Well I spent a bunch of time getting the building working and getting the XEP building nicely integreated. We’re looking pretty good now although as winifried mentioned we need to fix something to get the right css files referenced.

  96. Laura

    Ok, sounds like progress!

  97. stpeter

    which are the right CSS files?

  98. simon

    missing css here: http://new.xmpp.org/extensions/xep-0079.html

  99. simon

    discussion here: https://github.com/xsf/xmpp.org/issues/91#issuecomment-157023684

  100. stpeter

    I see <link rel="stylesheet" type="text/css" href="../xmpp.css" /><link href="../prettify.css" type="text/css" rel="stylesheet" />

  101. stpeter

    those would be in the root directory

  102. stpeter

    but maybe they are elsewhere?

  103. adam

    still not sure exactly what's needed here

  104. simon

    peter: since they are XEP specific, it would be nicer to have them in /extensions and away from clashes with existing content.

  105. stpeter

    sure we can do that

  106. simon

    it’s a quick fix…

  107. stpeter

    yep

  108. simon

    but the good thing is that we have a complete build now for website + xeps ready to be published.

  109. Laura

    What does this mean for Go-Live? A few more days to tidy up?

  110. Kevish

    I did a (very little) looking at https for github pages, and it doesn't seem to be a thing, so I think we need to have a discussion with iteam about self-hosting (or someone telling me I'm wrong). As long as someone gives me reasonable notice I'll try to help with that.

  111. simon

    basically the infrastructure team can sync from https://github.com/xsf/xmpp.org/tree/gh-pages to the site. (Personally I’d leave it on github pages rather than create the work of self-hosting. Their call)

  112. adam

    I dont think we should let missing css on these pages keep us from going live. the content is readable and clear on these documents; I hadn't even recalled those pages *had* css until looking back at the originals justn ow

  113. simon

    adam +1

  114. Kevish

    simon: Can you get a mail sent to me at my work address with what needs doing, and I'll see what I can arrange?

  115. Will

    yup, just push the button. we can leave fixing the small things to the next lot ;-)

  116. simon

    Gory build details: https://travis-ci.org/xsf/xmpp.org

  117. simon

    kev: just git clone from the gh_pages branch on the repo.

  118. simon

    the builds are always published back to that.

  119. stpeter

    are we still using prettify.js or shall I remove references to that from the build scripts?

  120. simon

    peter - it’s called in some of the xep pages so I’d leave it there.

  121. stpeter

    ok

  122. SamWhited

    The syntax highlighting breaks if you don't have it, IIRC

  123. SamWhited

    on XML examples

  124. simon

    Kev: either pull to the webroot on your server or DNS change + add a https:// reverse proxy.

  125. Laura

    Ok, sounds like more discussion needed. Can we continue this chat after the Board?

  126. Kevish

    simon: Is it ok to just go live if I can arrange that, or do I need to wait?

  127. simon

    Thanks hugely to winifried for helping with the XEP build process.

  128. simon

    Just go live.

  129. Kevish

    OK, I'll try to find time.

  130. simon

    “move fast and break things” :)

  131. simon

    peter: are you looking at the css path issue or should I?

  132. Laura

    Ok, let's draw a line guys - we do have a few things left to discuss and the Board meeting shouldn't be for all this working out

  133. stpeter

    https://github.com/xsf/xmpp.org/pull/100 for the CSS files

  134. Laura

    #3 Commitment from last week

  135. ralphm

    hi

  136. Laura

    Simon - did you manage to progress with Treasurer role?

  137. Laura

    Hi ralphm

  138. simon

    laura: yes…

  139. simon

    let me find the answer.

  140. simon

    “I would if there was insurance.”

  141. Laura

    What does this mean?

  142. simon

    Jonathan Siegler would help with treasury role stuff if there was insurance. Just got the email and haven’t discussed more.

  143. simon

    Sorry, not super helpful.

  144. Laura

    What kind of insurance?

  145. simon

    I’m replying to find out… but I woudn’t persue it if we need insurance.

  146. stpeter

    some foundations have insurance shielding officers from liability

  147. Kevish

    Such insurance seems a reasonable thing to me.

  148. stpeter

    speaking of treasurers I will reimburse Ralph for some expenses this week

  149. Laura

    Ahh ok. Thanks Simon - we can always hand this to the "next Board" if needed

  150. stpeter

    Kevish: it might be worth investigating, yes

  151. Laura

    #4 Items for discussion

  152. stpeter

    I have never looked into it

  153. simon

    laura: /me is happy to throw this over the wall :)

  154. Laura

    The website, obviously, is being discussed

  155. Laura

    And New-Board will need to discuss FOSDEM and Summit (not really one for us to lead on)

  156. stpeter

    yep

  157. Laura

    #5 AOBs

  158. Laura

    Anyone?

  159. Laura

    I have 1, but happy to hear others first

  160. Kevish

    Thanks to Board for their service this term.

  161. stpeter

    indeed!

  162. Laura

    Ah, thanks Kvish

  163. Will

    thanks to adam/simon in particular for website efforts

  164. Laura

    New name.

  165. stpeter

    I have no AOBs

  166. Laura

    Yes, massive hats to them!

  167. Kevish

    Indeed, webiset goodness, etc.

  168. simon

    Still on the website: there’s many small website tasks that need some tech love at https://github.com/xsf/xmpp.org/issues

  169. ralphm

    Indeed, thanks all for another year

  170. Laura

    My AOB - did the Board see my email about the GSoC mentors and money?

  171. stpeter

    simon: I'll put some more time into those issues during the evenings this week

  172. ralphm

    Laura: I did. If the discussed concerns are resolved, let's go ahead

  173. simon

    kev: does iteam look after the jdev muc too?

  174. Kevish

    Laura: If I'd misunderstood and those were necessary expenses to get to the summit for the required number of days, we should pay them.

  175. Kevish

    (from the peanut gallery)

  176. ralphm

    simon: jabber.org is an independent thing

  177. Will

    re GSoC, I'm OK with re-imbursing

  178. Laura

    Is everyone happy for us to reimburse the GSoC mentors, as per the email?

  179. ralphm

    with coincidently similar people looking after it

  180. Laura

    That's me, ralphm and Will saying yes

  181. Laura

    Simon / adam - any comment?

  182. Kevish

    And Kev as GSoC admin ;)

  183. Laura

    Yes, and you Kevish

  184. simon

    +1 on reimbursing.

  185. adam

    +1 yes

  186. Laura

    Awesome guys.

  187. Laura

    I will let them know

  188. Laura

    And that folks, is that.

  189. Kevish

    Speaking of which, we should get a report out of them for what happened at the summit.

  190. ralphm

    simon: but to be clear, jabber.org is not XSF

  191. Laura

    Yes, agree Kevish

  192. simon

    we have an issue https://github.com/xsf/xmpp.org/issues/73 that needs some love from them.

  193. Laura

    I think's it's a wrap (before website chat continues!)

  194. ralphm

    simon: yes, intosi and Kev should look into that

  195. Laura

    Thank you all, for an amazing year!

  196. Laura

    *bangs gavel*

  197. ralphm

    Laura: and thank you for chairing again

  198. Will

    thank you

  199. simon

    thanks everyone

  200. adam

    yes, thanks indeed, everyone

  201. adam waves

  202. Laura

    Is it results of new Board on Wednesday?

  203. ralphm

    Laura: hmm?

  204. stpeter

    Laura: yes, or Tuesday I think - the meeting is tomorrow, no?

  205. ralphm

    tomorrow

  206. Laura

    Hence the question…

  207. Laura

    Ah good.

  208. stpeter

    Laura: thanks so much for chairing!

  209. Laura

    I have really enjoyed it - thank you all for putting up with me!

  210. SamWhited

    Laura++; excellent job all!

  211. stpeter

    :)

  212. stpeter

    OK I need to run off and do some blizzard prep here, bbiab

  213. Zash

    Thanks for boarding yall

  214. stpeter

    where are we working on website coordination BTW?

  215. simon

    I’m here if anyone wants to coordinate?