XSF Discussion - 2019-11-08


  1. pep.

    Ge0rG, so I have retracted the two agenda items, and it is clear that is is unclear how to proceed with adding agenda items anyway. There's still your proposed item left, maybe propose it to board for next week in addition? See what they decide the course of action should be.

  2. lskdjf

    > it's not about keeping records, it's about publishing them Yeah it would be great if the membership applications would not require people to write their personal information into a public wiki anymore.

  3. Ge0rG

    This has been addressed in the past repeatedly, with the consensus being that a public standards organization can require its prospective members to be known in public, mainly for transparency reasons

  4. Seve

    Definitively hard to trust an organization like that

  5. pep.

    Seve: what's your point?

  6. larma

    Transparency makes a lot of sense for Council, Board and official positions. But for membership it doesn't. Also what would be way more important than an e-Mail address would be the list of companies that pay a member/council/board, at least if we are targeting transparency and not just leak of private information...

  7. pep.

    Ge0rG: I believe there are other places we ought to be transparent first.

  8. pep.

    Seve: I just didn't get towards which part the sarcasm was directed, if there was :)

  9. eevvoor

    lskdjf‎ agreed

  10. eevvoor

    > Yeah it would be great if the membership applications would not require people to write their personal information into a public wiki anymore.

  11. pep.

    how does the no @by for origin-id work with j2j gateways? https://xmpp.org/extensions/xep-0359.html#origin-id

  12. nyco

    https://github.com/xsf/xmpp.org/pull/632 @iTeam, can someone please merge and deploy?

  13. Ge0rG

    pep.: why should a j2j gateway add origin-id?

  14. Ge0rG

    (I'm still of the strong conviction that origin-id must die)

  15. pep.

    Ge0rG, you'd have the original client add it?

  16. Ge0rG

    pep.: that's what it is for

  17. Ge0rG

    the main benefit of origin-id over @id in the stanza is to tell everybody "look, I'm smart and I can generate unique message IDs"

  18. pep.

    Ge0rG, I could see a use-case where the original client doesn't want anything their client sent leaking outside (apart from messages, of course). By this I mean having the j2j translate everything (not just routing)

  19. pep.

    I don't have this use-case myself (I think?)

  20. Ge0rG

    pep.: I can't follow

  21. pep.

    But then not having @by in origin-id is not an issue anyway, nvm

  22. pep.

    the gateway would just remove it and add its own

  23. pep.

    One could take a j2j gateway as a client in front of another (that's essentially what it is, right?)

  24. Ge0rG

    the j2j gateway is the client behind of another, isn't it?

  25. Ge0rG

    is there even a reasonable j2j gateway implementation anywhere?

  26. pep.

    no clue

  27. Ge0rG

    last time I checked there was no progress on this front for 15 years

  28. pep.

    I've only started thinking about it (wait for another 15 years), was curious about other things and that lead to j2j :x

  29. nyco

    Kev Guus (I don't know who else from iTeam) can you please deploy now https://github.com/xsf/xmpp.org/pull/632 ? sorry to insist...

  30. Kev

    That shouldn't need anyone from iteam, just needs a webbish person to hit merge, and it'll get autodeployed.

  31. Kev

    At least, unless something changed.

  32. nyco

    ok, so who are the webbish persons?

  33. pep.

    That is still undefined? I did ask once

  34. Kev

    I'm not involved in that at all - but it looks like Guus at least merges things, looking at past PRs.

  35. Kev

    jonas’ too.

  36. pep.

    Guus is board and jonas has rights but iirc he doesn't know why

  37. Kev

    Looks like it's usually jonas’ who approves stuff for the website, at least. For whatever reason.

  38. Kev

    Actually, no, might be an even mix of Guus and jonas’. But either way - they seem to be the main people doing it.

  39. nyco

    so I guess https://wiki.xmpp.org/web/XSF_Infrastructure needs some maintenance, right?

  40. Kev

    I do have the power to hit merge though, if you want me to with your Board hat on. I just won't have done any review.

  41. Kev

    That page does need looking at, but the question of the content of the website is independent of iteam.

  42. nyco

    I would not like to sound bossy or kind of totalitarian some reviews have been made by MDosch, Guus, Link Mauve, and mwild1 I feel like it is enough anyway, the newsletter already has been sent by email

  43. nyco

    oh, good precision: content vs infra, thx

  44. pep.

    I guess I'll add another item on board's agenda for next week.. Who is webteam.

  45. pep.

    And how to get in

  46. Guus

    I'm sorry, I'm in a 7 hour conference call with panicking customer

  47. Guus

    I can hit merge if you want, but unsure what I'm merging

  48. Guus

    oh, newsletter

  49. pep.

    It should be safe to merge

  50. Guus

    we've done that before

  51. Guus

    merged

  52. pep.

    Thanks

  53. Guus

    I need to go back in.

  54. Guus

    it'll take some time for it to be online

  55. Daniel

    👍

  56. Kev

    Thanks Guus. Sorry not to have been more helpful, nyco.

  57. Guus

    np

  58. nyco

    thanks all, it's done, it's cool, we progress, which is great, and yes please do propose that question for the board meeting

  59. Daniel

    Out of curiosity is there anyone in here who can build the website locally on their machine? Or is the only way to rebuild the website a mystery docker box?

  60. Daniel

    I was hunting down the doap thing which apparently is block by people not being able to debug the website build

  61. MattJ

    I wasn't aware of any mystery docker boxes

  62. Zash

    It's in the cloud, no?

  63. MattJ

    But I don't think I've ever built the websie locally either

  64. Guus

    I've used both the mystery docker box as well as through vagrant (as supplied in the git repo) in the past.

  65. Guus

    the vagrant build gives you more of a regular server to play with

  66. Guus

    Haven't used it in a while though.

  67. nyco

    please retweet: https://twitter.com/xmpp/status/1192836120725409794

  68. Daniel

    nyco, no link?

  69. nyco

    yep, I f*cked up this... :'( sorry...

  70. Guus

    Shit happens. Can't get it right all the time. Thanks for putting in all of that effort!

  71. Zash

    What Guus said

  72. pep.

    As a French national I feel the need to protest anyway. :p

  73. nyco

    always :)

  74. nyco

    I am a victim of the same fate

  75. Zash

    I reject your protest and substitute my own