XSF Communications Team - 2019-10-04


  1. afp has joined

  2. ldkjgoiwe has left

  3. afp has left

  4. afp has joined

  5. afp has left

  6. afp has joined

  7. jcbrand has joined

  8. Daniel

    emus: no you can't. It's anschnallen

  9. Daniel

    Not beschleunigen

  10. Daniel

    Oder befestigen

  11. emus has joined

  12. LNJ has joined

  13. emus

    ok danke, ist eh noch nicht reviewed bzw. online

  14. Daniel has left

  15. Daniel has joined

  16. Martin

    Do you put the translation in a vcs so we can review and make PRs?

  17. Martin

    I was also considering translating the newsletter to german but you were faster. πŸ˜ƒ

  18. emus

    Martin: is fine, do the stuff I cannot do or what is more advanced. If you show me a place where to upload I can do so

  19. Martin

    Up to you. Xsf uses github for the.newsletter. I don't if it would make sense to also have translations in their repo. nyco what do you think?

  20. Martin

    Up to you. Xsf uses github for the newsletter. I don't know if it would make sense to also have translations in their repo. nyco what do you think?

  21. afp has left

  22. afp has joined

  23. emus

    whatever you think is right. Github would be fine for me

  24. emus

    nyco: There is one guy having an unbelievable innovative suggestion/request: Why not sending the newsletter also through XMPP? πŸ˜‚ ok srysly, why not? could be a read only group^^

  25. afp has left

  26. debacle has joined

  27. pep.

    Yeah I believe that should also be done. There could be a pubsub server on xmpp.org for this

  28. afp has joined

  29. debacle has left

  30. emus

    > Yeah I believe that should also be done. There could be a pubsub server on xmpp.org for this For what exactly now?

  31. emus

    The newsletter via xmpp?

  32. pep.

    What you said

  33. pep.

    Yeah

  34. emus

    ok

  35. emus

    Is there a todo list in the wiki?

  36. ldkjgoiwe has joined

  37. Martin

    > whatever you think is right. Github would be fine for me Then push it to github, let us have a look at it and if someone of the xsf wants to have it in their repo as well they can easily pull it.

  38. afp has left

  39. emus

    but why pull? I meant you said I need to find another pub'ish as xsf cannot do it?

  40. emus

    publisher

  41. pep.

    Martin: yeah, atm I don't think it's possible to publish multiple languages for one article. Somebody needs to put in the work and see if pelican can support that

  42. debacle has joined

  43. Martin

    emus: I don't talk about publishing there. But maybe the want to put the translation somewhere in their repo for the sake of completeness. πŸ˜ƒ

  44. emus

    ok

  45. Martin

    Regarding publishing: Did you reach jabber.de guys?

  46. afp has joined

  47. Daniel has left

  48. emus

    Martin: yes, they are happy to do so

  49. afp has left

  50. Martin

    Great, thx.

  51. afp has joined

  52. Daniel has joined

  53. Link Mauve

    β€œ12:05:10 pep.> For the French translations we publish it on jabberfr.org”, also on LinuxFR.org.

  54. Daniel has left

  55. nyco

    >> nyco> it is not about agreeing, it is about doing the right thing >Then yes it is about agreeing on what the right thing is.. still wrong it is about experimenting what users like/want

  56. nyco

    can you please stop the fight? it's boring...

  57. nyco

    > cool - then the first translation to German is done! SLIGHTLY SMILING FACE Good thing on the German unification day GRINNING FACE OH YEAH, cool! is it published somewehere? emus

  58. nyco

    > Up to you. Xsf uses github for the newsletter. I don't know if it would make sense to also have translations in their repo. nyco what do you think? what's best for translators and publishers?

  59. nyco

    > nyco: There is one guy having an unbelievable innovative suggestion/request: Why not sending the newsletter also through XMPP? FACE WITH TEARS OF JOY > ok srysly, why not? could be a read only group^^ great idea! let's try it! where and how? I guess the links will be broken though

  60. nyco

    https://docs.getpelican.com/en/stable/index.html#features Features Pelican 4 currently supports: [...] Publication of articles in multiple languages [...]

  61. nyco

    actually, we (XSF) could host the translations? not sure, need to check more in detail at what cost/effort should we do it? not sure, imho it is cool than local communities who do the work host the article do translations need to be published at the same time as the original? not for me

  62. Martin

    emus: Did you upload it somewhere already?

  63. Martin

    I was busy molesting debacle to do a debian xmpp team blog post to advertise the newsletter. :D

  64. nyco

    Martin wow, great idea!

  65. nyco

    I mean... not molesting! :)

  66. nyco

    so, the DE version of the newsletter is ready, the FR just started... :)

  67. nyco

    call to translators: if we need to rephrase the English version before it is published, in order to ease all/most translations, then let's just do that, ok?

  68. nyco

    also, question to translations: what format do you need? Mediawiki markup? Markdown? HTML? other?

  69. emus

    Martin: no, working atm

  70. Martin

    jabber.de seems to be using wordpress. No idea if they still use their own markup or work with markdown now.

  71. emus

    nyco: I can translate afterwards. I recomment to just link ala The German version will be publish in the next days overhere: jabber. de/abcde

  72. emus

    Martin: will figure out

  73. emus

    nyco: Html said Sven is goo

  74. emus

    good

  75. Martin

    emus: No rush. The publishing for proof reading is also only an offer, like 4-2*x eyes principle. If you think it is good as is you can also just publish it.

  76. emus

    Martin: ok, PM your mail and I can send you the German one for review. I just made it in a text document for the monent

  77. emus

    moment

  78. nyco

    hey, translations can be worked on the wiki as well (in addition to the Git repo)

  79. nyco

    pep. JabberFr wants/prefers what format?

  80. nyco

    translators: I think JabberFr usually does the translations on an Etherpad, but I've just participated once

  81. jcbrand has left

  82. emus

    > hey, translations can be worked on the wiki as well (in addition to the Git repo) > pep. JabberFr wants/prefers what format? can you send me a link, so I dont need to search where

  83. jcbrand has joined

  84. nyco

    emus we collect links here: https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter but maybe you can create a page, linking from: https://wiki.xmpp.org/web/CommTeam

  85. nyco

    actually, wait :)

  86. nyco

    https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter#Process

  87. nyco

    so: https://wiki.xmpp.org/web/index.php?title=French_translation_of_the_newsletter&action=edit&redlink=1

  88. nyco

    https://wiki.xmpp.org/web/index.php?title=German_translation_of_the_newsletter&action=edit&redlink=1

  89. nyco

    https://wiki.xmpp.org/web/index.php?title=Spanish_translation_of_the_newsletter&action=edit&redlink=1

  90. nyco

    you can use them... or not

  91. Daniel has joined

  92. jcbrand has left

  93. Daniel has left

  94. jcbrand has joined

  95. emus

    cool

  96. emus

    nyco: problem: how do I get an account?^^

  97. nyco

    ah

  98. nyco

    ask the iTeam

  99. emus

    ok

  100. nyco

    or use whatever tool is best for your translation team

  101. emus

    I have it in a text document at the moment. need to talk to Sven, he is on vacation as he doesnt reply I think

  102. pep.

    Jabberfr uses WordPress and I can't seem to be able to escape the crappy wysiwyg, so any format will do as I have to translate it anyway

  103. emus

    Yes, I dont see the big problem with it for the moment. I`d suggest, if we hit the 1000 subcribers point, we should rediscuss the system, also to include multilanguage

  104. nyco

    pep. in my WordPresses, I can always switch to HTML: you can't?

  105. emus

    thats what Sven from Jabber.de said aswell

  106. emus

    he asked for HTML

  107. Daniel has joined

  108. pep.

    I don't know, arnaudj might know better, I'm not WordPress expert

  109. Martin

    Hehe, seems like opening the newsletter is a lot of hassle for nyco but also pays out. πŸ˜ƒ

  110. Daniel has left

  111. jcbrand has left

  112. nyco

    indeed, it has greatly improved imho

  113. jcbrand has joined

  114. emus has left

  115. jcbrand has left

  116. emus has joined

  117. jcbrand has joined

  118. emus has left

  119. Daniel has joined

  120. Daniel has left

  121. Martin

    > nyco: problem: how do I get an account?^^ Ge0rg gave me an account

  122. emus has joined

  123. nyco

    good

  124. nyco

    emus do you have a wiki account as well?

  125. Martin

    So far he send me an odt via email and I added my comments. But maybe for the next one we can use the wiki so more people can participate. Slowly but steady improving. πŸ˜ƒ

  126. Martin

    So far he sent me an odt via email and I added my comments. But maybe for the next one we can use the wiki so more people can participate. Slowly but steady improving. πŸ˜ƒ

  127. nyco

    great, good mindset :)

  128. nyco

    btw, maybe we can split that page: https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter

  129. nyco

    we keep that content: 1 To contributors, editors, reviewers, translators 1.1 Live discussion 1.2 What determines relevancy? 1.3 Process 1.4 Planning

  130. nyco

    and we move this part to a dedicated page, that changes every month: 2 Submissions for next newsletter

  131. emus has left

  132. nyco

    this "central" page would be much lighter and would not move a lot, only updates in the process that happen not that often

  133. nyco

    and there would be no need to empty the content each month, to restart

  134. nyco

    for the per-newsletter pages, there would be on per month: we create it at the beginning of the moth, it grows, and then it's finished at the end of the month

  135. nyco

    what do you think? SouL emus Martin

  136. emus has joined

  137. nyco

    also, each per-month page can have its subpage per translation

  138. Martin

    Sounds reasonable. People interested in participating are not scared away by an empty wiki page when first looking and have all necessary information (relevancy, process) at hand.

  139. emus

    > emus do you have a wiki account as well? not yet

  140. emus

    > what do you think? SouL emus Martin i didnt full understand your plan and i am maybe to new to this to make a decent statement. I dont really care, youre probably right and is fine

  141. Daniel has joined

  142. Daniel has left

  143. Daniel has joined

  144. Daniel has left

  145. arnaudj has left

  146. arnaudj has joined

  147. eQ has joined

  148. eQ has left

  149. debacle has left

  150. debacle has joined

  151. debacle has left

  152. Martin has left

  153. Martin has joined

  154. jcbrand has left

  155. Guus has left

  156. Guus has joined

  157. arnaudj has left

  158. arnaudj has joined

  159. Vaulor has left

  160. SouL has left

  161. emus has left