XSF Communications Team - 2019-03-01


  1. jc has left

  2. jc has joined

  3. vaulor has joined

  4. LNJ has joined

  5. alacer has joined

  6. LNJ has left

  7. Guus

    Thanks for a new newsletter guys!

  8. Guus

    For future reference: please stylize Openfire like that, instead of OpenFire.

  9. Neustradamus

    Ah ah

  10. Neustradamus

    Any news for the old new https://xmpp.org/2019/01/the-xmpp-newsletter-31-january-2019 ?

  11. Neustradamus

    A lot of people are lost with it

  12. Neustradamus

    Dead link

  13. Neustradamus

    Already one month.

  14. jc

    huh? Where is that link?

  15. jc

    Guus: 👍

  16. jc

    Neustradamus Where is that link being used?

  17. jc

    We can only fix the URL if we have a rewrite for the old URL

  18. jc

    Which means configuring the webserver

  19. jc

    Not something I can do

  20. LNJ has joined

  21. vaulor has left

  22. vaulor has joined

  23. Neustradamus

    jc: in planet for example

  24. Neustradamus

    We had several talks about this problem but no change

  25. Neustradamus

    I have created a ticket of course for history like all opened tickets

  26. Neustradamus

    XMPP.org tickets: https://github.com/xsf/xmpp.org/issues Jabber.org tickets: https://github.com/stpeter/jabberdotorg/issues

  27. Neustradamus

    Manifesto tickets: https://github.com/stpeter/manifesto/issues

  28. Neustradamus

    Link Mauve and pep.: With your good memory, can you talk again about the bad newsletter link?

  29. vaulor has left

  30. LNJ has left

  31. jc

    That's weird, why does the planet have the "wrong" link?

  32. LNJ has joined

  33. Neustradamus

    I have waited the change for social network... But I have done with the bad date... Because no change.

  34. Neustradamus

    Always complicated with XSF team... Since several years for have a solution to problems.

  35. jc

    Guus: do you have access to the webserver configs for xmpp.org?

  36. SouL

    I checked the issue Neustradamus but I think that is for iteam instead?

  37. SouL

    Because I don't have access to any of that

  38. Neustradamus

    Iteam has a lot of work since several years badly.

  39. SouL

    So maybe we need more hands on the team

  40. Neustradamus

    XSF iteam and Jabber.org iteam (do not mix)

  41. Neustradamus

    Do not forgot the XSF server crash...

  42. pep.

    Neustradamus, in the meantime they're the only ones with server access

  43. Neustradamus

    Debian 10 will be release soon, I hope change for TLS problems...

  44. Neustradamus

    An update of the old manifesto for be more secured... Without SSLv3...

  45. Neustradamus

    An update of the old M-Link version for jabber.org...

  46. SouL

    Does the XSF manage jabber.org? Because is not the same XSF managing that server and people that happen to be in the XSF to manage that server

  47. Neustradamus

    "XSF iteam and Jabber.org iteam (do not mix)" -> https://www.jabber.org/team.html -> https://xmpp.org/about/xsf/infrastructure-team

  48. Neustradamus

    Please look here the ticket like a lot of other -> https://github.com/xsf/xmpp.org/issues/483

  49. alacer has left

  50. pep.

    Neustradamus, I guess you want to say all this in iteam@muc.xmpp.org, not here

  51. Neustradamus

    I have not access :)

  52. SouL

    You cannot join that MUC?

  53. Neustradamus

    Yes

  54. Neustradamus

    Not new ;)

  55. pep.

    banned?

  56. pep.

    Because it's the same MUC service

  57. SouL

    What did you do naughty Neustradamus?

  58. SouL

    :D

  59. pep.

    So I don't see many other problems

  60. Neustradamus

    About Jabber.org, there is a ticket to change to organization on github... https://github.com/stpeter/jabberdotorg/issues

  61. Neustradamus

    Please look this closed ticket: https://github.com/stpeter/jabberdotorg/issues/1

  62. pep.

    Can you stop waving unrelated tickets in front of us please

  63. Neustradamus

    There are tickets about XSF and Jabber.org (some guys are same)

  64. pep.

    Good, now what

  65. pep.

    They'r enot here

  66. pep.

    They're not here

  67. Neustradamus

    It is commteam no?

  68. Neustradamus

    There are communication problems since a long time... Need to be resolved

  69. pep.

    whatever.. I have more important things to do

  70. Neustradamus

    There are communication problems since a long time... Need to be solved

  71. SouL

    Neustradamus, I appreciate a lot your effort, if you have a list of issues please make that list and then I will check. But right now I just don't understand you :)

  72. Neustradamus

    Look tickets on github

  73. Neustradamus

    Easy

  74. Neustradamus

    All have visibility on it

  75. Neustradamus

    Not only my tickets of course: - https://github.com/xsf/xmpp.org/issues - https://github.com/stpeter/jabberdotorg/issues (do not forgot closed tickets) - https://github.com/stpeter/manifesto/issues

  76. Neustradamus

    And I can thank again MattJ and Guus about XMPP.net for work done.

  77. SouL

    Neustradamus, ok I will take a look at them, but I would love to have some specific topics to look into, because I just can't check all the issues. I need something you want to fix.

  78. alacer has joined

  79. Neustradamus

    Easy to look tickets, thanks in advance SouL

  80. Neustradamus

    Maybe 2019 will be the best year for all.

  81. alacer has left

  82. alacer has joined

  83. alacer has left

  84. alacer has joined

  85. Neustradamus

    jc: https://github.com/xsf/xmpp.org/issues/532#issuecomment-468615155

  86. jc

    I'm going on holiday to South Africa tonight and will be away for the next weeks, so someone else will have to do it

  87. Neustradamus

    Happy holiday jc!

  88. jc

    thanks 🙂

  89. alacer has left

  90. alacer has joined

  91. alacer has left

  92. alacer has joined

  93. LNJ has left

  94. LNJ has joined

  95. LNJ has left

  96. LNJ has joined

  97. alacer has left

  98. alacer has joined

  99. alacer has left

  100. alacer has joined

  101. alacer has left

  102. alacer has joined

  103. Guus has left

  104. Guus has joined

  105. alacer has left

  106. alacer has joined

  107. pep.

    https://github.com/xsf/xmpp.org/pull/539

  108. alacer has left

  109. SouL

    Oh I didn't even spot that one 😿 Thank you pep.

  110. SouL

    Going to merge in 2 minutes

  111. alacer has joined

  112. jc has left

  113. jc has joined

  114. arnaudj has left

  115. arnaudj has joined

  116. jc has left

  117. jc has joined

  118. arnaudj has left

  119. arnaudj has joined

  120. jc has left

  121. jc has joined

  122. Neustradamus has left

  123. arnaudj has left

  124. jc has left

  125. jc has joined

  126. arnaudj has joined

  127. alacer has left

  128. alacer has joined

  129. jc has left

  130. jc has joined

  131. alacer has left

  132. jc has left