XSF Discussion - 2019-09-26


  1. jonas’

    MattJ, after council meeting isn’t really going to work for me, I’m usually preparing dinner then. I assume weekends aren’t going to work for you?

  2. MattJ

    Usually not, but I might be able to make this Sunday work

  3. jonas’

    SMS-based 2fa is very convenient with MAXS ;-) (cc and thx @ flow)

  4. Ge0rG

    jonas’: it's also reducing the number of factors.

  5. jonas’

    Ge0rG, yeah

  6. jonas’

    although that depends really

  7. jonas’

    but in any case, I’m not fond of SMS based 2fa anyways

  8. jonas’

    I don’t trust the phone or phone network with that

  9. MattJ

    I agree, MAXS makes it easier

  10. MattJ

    and it's not really removing a factor, it just means you have to have your phone or your laptop, the other factor is still the password

  11. MattJ

    Unless you have the password saved on the laptop :)

  12. MattJ

    Huh, we swapped rooms

  13. Ge0rG

    MattJ: or in the app on your phone

  14. nyco

    test

  15. Kev

    toast

  16. Guus

    donkey!

  17. nyco_

    5

  18. nyco_

    _o/

  19. nyco_

    Ralph is not joining, excused by email

  20. Seve

    Can someone else chair today, please?

  21. Guus

    Hi guys

  22. Guus

    MattJ - are you around?

  23. MattJ

    Here

  24. nyco_

    quorum

  25. Guus bangs the gavel

  26. Guus

    Hello, and welcome to the umptieth edition of the XSF board meeting!

  27. Guus

    1) Role call and agenda

  28. MattJ

    Here

  29. Guus

    we've established that everyone is here, but Ralph that just sent an email to apologise

  30. Guus

    as usual, the agenda is driven by our Trello board at https://trello.com/b/Dn6IQOu0/board-meetings

  31. MattJ

    Re. agenda: I propose we tackle some of the items we didn't cover last week, due to the length of the DOAP discussion last week

  32. Guus

    does anyone want us to address anything that's not on there?

  33. MattJ

    and if we have time, we can revisit DOAP

  34. Seve

    Yes, I would also like to do that, MattJ

  35. Guus

    I have no preference either way.

  36. Seve

    (And I do not have anything for the agenda)

  37. Guus

    Unless nyco strongly objects within the next few moments, so it shall be then.

  38. Guus

    2) Confirm minute taker

  39. Guus

    Who would be so kind?

  40. nyco_

    I object this objection! :)

  41. MattJ

    I'll do it

  42. Guus

    Anyone? We'd be helped a lot by someone taking notes, compiling them and sending them on the members lists after the meeting. There's nothing more to it.

  43. Guus

    Thanks MattJ - if anyone that's not also taking part in the discussion would consider doing this next time(s), please!

  44. Guus

    3) Topics for decisions

  45. Guus

    3.1) Sponsorship request

  46. MattJ

    Ralph isn't here, but indicated he would rather decline this unless we can determine their relationship with XMPP

  47. Guus

    we received this offer: > I represent a company called TheBestVPN.com and we'd like to make a sponsorship for XMPP. > Can you let us know if you're accepting any new sponsorship request and are there any perks associated with it?

  48. MattJ

    Also, relatedly, I just searched my inbox to find the email from Peter

  49. MattJ

    and turned up an email from someone at TheBestVPN.com to a Debian mailing list, which looked like a thinly-veiled SEO attempt

  50. Seve

    I tried to find some information about them on the Internet but it is not quite clear to me if there is a real support for XMPP or it is a "kind of SEO request"

  51. Guus

    I'm not sure if we should limit ourselves to sponsors that have a direct relation to XMPP

  52. nyco_

    fine, so be it: it's no

  53. MattJ

    I don't see anything particularly shady in any of it itself, but we've previously declined SEO-only sponsors, and I'm inclined to maintain this policy

  54. nyco_

    do we need to debate more?

  55. Guus

    I do think we should not have sponsors that only want to use us for blatant SEO

  56. nyco_

    they are bad SEO then, because you can some for free

  57. Guus

    Well, this guy didn't say/do anything to suggest that this is a SEO attempt.

  58. Seve

    Guus, I think we should not close the doors to any sponsors, either XMPP supporters or not, but yeah, not only SEO requests

  59. Guus

    He just offered to sponsor, and asked about the perks.

  60. Seve

    Indeed

  61. Guus

    I see no harm in pointing him at the website that lists the perks.

  62. Ge0rG

    related: https://www.pcmag.com/news/367640/how-a-vpn-review-site-dominated-google-search-with-a-scam

  63. Guus

    Thanks Ge0rG - that's a troubling headline.

  64. MattJ

    Based on everything I've seen so far, and the email to the Debian list, it's 99.99% likely to be SEO-related

  65. Guus

    Given that, I suggest that we reject based on the shady history of the company, and that we're reluctant to be associated to that.

  66. Ge0rG

    I suggest to drop and not to reject.

  67. nyco_

    yes, please, let's reject it

  68. Guus

    Ge0rG ?

  69. Ge0rG

    don't reply at all, that reduces the risk of long discussions.

  70. nyco_

    fine

  71. Guus

    He already sent a follow-up question. I'll try to formulate a response - that's the least we can do.

  72. Ge0rG

    people who are good at SEO are also good at sending follow-up requests

  73. Guus

    so, we reject this offer due to the perceived SEO-nature and non-positive history of the company?

  74. nyco_

    on LinuxFr, I usually reject kindly all ads, promoted content, links exchanges, partnerships... explicity, it helps I get a "thank you" almost every time

  75. nyco_

    I'd reject based on non-relatedness to XMPP

  76. Ge0rG

    Any kind of rejection needs to be well argued based on our public policy.

  77. Guus

    I don't want to reject it based on non-XMPP relationship. That's an excuse.

  78. nyco_

    no one in that company has written XMPP software, no one is a member => correct assumption?

  79. Ge0rG

    Writing a proper rejection will be some work.

  80. MattJ

    I know why you would say "don't limit us to XMPP-related things only", but if someone wants to sponsor us who is not related to XMPP or aligned with the XSF's goals, what could their motives be?

  81. nyco_

    no, it's quite easy and fast

  82. Seve

    Apart from SEO... Hmm

  83. MattJ

    SEO is top of that list

  84. Seve

    Good people?

  85. Seve

    ÑD

  86. Guus

    MattJ supporting OSS / Open standards?

  87. Seve

    :D

  88. MattJ

    Guus, that aligns with our goals, obviously

  89. nyco_

    I feel we're wasting too much time on this

  90. Guus

    I tend to agree nyco.

  91. MattJ

    Well, we're not just really discussing this request, but how to deal with requests of this kind (this is not the first and it won't be the last)

  92. Guus

    I'll draft a rejection reply, and share it with board.

  93. nyco_

    +1

  94. Guus

    if there's no consensus via mail, we can pick this up again next week.

  95. MattJ

    Ultimately we could provide Peter with some guidance on how to handle these himself

  96. MattJ

    Instead of every inbound SEO request ending up on Board's agenda

  97. MattJ

    which believe me, doesn't happen in any other sane organisation

  98. Guus

    given that this is our second request in as many years... 🙂

  99. nyco_

    we get two or three such requests per month on LinuxFr.org

  100. nyco_

    it takes 5 min each

  101. MattJ

    Then maybe no general action is needed, let's just ask Peter to kindly reject with a one-liner

  102. Seve

    We would need to check if he said he would forward it to Board

  103. Guus

    I'll send the one-liner.

  104. Guus

    Let's move on

  105. Seve

    Ok, thank you.

  106. Guus

    4) Commitment for the week ahead

  107. Guus

    I'm skipping over the issues with Ralph's face tagged to it, as he's not here

  108. Guus

    which leaves

  109. Guus

    4.1) GSOC '19 evaluation

  110. Guus

    Nyco, I'm seeing your name attached to that

  111. Guus

    Do we want to do anything here?

  112. nyco_

    yes, https://wiki.xmpp.org/web/GSoC_2019 or not... just asked the commTeam

  113. nyco_

    sorry, it went out of my mind

  114. Guus

    No worries, I have a similar mind 🙂

  115. nyco_

    we are closing the newsletter tomorrow, we'll send a PR on GitHub, for a publication on Tue 1st Oct

  116. nyco_

    so either someone write a short piece

  117. Guus

    comms related to this is good, but not something that board is needed for.

  118. nyco_

    or we forget it

  119. nyco_

    agree

  120. Guus

    do we want to evaluate the process itself? Eg: flow organizing things for the first time?

  121. nyco_

    he hasn't got time for this, I asked

  122. Guus

    I think I pinged him on that, but forgot his response, if I got any.

  123. Guus

    Ok - Is there anyone that feels an evaluation is needed?

  124. Guus

    We seem to hav had a successful gsoc?

  125. nyco_

    maybe a summary could do, as a reminder for our newsletter readers

  126. nyco_

    (and contribute to SEO as well...)

  127. Seve

    Ideally I would like someone related to it

  128. Guus

    that's comms again 🙂

  129. Guus

    (and: fine by me)

  130. Guus

    I'm not hearing anyone particularly wanting to go over this.

  131. nyco_

    I'll try, low proba it will end up in the newsletter

  132. Ge0rG

    Aren't there blogs kept by all participants? A summary could link those.

  133. Guus

    Yeah, I intended this to be not about comms

  134. Guus

    but more around the question: do we want to organize things differently next year?

  135. Guus

    I don't see any reason to, and as I'm having trouble getting this discussion off the ground, let's skip it completely and thank Flow and others involved for their effort.

  136. Seve

    That would require input from the people involved in it, I can't tell much, unfortunately.

  137. Guus

    5) Items for discussion

  138. Guus

    5.1) Publicize XSF financials

  139. Guus

    This is in response to a question I received from an XSF Member about the state of the XSF financials.

  140. Guus

    let me quote some stuff

  141. Seve

    Where they done public in the past? I've read that by someone but can't remember who :)

  142. Guus

    > Earlier today, a member had detailed questions on XSF financials (what do we spend money on, how do we obtain money, etc). He asked if/why data was private. > I had to admit that I simply didn't know. I feel that much of this isn't private data, but I don't think we publicly share information either. > There's a least one member that hinted at us being secretive about the financials. I don't think that's necessarily true, but since we've not been publishing any information, I can see how that can be perceived as being secretive. > Someone else mentioned that the XSF has been 'more open' about this in the past. I'm thinking that the lack of information sharing is largely caused by people being less active, and not so much a deliberate attempt at withholding data. What do you think? > I'd hate for people to feel that we're doing things in the dark here. If we did things differently before, can you share on what worked well at that time?

  143. Seve

    Just to know how things went previously, etc

  144. Guus

    that was all me, to Peter

  145. Guus

    Peter responded: > The board has never set a policy on this. If we want to open the books, it is easy enough to do. and > Well, "secretive" is a bit strong. In the far past we posted a kind of spreadsheet on the website, describing various expenses. I'd be happy to do that again, and even reconstruct expenses for all the years between then and now. Naturally it will take me some time to generate that information from file folders in my safe. 🙂

  146. Guus

    (that concludes my quoting of things)

  147. Guus

    I'd not mind taking Peter up on that offer.

  148. Seve

    That helps a lot, really

  149. MattJ

    Is backfilling a requirement?

  150. Guus

    Which in my perspective is basically picking up where we left off.

  151. jonas’

    floor comment: I suggest we don’t put too much load on peter in htis regard and do not ask for expense summaries since back then

  152. MattJ

    I agree, I'd rather not provide Peter with more work if we can help it

  153. nyco_

    agree, it's a question of RoI

  154. Guus

    I disagree. If we do make things public, it shouldn't have gaps.

  155. nyco_

    ROTI, return on time invested

  156. jonas’

    unless a majority of members wants that information, of course

  157. pep.

    MattJ: is as one of the people to ask about this, I don't mind if it's just from now on.

  158. Guus

    also, I'm guessing that the work involved is light, as he already should have administation

  159. MattJ

    Guus, we make things public from today, I don't see the problem

  160. MattJ

    He said himself it will "take some time"

  161. Guus

    Sure, doesn't need to happen overnight

  162. nyco_

    can we easily track the board's decisions regarding spending?

  163. Guus

    but I think it's sensible to have a complete record.

  164. MattJ

    I feel it's unfair to ask him to put in that time just to satisfy the curiosity of a couple of folks, when just general overview of current+future would be fine

  165. Guus

    also, he offered without being asked to.

  166. MattJ

    We're over time again and I need to prep for my next meeting

  167. Guus

    I'm not seeing this as satisfying curiosity, but as a way to be transparant as an organisastion.

  168. Guus

    Ok, can we conclude this before you go?

  169. MattJ

    I've no objection to transparency

  170. nyco_

    yep, we are fully transparent with the board, holding meetings in public...

  171. MattJ

    But I don't see that historical records are a hard requirement

  172. MattJ

    I see them as a nice thing to have, but I think publishing our current financial state and maintaining that going forwards is plenty of improvement already

  173. Kev

    What practical purpose would historical records have, compared to current?

  174. nyco_

    trust?

  175. jonas’

    middle-ground: add a note (to whereever this is going to be published) that historical records are not available in digital form, but can be requested by any member at any time

  176. Kev

    How is a lack of trust current presenting itself?

  177. Kev

    How is a lack of trust currently presenting itself?

  178. nyco_

    not sure, people asking on written form?

  179. Guus

    In the interest of time, let's move this to next week

  180. MattJ

    Kev, well, arguably I could have been colluding with Peter to siphon XSF funds into the Prosody project, hence my argument to keep the records closed :)

  181. nyco_

    (guessing...)

  182. Guus

    Matt needs to go.

  183. Guus

    6) AOB (that are pressing?)

  184. nyco_

    nope

  185. MattJ

    I obviously haven't, but there is merit to having open historical records

  186. Guus

    7) Date/Time of next +1w?

  187. MattJ

    wfm

  188. nyco_

    +1

  189. Guus

    do we have DST changes upon us?

  190. Guus

    (it's that time of year)

  191. Guus

    we're all on the same switchover date, I think?

  192. Seve

    Yes, we are.

  193. MattJ

    in a few weeks at least

  194. nyco_

    nope

  195. nyco_

    ah ok, not this weekend

  196. Guus

    Ok, we'll continue to use London time then, which should avoid us being affected at all

  197. Guus bangs gavel

  198. Guus

    thanks!

  199. nyco_

    26-27th Oct

  200. Seve

    Thank you :)

  201. nyco_

    thx all!

  202. MattJ

    Thanks!

  203. MattJ

    I'll have to finish the minutes after my meetings today

  204. Guus

    Kev - I think the purpose of opening the books is to prevent a lack of trust manifesting itself.

  205. Guus

    not the other way around

  206. Kev

    Yes, and opening the books from now seems quite pragmatic and sensible. I'm not sure it's worth the effort of going back and reconstructing reports, given Peter's time is presumably not easy to come by.

  207. Kev

    But YMMV.

  208. Guus

    I appreciate that, but a) he offered, and b) it kind of comes with the role of being a Treasurer.

  209. Guus

    it's not that I suggest we pressure him into doing things

  210. Guus

    but as he offered, and I think it'd be good to have a full set of records, I'm inclined to take him up on that offer.

  211. Guus

    also, I'm happy for this to not be ready tomorrow.

  212. Seve

    I don't see any specific urgency on this, either. But I also do not expect members to request trust from Boards long time ago.

  213. Guus

    I'm envisioning this as nothing more than a simple table, right - not extensive details

  214. Seve

    I guessed so.

  215. nyco_

    anything you publish, you might have questions around it

  216. nyco_

    if not objections

  217. Guus

    then we decide to not publish anything

  218. nyco_

    hehehe

  219. Guus

    (which I think is a bad idea)

  220. nyco_

    hide and stop doing things

  221. jonas’

    Guus, there appears to be a full set of records, it’s just not public

  222. jonas’

    thus my middle-ground suggestion above

  223. Guus

    jonas’ which I didn't dislike.

  224. MattJ

    same

  225. metaentropy

    /quit