XSF Discussion - 2019-04-25


  1. pep.

    https://xmpp.org/2019/01/google-summer-of-code-2019/ is that pelican failing to parse the Project_Ideas url? Do we have to tell it for every single one?

  2. pep.

    Is there an equivalent markdown for `<https://foo.bar>`_ (note, I don't know if that's valid rst either, without a link description)

  3. jonas’

    pep., [url](description)?

  4. jonas’

    or just [url](url)?

  5. pep.

    right, I did the latter, but that seemed a bit repetitive

  6. Zash

    pep.: <url> maybe?

  7. flow

    http://www.astroscu.unam.mx/rmaa/RMxAC..51/PDF/RMxAC..51_articulo06.pdf

  8. Zash

    flow: Cool

  9. flow

    It appears to be open access, so maybe the XSF could blog about it

  10. flow

    Added to https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter#Other - I hope that was right

  11. wurstsalat

    this is nice to read!

  12. edhelas

    yup !

  13. jonas’

    pep., https://github.com/xsf/xmpp.org/pull/560/files#r278525237

  14. Guus

    flow would be a nice addition to https://xmpp.org/uses/

  15. vanitasvitae

    Yay, we got 4 slots for GSoC :)

  16. vanitasvitae

    Ah no wait, nvm

  17. pep.

    jonas’: sure, I was just fixing the link :p

  18. jonas’

    pep., it solves your link markup dilemma :)

  19. pep.

    I'd say that'S a workaround rather than a fix

  20. pep.

    But that looks better yes

  21. jonas’

    it’s a fix, because it also fixes the a11y issues of raw URLs

  22. pep.

    not a fix for my issue

  23. Guus

    vanitasvitae yes we did.

  24. ralphm waves

  25. nyco waits

  26. ralphm bangs gavel

  27. ralphm

    0. Welcome + Agenda

  28. ralphm

    Hi!

  29. ralphm

    Who do we have today?

  30. Guus

    I can't join in today, as announced

  31. MattJ

    o/

  32. ralphm

    Guus: no worries

  33. Guus

    will try to read along

  34. ralphm

    Seve?

  35. ralphm

    1. Minute taker

  36. ralphm

    Who?

  37. ralphm

    (Assuming that nyco is actually here)

  38. nyco

    (I am)

  39. MattJ

    No minute taker, I assume

  40. ralphm

    Guess no meeting then.

  41. ralphm

    This is getting ridiculous.

  42. nyco

    because no one wants to take notes? we can still have a meeting, can't we?

  43. ralphm

    No

  44. ralphm

    Having meetings without minutes is not acceptable to me, to be honest.

  45. MattJ

    It's not acceptable according to the org bylaws

  46. ralphm

    And that, I didn't even check.

  47. nyco

    then we're quite regularly out of bounds

  48. nyco

    we failed many times to deliver those minutes

  49. ralphm

    Yes, and I am a bit fed up with it.

  50. nyco

    so am I

  51. ralphm

    So, either one of us takes notes, or we find a sustainable other solution.

  52. nyco

    I still believe we should use a real-time collaborative text editor just proposing a solution to the lack of volunteers

  53. nyco

    ok, let me take the notes today

  54. ralphm

    nyco: it is not ideal to have people taking part in the discussion also having to take notes.

  55. nyco

    go on

  56. nyco

    please

  57. ralphm

    Ok, thank you.

  58. nyco

    it is less ideal to have no notes

  59. ralphm

    2. Infrastructure Team lead

  60. ralphm

    I have not seen anyone step up for this?

  61. nyco

    neither have I

  62. nyco

    I offer a "Pain au Chocolat" to anyone who will take the lead!

  63. ralphm

    :-D

  64. nyco

    (that's extrinsic motivation, but hey)

  65. MattJ

    I'll take it

  66. Kev

    More than I ever got for it :p

  67. ralphm

    MattJ: the pain or the pain?

  68. MattJ

    Oh dear

  69. nyco

    ok, one for Kev as well => send me privately your mail address

  70. nyco

    > MattJ: the pain or the pain? indeed, needs clarification and precision

  71. MattJ

    I'll take the pain

  72. MattJ

    But seriously, if nobody else steps up, I'm willing to take it on

  73. ralphm

    I am taking a leap here knowing Kev and Intosi won't object to MattJ as lead, so I motion we appoint MattJ as lead of iteam.

  74. ralphm

    +1

  75. nyco

    +1

  76. nyco

    one _pain_ for MattJ 😉

  77. Seve

    +1

  78. MattJ

    Just one. And a chocolate pastry. Sounds like deal :)

  79. ralphm

    MattJ: you may vote

  80. Seve

    I can take notes after the meeting, not while we are at it

  81. MattJ

    Well, since I proposed it... +1?

  82. nyco

    thanks a lot to both Kev and MattJ, congrats MattJ! 😉

  83. ralphm

    Good. The ayes have it.

  84. ralphm

    3. Deferred XEP typos

  85. nyco

    (Kev got your golden parachute?)

  86. nyco

    (@Kev: got your golden parachute?)

  87. ralphm

    I seem to remember there was recent discussion on this in Council?

  88. ralphm

    jonas’: ?

  89. Kev

    Fine with MattJ as lead for the record.

  90. ralphm

    Kev: thanks. Wasn't there recent discussion in Council on XEP version numbers that touches on this?

  91. Kev

    On a call at the moment, sorry.

  92. Guus

    https://github.com/xsf/xeps/pull/780

  93. Guus

    that?

  94. ralphm

    Ah yes.

  95. Guus

    happy for Matt to have accepted chocolate-induced-pain.

  96. ralphm

    I think that PR should have review by Council, first.

  97. ralphm

    I.e. I wouldn't like to make changes to XEP-0001 with them forming an opinion on it.

  98. ralphm

    without

  99. ralphm

    I've added the _Needs Council_ label to make sure, and let the minutes reflect that we'd like their input.

  100. ralphm

    4. Server setup

  101. Guus

    board can form an opinion without Council

  102. Guus

    no need to wait expressing the opinion - we can hold off voting on it though.

  103. ralphm

    Guus: yes we can, but I like their opinion when it changes the process.

  104. ralphm

    I had a brief discussion with Edwin on the server setup.

  105. ralphm

    iteam members have been a bit swamped with other stuff to pick this up.

  106. ralphm

    In any case, they would like to balance the existing offer to continue hosting parts of our infrastructure where it is now, while also looking into having stuff in some cloud offering

  107. ralphm

    (most likely AWS)

  108. ralphm

    Examples include DNS resolution and hosting our website.

  109. MattJ

    I'd be quite happy with the XSF officially adopting $some_cloud_provider for (at least some) infrastructure

  110. ralphm

    There's no actionable plan, yet, but I have expressed that Board would be ok with paying for hosting some of our infra at AWS. I also think it makes sense to retain existing hosting, but there might be some required hardware upgrades, too.

  111. ralphm

    So MattJ, let's have that discussion with iteam, I'd be happy to sit in and help out.

  112. MattJ

    Great

  113. jonas’

    it would be nice to have the mission critical stuff in some stable environment (maybe we can push to aws from travis directly and save the docker roundtrip for the website and xeps, too?) and allow more experimental stuff on the main machine

  114. ralphm

    jonas’: noted. Moving this discussion to iteam.

  115. ralphm

    5. Tigase / XMPP Logo

  116. ralphm

    I haven't asked stpeter yet. Will contact him this week.

  117. ralphm

    6. AOB

  118. nyco

    not for me

  119. ralphm

    7. Date of Next

  120. ralphm

    +1W

  121. ralphm

    8. Close

  122. ralphm

    Thanks All!

  123. ralphm bangs gavel

  124. nyco

    -1, I'll try to join from my holidays in Italy

  125. MattJ

    Thanks ralphm/all

  126. nyco

    thx

  127. nyco

    > Thanks ralphm/all ralphm divided by all?

  128. ralphm

    Oh, I think I'm on a plane next week.

  129. nyco

    still have wifi? 😉

  130. ralphm

    nyco: such is the fate of a chair person

  131. ralphm

    nyco: crossatlantic, so no

  132. ralphm

    Since I'm flying at 11:00 CEST to JFK, I'm sure I'd be somewhere just passed Iceland or so

  133. Seve

    Thank you for the meeting guys

  134. nyco

    minutes sent, please read and correct me if I got something wrong or forgot anything

  135. MattJ

    Thanks nyco :)

  136. Guus

    Congratulations MattJ

  137. Guus

    enjoy the pain.

  138. MattJ

    Thanks :)

  139. jonas’

    MattJ, congrats!

  140. Ge0rG

    MattJ: congratulations! Now please let me bother you in your new role with https://github.com/xsf/mediawiki-docker/issues/2

  141. MattJ

    uh-oh

  142. Zash

    So it begins

  143. Ge0rG

    It's merely half a year that I'm asking for that feature

  144. Neustradamus

    Congrats to MattJ for iteam! After your good job with XMPP.net it is normal!

  145. Neustradamus

    Can not wait the update of this part: https://xmpp.org/about/xsf/infrastructure-team

  146. Ge0rG

    Neustradamus: make a PR?

  147. Neustradamus

    Time to move the https://github.com/stpeter/jabberdotorg to org? Ticket: https://github.com/stpeter/jabberdotorg/issues/9 And have an update of this page too: https://www.jabber.org/team.html

  148. Neustradamus

    Ge0rG: Only the leader knows what people are in team ^^ cleaning time :)

  149. Neustradamus

    Linked to https://github.com/xsf/xmpp.org/issues/483

  150. Ge0rG

    we need a LIDAR!