XSF Discussion - 2020-05-14


  1. rion

    How to become an author of xep-0371? Seems like the original author doesn't care about the future of the xep.

  2. Alex

    Reminder for those who have not reapplied yet: https://wiki.xmpp.org/web/Membership_Applications_Q2_2020

  3. Holger

    https://xmpp.org/community/membership.html#application talks about "the first two weeks of January, April, July, and October", has this changed or are things just delayed (this time)?

  4. Alex

    looks like we need to update the webpage. dates have slipped many years ago

  5. Holger

    Ah :-)

  6. jonas’

    rion, ask council :)

  7. MattJ

    Sorry, forgot I can't make the meeting today

  8. pep.

    :)

  9. pep.

    !

  10. pep.

    It's time

  11. pep.

    ralphm, Guus, Seve

  12. Guus

    o/

  13. Guus

    uhoh

  14. pep.

    hmm.

  15. pep.

    I don't really want to skip this one

  16. Seve

    Hey

  17. pep.

    woo

  18. pep.

    Let's start and hope it'll summon ralphm

  19. pep.

    1. Agenda

  20. pep.

    - Add emus to commteam

  21. pep.

    I also have an item to add re ISOC foundation

  22. pep.

    Anything else?

  23. Guus

    what's the status on that adopt-a-char issue?

  24. Guus

    are we still blocked on figuring out how to vote?

  25. Guus

    if so, I'd like to see if we can get that oving.

  26. Guus

    *moving

  27. Seve

    I haven't heard any news on this, personally.

  28. pep.

    Last time I checked that was up to Flow. I think he meant to have a look at updating memberbot

  29. Seve

    (No items from me)

  30. Guus

    (to be added to agenda instead of disccussed right now)

  31. pep.

    right

  32. pep.

    2. Add emus to commteam

  33. Seve

    He has been taking care of the newsletter, I think it would help the process. I'm +1

  34. pep.

    It was mentioned this week in their channel. emus has been helping for some time now with the newsletter

  35. pep.

    Seve, let's wait for the motion :p

  36. Guus

    Who's actually the team lead for comm?

  37. Guus

    nyco?

  38. pep.

    I'm not entirely sure, but the question was indirectly raised by JC

  39. Seve

    Guus, the commteam is a bit "afk" lately (I'm included there)

  40. pep.

    emus asking for people to publish things on social media

  41. Guus

    https://xmpp.org/about/xsf/comm-team.html

  42. Ge0rG

    Wasn't there an attempt to hire a social-media contractor?

  43. pep.

    And JC wondering if he should give him access (hence asking team membership)

  44. pep.

    Ge0rG, it's in the works yes

  45. pep.

    I'll update on that in commitments

  46. Guus

    In any case, I'm happy to have emus added.

  47. Guus

    is JC asking for him to be added, or is he asking himself? πŸ™‚

  48. pep.

    emus is asking, from my PoV JC just prompted the discussion

  49. Guus motions that Edward 'emus' Maurer is to be added to the Commteam workteam.

  50. pep.

    +1

  51. Seve

    +1

  52. Guus

    +

  53. Guus

    shees

  54. Guus

    +1

  55. Guus

    sorry πŸ™‚

  56. pep.

    Ok. 3 +1s ! emus congrats

  57. Guus

    Thanks for stepping up, emus !

  58. Seve

    emus, woo :)

  59. nyco

    ...

  60. pep.

    nyco, ?

  61. Guus

    Does commteam have access to the site?

  62. Guus

    as in, first task: add yourself to the website in the new role? πŸ™‚

  63. Guus

    (for which we probably need iteam to add him in the correct github team?)

  64. Guus

    MattJ, in case you read back notifications, can you facilitate that?

  65. pep.

    As a note, I'd like us to figure out how to have teams handle that themselves. I'm curious why we need board here

  66. nyco

    Wat

  67. nyco

    Who soeaks where?

  68. pep.

    nyco, I'm curious if you have any comment, I'd like to hear them

  69. nyco

    Ping

  70. Guus

    pep. probably mandated in the bylaws. We can go through them out-of-band if you want.

  71. nyco

    hi

  72. Guus

    for now, let's move on πŸ™‚

  73. pep.

    3. ISOC Foundation grant

  74. nyco

    soryr to interrupt, sometimes I receive some notifications from I don't know where nor I don't know who, but no always

  75. nyco

    ok, sorry

  76. pep.

    https://www.isocfoundation.org/grant-programme/emergency-response-grant-programme-covid19/

  77. pep.

    The isoc foundation is offering a grant that non-profits can apply to in order to help with the current situation (covid)

  78. pep.

    The application period is until the 17th though, so pretty quick. I personally don't have many ideas but if anybody is interested in suggesting something I'd like board to consider it before the deadline

  79. Guus

    We briefly discussed this yesterday (day before yesterday maybe?). I do like attracting a grant like this, but a) it's short notice, and b) I'm unsure if we'd qualify for this particular one.

  80. Guus

    If someone has a good idea to move this forward, I'm all ears though.

  81. pep.

    I'm also unsure, but if anybody is willing to take up on the challenge I think we should hear it yeah

  82. Guus

    The ISOC offered grand discussion did trigger an idea with me. Should the XSF aim to have more of a team that chases down grants like these, and have proposal drafts available to answer? We might even want to consider hiring people to do this - basically have them pay for themselves?

  83. Guus

    grand/grant

  84. Guus

    Not sure exactly what this should look like, but it might be worth entertaining the thought.

  85. pep.

    hmm, why not. I'm open for discussion

  86. Guus

    let's ponder, and revisits in a next meeting?

  87. pep.

    In the meantime I'll send an email regarding this specific grant

  88. pep.

    to members@

  89. Guus

    ok, tx

  90. pep.

    That does imply board is willing to give their approval before the 17th though, right

  91. Seve

    For this specific case though, I'm out of ideas. I hardly see how could we present something for that grant, but it will be great to hear any ideas from that mail

  92. Guus

    pep. I don't think that that's implied.

  93. Guus

    it's implied that board will at least see what comes out of it πŸ™‚

  94. pep.

    I mean, discuss it, not approve it

  95. Guus

    right

  96. Seve

    Of course

  97. pep.

    Okay

  98. pep.

    4. Adopt a character

  99. pep.

    As mentioned above I don't think there is much progress since last time, but that's not up to me

  100. Guus

    I'd just like to know where we are on this, and, if board needs to do something to move this along?

  101. Guus

    flow ?

  102. pep.

    I'm happy to leave this with flow for the time being

  103. Seve

    We can contact him out of this meeting and come back with an update. Then decide.

  104. Guus

    sure

  105. pep.

    Though an update would be nice

  106. pep.

    5. Commitments

  107. pep.

    Regarding the marketing person, MattJ and I have had a chat with her, we've tried to state what we'd be expecting of a marketing/comms person and it seems she had a bit more clue compared to when she joined the meeting :)

  108. Guus

    where does that leave the effort?

  109. pep.

    She said she'd send us a sketch of what she thinks we can do, alongside with her rates

  110. pep.

    (is that the word?)

  111. Seve listens

  112. Guus

    that's _a_ word - unsure which one you're talking about πŸ™‚

  113. pep.

    So I'm waiting on this at the moment

  114. pep.

    "rates", money things

  115. Guus

    yeah, fair enough. I usually use the singular 'rate' - but none of us are native speakers so we're forgiven πŸ™‚

  116. Seve

    :D

  117. Guus

    Anyway, good news that we've engaged

  118. pep.

    That's it from me.

  119. Seve

    Looking forward for the sketch

  120. pep.

    6. AOB?

  121. Seve

    None here

  122. Guus

    none here

  123. jonas’

    none here

  124. pep.

    :)

  125. pep.

    Close then!

  126. pep.

    I'll send minutes later

  127. Guus

    Next week is ascension day

  128. Guus

    is that reason to postpone a meeting?

  129. Guus

    or shall we simply see who turns up?

  130. pep.

    Not for me

  131. Seve

    Wohoo, thank you pep.

  132. Guus

    we might make a family day out of it, unsure yet.

  133. Guus

    I'm happy to just see who turns up

  134. Seve

    Me too

  135. Guus

    (at the meeting, not the family day)

  136. pep.

    wofs

  137. Seve

    Oh..

  138. pep.

    :D

  139. pep.

    wfs*

  140. pep.

    wfm.

  141. pep.

    hard to type on a keyboard

  142. Guus

    ok +1w then

  143. pep.

    Thanks all

  144. Guus

    thanks!

  145. Seve

    πŸ™Œ

  146. flow

    re the adopt-a-character and members opinion poll: I am (more or less) blocked on https://github.com/andrewcmyers/civs/issues/33

  147. flow

    if CIVS would offer an option to generate N vote URLs then we could let every member draw exactly one URL from membersbot

  148. flow

    (of course this needs adjustment to membersbot, but this should be trivial)

  149. flow

    so I guess +1 the issue pls, and maybe we have an perl hacker amoungst us who wants to add that feature to CIVS

  150. Guus

    Ok. If, in the interest of time, we want to move without using CIVS, I'd be fine with that.

  151. Guus

    If we end up postponing this indefinitely only to be able to test-drive CIVS, that kind of defeats the purpose

  152. Guus

    Not that I'm in a hurry

  153. flow

    Guus, well if there is a tool that fits the(/my) requirements I would happily use it

  154. flow

    + I really like to use it as trial run for condorcet voting and allow members a first impression of it

  155. Guus

    I think your requirements are higher than the requirements πŸ™‚

  156. Guus

    sure, I'm not opposing that

  157. Guus

    Just want to make sure you don't feel obliged to chase down a dependency on our account.

  158. flow

    I kinda could go with a system that does no condorcet voting, but I could not find a sensible one

  159. emus

    Goodday guys πŸ‘‹ Happy to join the team. Sorry, I missed the meeting 😫

  160. pep.

    fwiw I'm not against testing Condorcet for this "non-essential" task

  161. pep.

    (I also don't care really much about the character personally, sorry but not sorry)

  162. flow

    pep., no need to apologize, you are entitled to your own opinion

  163. flow

    (in this case)

  164. flow

    ;)

  165. pep.

    nyco, btw, still happy to hear your comments if you have any, here or in private

  166. nyco

    About ?

  167. pep.

    Your messages above happened while we were talking about emus

  168. pep.

    Since you're also commteam I thought it might have been related

  169. MattJ

    emus, what's your Github username?

  170. MattJ

    (and congrats :) )

  171. emus

    MattJ: Thanks, just check the recent drafts for the XMPP Newsletter, Im was the creator, echolon wait

  172. emus

    yes its only Echolon

  173. MattJ

    Ok, added. I think you may receive an invite

  174. emus

    MattJ: Yes. already accepted, thanks!

  175. pep.

    Minutes sent

  176. pep.

    https://www.laquadrature.net/en/2020/04/23/our-arguments-against-the-french-contact-tracing-app-stopcovid/

  177. pep.

    can the XSF also make a statement against solutionism or sth? (the idea that everything can be solved with technology)

  178. pep.

    also related: https://edri.org/blog-ban-biometric-mass-surveillance/

  179. emus

    I would personally agree to work on a draft, but Iag time this weekend πŸ˜•

  180. emus

    I would personally agree to work on a draft, but Iag time this weekend πŸ˜•

  181. xnamed

    hello, I'm confused about connection error from xmpp.org with my server

  182. xnamed

    >>>> admin@jabber.eu.org/eyeCU 22:03:05 +19238 >>>> <iq xmlns="jabber:client" to="xmpp.org" type="get" id="sid_212"> <query xmlns="http://jabber.org/protocol/disco#info"/> </iq> >>>> admin@jabber.eu.org/eyeCU 22:03:05 +4 >>>> <iq xmlns="jabber:client" to="xmpp.org" type="get" id="sid_213"> <query xmlns="http://jabber.org/protocol/disco#items"/> </iq> <<<< admin@jabber.eu.org/eyeCU 22:03:05 +566 <<<< <iq xmlns="jabber:client" from="xmpp.org" xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace" to="admin@jabber.eu.org/eyeCU" type="error" id="sid_212"> <query xmlns="http://jabber.org/protocol/disco#info"/> <error xmlns="jabber:client" type="wait" code="504"> <remote-server-timeout xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/> <text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace">Connection failed: connection refused</text> </error> </iq> <<<< admin@jabber.eu.org/eyeCU 22:03:05 +15 <<<< <iq xmlns="jabber:client" from="xmpp.org" xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace" to="admin@jabber.eu.org/eyeCU" type="error" id="sid_213"> <query xmlns="http://jabber.org/protocol/disco#items"/> <error xmlns="jabber:client" type="wait" code="504"> <remote-server-timeout xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/> <text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace">Connection failed: connection refused</text> </error> </iq>

  183. Zash

    xnamed, what's confusing about it?

  184. xnamed

    Zash, what's the problem

  185. Zash

    The local server could not connect to xmpp.org.

  186. Zash

    From "connection refused" I would guess that it either failed to look up the SRV records and tried to connect to the wrong port, or that there's a local firewall that blocks connections to the port xmpp.org uses.

  187. xnamed

    I think the second possibility

  188. xnamed

    thank you Zash

  189. flow

    I always think it would be nice if the textual error message would include the invovled tcp 4-tuple

  190. flow

    I always think it would be nice if the textual error message would include the involved tcp 4-tuple

  191. Zash

    Hmm

  192. Ge0rG

    now is a good time to point out that the text element of stream errors is not supposed to be user-understandable

  193. Zash

    I'm not sure we should shove too many details at users, but it can be useful.

  194. flow

    my counter argument is always that users who do not understand it could at least give the text to their admin

  195. Zash

    When will I find the time and energy to write that Extended S2S Error Info XEP?

  196. flow

    because there is a reason why some UIs just tell the user that "something bad happened, try again later"

  197. Ge0rG

    The <error/> element: MAY contain a <text/> child element containing XML character data that describes the error in more detail

  198. flow

    so you usually want to display this to the user, with an extra button that leads to a detailed error report

  199. flow

    that he/she is not expected ot understand

  200. Zash

    While we have that single <text> element, we could at least try to have the beginning of it easily understandable, and then go into more details.

  201. flow

    I would totally support adding a "dump-user-text" element

  202. flow

    but the existing <text/> should probably contain as much as details as possible

  203. flow

    err dumb-user-text

  204. Ge0rG

    for dumb-user-text all you need is a set of strings for all well-known conditions

  205. Zash

    If they're well-known conditions, wouldn't conditions be better?

  206. Zash

    as in like the tag names we have, but moar!

  207. Zash

    <certificate-expired/>, <connection-refused because="firewall"/>...

  208. flow

    can't catch them all

  209. flow

    but yes, why not, we certainly will end up with a textual escape hatch

  210. Zash

    we already have that

  211. flow

    great, I like hatches. but not the one from lost

  212. xnamed

    I remember had certificate expired error long ago but this time it's something else

  213. xnamed

    I think good idea to add details

  214. pep.

    > flow> my counter argument is always that users who do not understand it could at least give the text to their admin I agree. For the 5% that do send things to their admin, it's good when they have more than "it doesn't work"

  215. Link Mauve

    The admin can usually correlate the timestamp with a particular s2s attempt in their debug logs.

  216. Link Mauve

    But +1 for more understandable errors.

  217. pep.

    Maybe the admin is not that admin

  218. Link Mauve

    It’s a good thing for users who are their own admin too. :)

  219. Ge0rG

    Link Mauve: "yesterday I couldn't talk to Jack"

  220. Ge0rG

    And then you have 2GB of server logs and they have three Jacks on the roster

  221. xnamed

    What if the admin like me doesn't have access to the debug logs?

  222. pep.

    Compared to yesterday I got a weird message when talking to Jack: "something something error 1235"

  223. Zash

    I'm still kinda proud of the new certificate related s2s errors in Prosody (trunk)

  224. Link Mauve

    xnamed, uh, then you can’t debug.

  225. Ge0rG

    I sometimes get screenshots from users, even for errors that were toast messages.

  226. Ge0rG

    They manage to make a shot of their mobile screen in the 1 or 2 seconds that the toast is visible

  227. Ge0rG

    Zash: a pity that I can't see them.

  228. Zash

    xnamed, with my iteam hat on, I see no trace of any connection to xmpp.org from that server.

  229. Zash

    Ge0rG, not?

  230. Ge0rG

    Zash: I'm not checking certificates

  231. Ge0rG

    But maybe one day I could run through all domains from my users' rosters and s2s ping them to collect certificate validity data and to be able to decide whether to enforce certificates after that.

  232. Zash

    I hope we can improve DNS and TCP related errors too

  233. Zash

    Currently you get e.g. > Server-to-server connection failed: unable to resolve service or > Server-to-server connection failed: connection refused

  234. Ge0rG

    And some clients are only wide enough to show "Server-to-server connection fa..."

  235. Zash

    Maybe someone could improve that as well

  236. Zash

    Compressed jargon doesn't feel like the solution, especially not if we want more details in there.