XSF Communications Team - 2019-11-14


  1. debacle has left

  2. DebXWoody has left

  3. DebXWoody has joined

  4. DebXWoody has left

  5. DebXWoody has joined

  6. DebXWoody has left

  7. DebXWoody has joined

  8. vanitasvitae has left

  9. DebXWoody has left

  10. vanitasvitae has joined

  11. DebXWoody has joined

  12. Guus

    There is no such plan that I am aware of. You seem to be the only one that is interested in that.

  13. DebXWoody has left

  14. DebXWoody has joined

  15. LNJ has joined

  16. jcbrand has joined

  17. LNJ has left

  18. emus has joined

  19. Nÿco

    I feel there is no need to rename Jabber planet to XMPP planet the two belong to the same era :) that said, maybe we can do some SEO

  20. winfried has left

  21. winfried has joined

  22. winfried has left

  23. winfried has joined

  24. winfried has left

  25. winfried has joined

  26. Nÿco

    fyi, as an experiment: https://www.linkedin.com/feed/update/urn:li:activity:6600654130799304704

  27. Nÿco

    proposed tweet for today: " The November XMPP/Jabber newsletter is available in French! https://linuxfr.org/news/lettre-d-information-xmpp-01-octobre-2019-fosdem-2020-modernisation-de-xmpp-reseaux-de-pairs #OpenStandards #OpenSource #InstantMessaging #Chat " if no opposition, I'll post it

  28. emus has left

  29. emus has joined

  30. winfried has left

  31. winfried has joined

  32. emus has left

  33. emus has joined

  34. jasonervin has joined

  35. DebXWoody

    The link is the october news not november.

  36. DebXWoody

    Is https://fosstodon.org/@xmpp managed by somebody here?

  37. SouL

    No one that I'm aware of

  38. pep.

    I don't think so?

  39. SouL

    I was on the hunt for a server where we could create a mastodon account, but I'm not decided yet

  40. SouL

    Setting up one can be a bit overkill for us, right now

  41. pep.

    SouL: we need mod_ap

  42. pep.

    And publish to microblog :p

  43. pep.

    This way we can use xmpp.org

  44. SouL

    That would indeed be really cool, also for us to show how cool XMPP is

  45. Nÿco

    > Is https://fosstodon.org/@xmpp managed by somebody here? I am experimenting it...

  46. Nÿco

    setting up a Mastodon server on our infra would be cool indeed, would show our implication and consistency however fosstodon is where Free/Libre/OpenSource Community is, so it seemed to me a good place to try it out

  47. DebXWoody

    Nÿco, Sehr cool!!!!

  48. Nÿco

    I've just set it up so far, please tell what you think

  49. SouL

    Nÿco, ah is it you? perfect then, thank you

  50. DebXWoody

    Nÿco, just post official information (Newsletter, maybe also information about state changes of XEPs,..) always use at least #XMPP #XFS. I think that is great.

  51. Nÿco

    XFS, eXtended File System? :)

  52. Nÿco

    ok

  53. DebXWoody

    🤪

  54. jasonervin has left

  55. jasonervin has joined

  56. Nÿco

    I confess I had never used Mastodon before... so far, after an hour of playing around, I... f***ing LOVE the federation concept... oh wait, what? :)

  57. pep.

    Tbh I spent like a month or two struggling to understand how to use it..

  58. pep.

    I would subscribe to people but I didn't even display the timeline for that :p

  59. pep.

    Also the columns are awkward to me. Scrolling horizontally is awkward

  60. Nÿco

    it is more or less like Tweetdeck as far as I can see

  61. pep.

    I don't use it

  62. pep.

    I don't use twitter..

  63. Nÿco

    some mobile clients exist, more or less like the basic mobile Twitter experience

  64. winfried has left

  65. winfried has joined

  66. Nÿco

    problem: on https://wiki.xmpp.org/web/CommTeam there is: " Update the text here xmpp.org/participate/become-a-member/the-xsf-communication-team " but that page does not exist

  67. winfried has left

  68. winfried has joined

  69. pep.

    It would be good to have a page for that indeed

  70. pep.

    Not just commteam but any team. That can be on the same page I'd say. Alongside "how to become an xsf member"

  71. pep.

    And then on each team we can redirect there

  72. LNJ has joined

  73. Nÿco

    yeah, let's ask the webteam to do it! :)

  74. Nÿco

    nah, seriously, we can draft something... on the wiki or the website git repo

  75. Nÿco

    I made a thing: https://wiki.xmpp.org/web/Social_Media

  76. Nÿco

    and reminder: https://wiki.xmpp.org/web/Personas

  77. Nÿco

    Twitter metrics: (sorry, I have not been disciplined, I am a procrastinator)

  78. Nÿco

    https://upload.movim.eu/files/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/fc3r2EYVmtrBm5JgMn9At1geXiDvEugP8A9Tmp4q/Capture_d_e_cran_2019-11-14_a__11.49.10.png

  79. Nÿco

    https://upload.movim.eu/files/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/IUvWucnDwroAZv9m1e7q3SBqwKzmdUvVjQzDEMx0/Capture_d_e_cran_2019-11-14_a__11.49.21.png

  80. Nÿco

    for LinkedIn:

  81. Nÿco

    https://upload.movim.eu/files/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/qNtHWJd0VU1sRTln7x4LlZNVLGoMMJdy7f7n9hX1/Capture_d_e_cran_2019-11-14_a__11.52.17.png

  82. Nÿco

    Page (not Group)

  83. debacle has joined

  84. winfried has left

  85. winfried has joined

  86. Nÿco

    proposed tweet for today (modified): " À tous les francophones, la lettre d'informations XMPP est disponible en français ! The November XMPP/Jabber newsletter is available in French! https://linuxfr.org/news/lettre-d-information-xmpp-01-octobre-2019-fosdem-2020-modernisation-de-xmpp-reseaux-de-pairs #OpenStandards #OpenSource #InstantMessaging #Chat " if no opposition, I'll post it in an hour or so

  87. Nÿco

    with this picture:

  88. Nÿco

    https://upload.movim.eu/files/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/ZIatL5YQAX1LPaFi5fFikqRmt3w0DpQ1Pyh7tVAp/XMPP_newsletter.png.jpg

  89. ldkjgoiwe has joined

  90. ldkjgoiwe has left

  91. Wojtek has joined

  92. Nÿco

    https://twitter.com/xmpp/status/1194969787912331265

  93. Link Mauve

    Nÿco, don’t reencode PNG logos as JPEG.

  94. Link Mauve

    This makes them look ugly.

  95. Nÿco

    wat

  96. pep.

    Movim reencodes pngs to jpeg

  97. Nÿco

    I did not do that why do you say so?

  98. pep.

    Yes "you" did

  99. pep.

    Not you

  100. pep.

    Your client did

  101. SouL

    Why is that? Do you know?

  102. pep.

    Unsure

  103. winfried has left

  104. winfried has joined

  105. winfried has left

  106. winfried has joined

  107. raspbeguy has left

  108. raspbeguy has joined

  109. winfried has left

  110. winfried has joined

  111. winfried has left

  112. winfried has joined

  113. Martin

    Might suchat.org be a good place for publishing the Spanish translations?

  114. Nÿco

    I can't judge...

  115. Neustradamus

    Any news for the bad link of the newsletter from 2019? - https://xmpp.org/2019/01/the-xmpp-newsletter-31-january-2018/

  116. Nÿco

    are you referring to something you "requested" ages ago somewhere?

  117. Neustradamus

    It is one of old remarks yes.

  118. Nÿco

    so what link? can you please submit a PR?

  119. Neustradamus

    A lot of tickets here: https://github.com/xsf/xmpp.org/issues

  120. Neustradamus

    Some were previously on tracker.xmpp.org ;)

  121. Nÿco

    which one? a PR would help

  122. Neustradamus

    https://github.com/xsf/xmpp.org/issues/532

  123. Nÿco

    it's closed

  124. Neustradamus

    Not by me.

  125. Neustradamus

    https://xmpp.org/about/xsf/comm-team.html The team is not complete, some names are missing too ;)

  126. Neustradamus

    Like https://wiki.xmpp.org/web/CommTeam

  127. Neustradamus

    In the same time, can you update the logo of the newsletter/website/wiki/icon/twitter/mastodon/...? The logo is not good. The last perfect version is here: https://commons.wikimedia.org/wiki/File:XMPP_logo.svg

  128. Neustradamus

    -> https://github.com/xsf/xmpp.org/issues/608

  129. Nÿco

    what's wrong with the logo?

  130. Neustradamus

    Open your eyes

  131. Neustradamus

    Missing redirections: https://github.com/xsf/xmpp.org/issues/421

  132. Neustradamus

    The return of XEP Diff Tool: https://github.com/xsf/xmpp.org/issues/412

  133. Neustradamus

    XMPP Protocol Namespaces not complete: https://github.com/xsf/xmpp.org/issues/413

  134. Nÿco

    ok, you lost me now

  135. Neustradamus

    RFCs are missing and maybe not updated for actual: https://github.com/xsf/xmpp.org/issues/414

  136. Nÿco

    I understand you are benevolently reviewing lots of things

  137. Neustradamus

    Website missing redirections: https://github.com/xsf/xmpp.org/issues/419

  138. Neustradamus

    Registrar section is not updated: https://github.com/xsf/xmpp.org/issues/422

  139. Neustradamus

    Schemas section is not updated: https://github.com/xsf/xmpp.org/issues/423

  140. Neustradamus

    If no people look tickets, it is not good ;)

  141. Neustradamus

    Year after year

  142. Neustradamus

    Update history: https://github.com/xsf/xmpp.org/issues/635

  143. Link Mauve

    Neustradamus, what about contributing rather than reporting issues?

  144. Link Mauve

    You can see we’re all overworked already, you could help alleviate some of it.

  145. Neustradamus

    My tickets are very old, look when it was done.

  146. Link Mauve

    Yet you didn’t at any point step forward to fix them.

  147. Neustradamus

    Nÿco: For logos, you can look here: http://logs.xmpp.org/xsf/2019-11-12

  148. Nÿco

    PRs are better than issues generally also fresh is better than

  149. Nÿco

    old

  150. Nÿco

    and here, we are only the commTeam

  151. Neustradamus

    Yes and you have forgotten my name in the CommTeam ;)

  152. Nÿco

    I have forgotten nothing related to this, as I am not supposed to maintain and know everything has your candidacy been approved by the Board? please point to the decision

  153. raspbeguy has left

  154. raspbeguy has joined

  155. Nÿco

    > Update history: https://github.com/xsf/xmpp.org/issues/635 that was easy: https://github.com/xsf/xmpp.org/pull/636 can anyone review and merge?

  156. debacle has left

  157. jasonervin has left

  158. winfried has left

  159. winfried has joined

  160. debacle has joined

  161. raspbeguy has left

  162. raspbeguy has joined

  163. Wojtek has left

  164. debacle has left

  165. Wojtek has joined

  166. winfried has left

  167. winfried has joined

  168. jasonervin has joined

  169. jcbrand has left

  170. winfried has left

  171. winfried has joined

  172. jcbrand has joined

  173. emus has left

  174. emus has joined

  175. arnaudj has left

  176. arnaudj has joined

  177. emus has left

  178. emus has joined

  179. winfried has left

  180. winfried has joined

  181. winfried has left

  182. winfried has joined

  183. pep.

    Neustradamus: I can only reiterate what Link Mauve just said.

  184. pep.

    If it's an issue with git some other technical stuff I'm happy to take the time and teach you

  185. vanitasvitae has left

  186. vanitasvitae has joined

  187. Wojtek has left

  188. debacle has joined

  189. winfried has left

  190. winfried has joined

  191. winfried has left

  192. winfried has joined

  193. winfried has left

  194. winfried has joined

  195. winfried has left

  196. winfried has joined

  197. LNJ has left

  198. jcbrand has left

  199. emus has left

  200. emus has joined

  201. emus has left

  202. jasonervin has left

  203. jasonervin has joined

  204. jcbrand has joined

  205. jcbrand has left