XSF Communications Team - 2019-09-30


  1. arnaudj has left

  2. arnaudj has joined

  3. LNJ has joined

  4. jcbrand has joined

  5. debacle has joined

  6. nyco has joined

  7. Guus has left

  8. Guus has joined

  9. Guus has left

  10. Guus has joined

  11. debacle has left

  12. nyco

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

  13. nyco

    lots of reviews, thx very much!

  14. nyco

    one last check before tomorrow merge-and-deploy? :)

  15. nyco

    https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/oTNiv2ht80AsWxAQ5CUT89RmcCYPQXiSBO9UPjlm/Capture_d_e_cran_2019-09-30_a__12.07.16.png

  16. nyco

    how about such a tweet today? "The XSF commTeam is finalising the next newsletter to be published this Tuesday 1st of October, covering the month of September: https://xmpp.org/newsletter.html"

  17. nyco

    +16 subscribers to the newsletter this month, that 6+% growth

  18. nyco

    https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/IQZXcOT1VzZEPBlV4Qc5xi6lrJSq4fVXCuC2fhpc/Capture_d_e_cran_2019-09-30_a__12.19.35.png

  19. nyco

    this month is our worst click rate so far

  20. nyco

    I explain this by the new specifications section

  21. nyco

    we continue the experiment, and we'll survey at the end of year

  22. debacle has joined

  23. nyco

    > how about such a tweet today? "The XSF commTeam is finalising the next newsletter to be published this Tuesday 1st of October, covering the month of September: https://xmpp.org/newsletter.html"

  24. SouL

    Tomorrow we are tweeting about it again, right?

  25. arnaudj

    Good ! I would add a “call to action” verb before the link, maybe “subscribe”

  26. SouL

    I would say maybe subscribe before it is published or something

  27. SouL

    arnaudj, you are too fast!

  28. SouL

    :D

  29. arnaudj

    SouL: Sometimes, not often! 😃

  30. nyco

    " The XSF commTeam is finalising the next newsletter to be published this Tuesday 1st of October, covering the month of September Subscribe before we send it: https://xmpp.org/newsletter.html "

  31. SouL

    " Subscribe before we send it! https://xmpp.org/newsletter.html "

  32. SouL

    just to sound more exciting :D

  33. SouL

    let's gooo

  34. arnaudj

    Go go go!

  35. arnaudj

    Thank you nyco

  36. nyco

    ok

  37. nyco

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

  38. nyco

    please retweet

  39. nyco

    so now, what tweet do we send tomorrow?

  40. nyco

    that's Tuesday what about Wednesday and Thursday?

  41. SouL

    It could start like "As promised yesterday [...]"

  42. nyco

    " The XMPP newsletter is out! [link] Read it while it is fresh Please subscribe to receive the next one in your inbox Share and Like this tweet! "

  43. nyco

    I would avoid using relative times on social media, as a post can last a few days I usually go for absolute dates

  44. SouL

    I have to agree with you, you are right, yes

  45. SouL

    Your tweet sounds good to me!

  46. nyco

    https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/KFXu7SaKBDTSWME5rWXWyL8IoJngFMIsyeT2RwWk/Capture_d_e_cran_2019-09-30_a__14.35.19.png

  47. Martin has joined

  48. Martin

    So it is out already?

  49. nyco

    wat

  50. nyco

    the tweet, yes

  51. nyco

    please check the link

  52. nyco

    > https://twitter.com/xmpp/status/1178646822803386369

  53. nyco

    and please Like/Retweet, if you want

  54. nyco

    for the newsletter, that's tomorrow: https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter#Planning

  55. Martin

    The newsletter. As I still don't understand how I can attach my commits to your PR. I'm no dev so github sometimes is irritating me. I just used the edit in your branch and githab made PRS out of it...

  56. Martin

    😡

  57. SouL

    I would not add any changes, Martin. Just add a comment and the person working on that PR can make the changes after

  58. nyco

    I'm no dev either

  59. nyco

    for this month, opening up the newsletter-making to other people has been a huge pain

  60. nyco

    > some people feed me one thing back, some tell other things, even opposite sometimes

  61. nyco

    > the process remains open, progresses each week/month, there is still much room for improvement

  62. nyco

    > > I juggle with Mediawiki markup, then Markdown for Pelican on our blog, then Tinyletter's WYSIWYG > please ease my job, do no complexify it, it is already super hard

  63. Martin

    nyco: sorry, I didn't want to make it difficult for you, I just wanted to improve it.

  64. nyco

    I know the intention, thx very much

  65. nyco

    I still have a work in parallel, that has been a time block hole this month

  66. nyco

    *black hole

  67. nyco

    so, I observe many more people wanna contribute, that is excellent, thx very much to all

  68. nyco

    but today, our tools don't scale

  69. nyco

    the reference has always been https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter will remain there for... I don't know how long

  70. nyco

    this wiki page is cool to host the checklist, planning, etc.

  71. nyco

    but it's not Markdown

  72. Martin

    Anyway I don't have time to dig in to github thingies today. So maybe someone who has time and knowhow can put the stuff from my PR tlin the right form. I will check out this review thing this month and do it properly next time.

  73. nyco

    on GitHub, I did not see a Markdown validation/test thing

  74. nyco

    yes, time and tools, I agree

  75. nyco

    we can definitely do BaC :) (Blog as Code)

  76. nyco

    but I wouldn't do a month-long PR

  77. nyco

    that's during the link collection/aggregation

  78. jcbrand has left

  79. MattJ has joined

  80. MattJ

    nyco, I just submitted a couple of suggestions

  81. nyco

    thx!

  82. MattJ

    One was selfish, we just made a Prosody release ;)

  83. nyco

    cool

  84. nyco

    changes ported @Martin

  85. Martin

    nyco: thanks a lot

  86. winfried has left

  87. winfried has joined

  88. winfried has left

  89. winfried has joined

  90. jcbrand has joined

  91. winfried has left

  92. winfried has joined

  93. LNJ has left

  94. LNJ has joined

  95. debacle has left

  96. Martin has left

  97. Martin has joined

  98. debacle has joined

  99. arnaudj has left

  100. arnaudj has joined

  101. Martin has left

  102. Martin has joined

  103. emus has joined

  104. emus

    Hi, you are looking for people making the German translations?

  105. pep.

    nyco, no promises, but if we publish a blog post/something about this weekend's sprint tonight, can that get into the newsletter? When do you publish it?

  106. nyco

    > Hi, you are looking for people making the German translations? the JabberFr team translates it in French, I guess German would be super cool

  107. nyco

    pep. is it possible to push that online tonight? if yes, then... let's negociate: what's your price??? :)

  108. pep.

    nyco, what's your price :P

  109. pep.

    we don't have an article yet

  110. nyco

    how much time?

  111. nyco

    can you write without too much pressure?

  112. pep.

    Ok the current mood is "we can get it into the next one" :x

  113. pep.

    I also do have a deadline for tomorrow and I've got lots of stuff to write down

  114. pep.

    Sorry for the trouble

  115. Daniel has joined

  116. Daniel has left

  117. nyco

    no trouble

  118. nyco

    this leaves us time to start the translation in French

  119. winfried has left

  120. winfried has joined

  121. winfried has left

  122. winfried has joined

  123. winfried has left

  124. winfried has joined

  125. arnaudj has left

  126. winfried has left

  127. winfried has joined

  128. winfried has left

  129. winfried has joined

  130. arnaudj has joined

  131. emus

    > the JabberFr team translates it in French, I guess German would be super cool Ok, probably cant make it for this release but for the next one with some more time in advance

  132. emus

    Or is translation afterwards possible as well

  133. pep.

    emus, yeah you can certainly translate it afterwards :)

  134. emus

    Thought so, fine 🙂

  135. emus has left

  136. LNJ has left

  137. debacle has left