XSF Communications Team - 2019-10-01

  1. arnaudj has left
  2. arnaudj has joined
  3. LNJ has joined
  4. emus has joined
  5. arnaudj has left
  6. arnaudj has joined
  7. Martin has left
  8. Martin has joined
  9. nyco the dead line is... before the next newsletter? :)
  10. nyco so I'll work on the newsletter, the real one, the one we send by email, that lands in your inbox
  11. nyco meanwhile, how do we want to promote this issue on Twitter?
  12. nyco https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/yBnLRbFARwFNH9oXGtPB9lVsuwUscCsPG1qm3kxS/Capture_d_e_cran_2019-10-01_a__08.44.43.png
  13. nyco my draft/proposition to you for today, like this afternoon: " The XMPP Newsletter is out! Read the latest news from the XMPP/Jabber communities: articles, events, software releases (servers, clients/apps, libraries)... [link] #social #instantmessaging #chat " what illustration?
  14. nyco maybe add a "Please share" or "Please Retweet"?
  15. debacle has joined
  16. jcbrand has left
  17. jcbrand has joined
  18. nyco I've just pushed "the button" on the newsletter... it is sending now to our 279 subscribers
  19. nyco as a subscriber, I have received it
  20. nyco please merge PR https://github.com/xsf/xmpp.org/pull/614 and deploy on our blog thanks all! it has been a real team effort, I am glad, it's hard but it works
  21. emus nyco: how do you want me to provide the translations?
  22. pep. emus, are you affiliated with jabber.de or sth btw?
  23. ralphm I have received it.
  24. emus pep.: no, why?
  25. pep. Just curious
  26. pep. Do you have a venue to expose the translation like we do with jabberfr maybe? I don't know if xmpp.org has multi-lang support(?)
  27. emus pep.: I dont know what you mean exactly. I have a github account if that help xD
  28. emus But I can also provide it as plain text in german and maybe spanish
  29. pep. emus: I don't know if xmpp.org can expose one article in multiple languages is what I'm saying
  30. pep. For the French translations we publish it on jabberfr.org
  31. emus Ahh, okay. now I understand
  32. emus I can ask the jabber.de guys if they are interested
  33. nyco that would be great
  34. nyco do they have a wiki or some tool to host the translation process?
  35. nyco https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/YNx98Bbor2jwCaIQhyOg6fU2GtsjGQotLpD09XEg/Capture_d_e_cran_2019-10-01_a__12.08.15.png
  36. emus no clue, I guess not. tell me what would be ideal for you
  37. emus I might can arrange
  38. nyco " The XMPP Newsletter is out! Read the latest news from the XMPP/Jabber communities: articles, events, software releases with servers, clients/apps, and services... [link] #social #instantmessaging #chat "
  39. emus nyco: Jabber.de said they re in 😃
  40. nyco es ist gut!
  41. nyco (that's all my German, sorry...)
  42. nyco so feel free, it's CC by-sa
  43. nyco please tell us when it's published so we can cover it on the next issue :)
  44. emus Sure, will check out! try to look if I can do it for spanish aswell
  45. nyco that would be awesome
  46. emus Läuft! 😉
  47. debacle has left
  48. nyco danke schön!
  49. Martin Speaking of the wiki: Would you be open to use an etherpad or something else supporting markdown for collecting the newsletter topics? That would make it a lot easier to transfer it to pelican.
  50. SouL Yeah, I already raised that matter, we need something with history as well, maybe not to collect the topics but at least to write the newsletter
  51. SouL to allow easier collaboration
  52. vanitasvitae has left
  53. vanitasvitae has joined
  54. debacle has joined
  55. nyco etherpad is cool, but text not markdown, and does not scale
  56. nyco probably link collection on the wiki, then copywriting on a markdown-friendly collab editor
  57. nyco but I'd rather have contributions, and then move to a new tool rather than people asking for a new tool and we migrate without contributions
  58. pep. nyco: "does not scale"?
  59. nyco no
  60. pep. I've had etherpads pads with tens of users without any issues
  61. pep. For collecting links I'm sure it's good enough
  62. pep. And writing the newsletter
  63. nyco in terms of community management, you don't create an empty space, hoping for spontaneous generation of contributors you start with something that is not optimised, then contributors do their thing, then you optimise the processes and tools
  64. nyco I've had the opposite experience
  65. nyco for now, the newsletter is only a link collection... that's not what a newsletter is supposed to be last month we introduced the specs this month we introduced the license and credits what improvements do you want to bring next month?
  66. nyco btw, if the tools we choose are good, we may host the translations efforts as well
  67. nyco what other local Jabber communities can we ask for translations? jabber.pl (dead)? jabber.ru? jabber.at?
  68. nyco btw, for a collab text editor, it should not only support real markdown, but also inline images
  69. Neustradamus has left
  70. Martin has left
  71. Martin has joined
  72. nyco === Planning === November * 2019-10-28 Mon: copywriting starts * 2019-11-01 Fri: end of submission, PR on GitHub * 2019-11-05 Tue: newsletter publication, blog post, promotion tweets
  73. nyco is completing the task list
  74. nyco https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter is ready for November
  75. nyco link collection still done in this wiki page for this month
  76. nyco tool for copywriting in discussion
  77. nyco https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/MASvtHh4orPao6yyJFuKb1pVAnPqAyYVUXCIsJbY/Capture_d_e_cran_2019-10-01_a__14.13.48.png
  78. nyco Twitter this month
  79. emus nyco: would put a sum to the top aswell
  80. nyco sum of what? on top of what?
  81. Guus has left
  82. Neustradamus has joined
  83. nyco > this month we introduced the license and credits oops, and images
  84. jcbrand has left
  85. emus nyco: the absolute numbers
  86. emus total subscribers
  87. nyco of what?
  88. emus for example
  89. nyco what are you talking about?
  90. nyco newsletter or Twitter?
  91. nyco https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/Fr2zFdNJVPe8CHSW2Jnhd1e8jzSn8iGuh6lSAb3q/Capture_d_e_cran_2019-10-01_a__15.02.48.png
  92. nyco that's the newsletter
  93. nyco and Twitter:
  94. nyco https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/BKVCnKChFaDNDigyRHKiBxXXP5nXrkOpT6RURPPf/Capture_d_e_cran_2019-10-01_a__15.03.29.png
  95. nyco " The XMPP Newsletter is out! Read the latest news from the XMPP/Jabber communities: articles, events, software releases with servers, clients/apps, and services... https://xmpp.org/2019/10/newsletter-01-october/ #social #instantmessaging #chat "
  96. nyco https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/eVQ3OZRGcxiZrVKQltIK87xMEAjjpEMkDKxMBytA/Capture_d_e_cran_2019-10-01_a__15.06.39.png
  97. nyco tell me if not cool
  98. emus nyco: your smtwitter stats you summed up in that spreadsheet. but is fine. is only for you
  99. nyco smtwitter what?
  100. nyco sorry, I don't get it
  101. nyco I summed nothing, I reported from https://analytics.twitter.com
  102. nyco the current number of followers are in realtime on:https://twitter.com/xmpp
  103. nyco https://twitter.com/xmpp
  104. emus Doesnt matter, forget it. I was referencing to the picture from 2:14pm
  105. nyco ok, but why do you want to report it on the metrics?
  106. emus No, I just thought could improve the overview. but its your thing, no need
  107. nyco it's not only for me, for usall
  108. emus ok
  109. nyco so I don't know he exact number of followers at any given time
  110. nyco it's not available
  111. nyco only the realtime, and it's on https://twitter.com/xmpp
  112. nyco so what would you want to copy-paste and why?
  113. emus 😄 nyco, is fine. I just had a thought. Doesnt matter
  114. nyco ok...
  115. jcbrand has joined
  116. Daniel has joined
  117. Daniel Apparently my Dino security analysis ( https://gultsch.de/dino_multiple.html ) didn't fall under this definition of relevancy :-/ > The submission must ideally be a blog or article about XMPP/Jabber and/or XMPP-based software (clients, servers, libs)
  118. winfried has left
  119. winfried has joined
  120. winfried has left
  121. winfried has joined
  122. winfried has left
  123. winfried has joined
  124. winfried has left
  125. winfried has joined
  126. Guus has joined
  127. nyco wat
  128. Martin has left
  129. nyco are you complaining the harsh way, again?
  130. Martin has joined
  131. nyco what is wrong with this? > Multiple vulnerabilities have been found in Dino, please update as soon as possible if you are a Dino user.
  132. nyco pointing to... oh wait! https://gultsch.de/dino_multiple.html
  133. Martin has left
  134. Martin has joined
  135. emus As the newsletter is about communication, I think we might can create a "Call" section. something like: Developer XY from App XY is calling for voluntary Chinese translators... or on specific problems. What do you think about it? It might help to exchange knowledge through the network
  136. nyco I like it
  137. SouL Sounds good!
  138. winfried has left
  139. winfried has joined
  140. nyco how would we select the calls?
  141. SouL It is a bit complicated I think
  142. SouL If we had previous examples it would be easier.
  143. emus I rather think, we look what people send. if there are like > 5 Calls, we need a process
  144. emus if there are only barely people useing it, thats it
  145. emus I would go first for an announcement that we plan this opportunity
  146. winfried has left
  147. winfried has joined
  148. winfried has left
  149. winfried has joined
  150. jcbrand has left
  151. jcbrand has joined
  152. Daniel has left
  153. Daniel has joined
  154. debacle has left
  155. SaltyBones has joined
  156. SaltyBones has left
  157. SaltyBones has joined
  158. winfried has left
  159. winfried has joined
  160. Neustradamus has left
  161. Neustradamus has joined
  162. winfried has left
  163. winfried has joined
  164. SaltyBones has left
  165. arnaudj has left
  166. arnaudj has joined
  167. jcbrand has left
  168. jcbrand has joined
  169. winfried has left
  170. winfried has joined
  171. debacle has joined
  172. emus has left
  173. emus has joined
  174. winfried has left
  175. winfried has joined
  176. LNJ has left
  177. jcbrand has left
  178. arnaudj has left
  179. arnaudj has joined
  180. arnaudj has left
  181. arnaudj has joined
  182. debacle has left
  183. emus has left