XSF Communications Team - 2020-07-05


  1. emus has left
  2. peetah has left
  3. peetah has joined
  4. debacle has left
  5. alacer has left
  6. alacer has joined
  7. alacer has left
  8. alacer has joined
  9. Vaulor has joined
  10. kikuchiyo has left
  11. alacer has left
  12. alacer has joined
  13. alacer has left
  14. alacer has joined
  15. DebXWoody has joined
  16. DebXWoody has left
  17. DebXWoody has joined
  18. DebXWoody has left
  19. DebXWoody has joined
  20. DebXWoody has left
  21. DebXWoody has joined
  22. DebXWoody has left
  23. DebXWoody has joined
  24. DebXWoody has left
  25. DebXWoody has joined
  26. DebXWoody has left
  27. alacer has left
  28. alacer has joined
  29. DebXWoody has joined
  30. Vaulor has left
  31. alacer has left
  32. alacer has joined
  33. Vaulor has joined
  34. alacer has left
  35. alacer has joined
  36. Nÿco has left
  37. Nÿco has joined
  38. alacer has left
  39. alacer has joined
  40. DebXWoody has left
  41. DebXWoody has joined
  42. Nÿco has left
  43. DebXWoody has left
  44. DebXWoody has joined
  45. Nÿco has joined
  46. DebXWoody has left
  47. DebXWoody has joined
  48. DebXWoody has left
  49. DebXWoody has joined
  50. DebXWoody has left
  51. jcbrand has joined
  52. Licaon_Kter has joined
  53. Nÿco has left
  54. DebXWoody has joined
  55. arnaudj has left
  56. arnaudj has joined
  57. DebXWoody has left
  58. DebXWoody has joined
  59. alacer has left
  60. alacer has joined
  61. alacer has left
  62. alacer has joined
  63. Nÿco has joined
  64. alacer has left
  65. alacer has joined
  66. arnaudj has left
  67. arnaudj has joined
  68. kikuchiyo has joined
  69. DebXWoody has left
  70. DebXWoody has joined
  71. DebXWoody has left
  72. DebXWoody has joined
  73. alacer has left
  74. alacer has joined
  75. emus has joined
  76. kikuchiyo has left
  77. Nÿco has left
  78. DebXWoody has left
  79. DebXWoody has joined
  80. peetah I will have a look some times before the end of today
  81. alacer has left
  82. alacer has joined
  83. Nÿco has joined
  84. debacle has joined
  85. debacle has left
  86. debacle has joined
  87. Alex has left
  88. Alex has joined
  89. emus okay, is fine
  90. alacer has left
  91. alacer has joined
  92. Nÿco has left
  93. Nÿco has joined
  94. arnaudj has left
  95. arnaudj has joined
  96. arnaudj has left
  97. arnaudj has joined
  98. arnaudj has left
  99. arnaudj has joined
  100. Nÿco has left
  101. Nÿco has joined
  102. arnaudj has left
  103. arnaudj has joined
  104. peetah has left
  105. DebXWoody has left
  106. DebXWoody has joined
  107. Nÿco has left
  108. Nÿco has joined
  109. debacle has left
  110. Nÿco has left
  111. Nÿco has joined
  112. arnaudj has left
  113. arnaudj has joined
  114. arnaudj has left
  115. arnaudj has joined
  116. Nÿco has left
  117. DebXWoody has left
  118. DebXWoody has joined
  119. Nÿco has joined
  120. peetah has joined
  121. DebXWoody has left
  122. DebXWoody has joined
  123. Nÿco has left
  124. Nÿco has joined
  125. Nÿco has left
  126. Nÿco has joined
  127. peetah has left
  128. peetah has joined
  129. Nÿco has left
  130. Nÿco has joined
  131. debacle has joined
  132. Nÿco has left
  133. arnaudj has left
  134. arnaudj has joined
  135. jcbrand has left
  136. kikuchiyo has joined
  137. kikuchiyo has left
  138. kikuchiyo has joined
  139. kikuchiyo has left
  140. kikuchiyo has joined
  141. jcbrand has joined
  142. Nÿco has joined
  143. peetah currently reviewing july newsletter: should'nt the images be hosted on xsf github accounts ?
  144. peetah I remember we decided to store them in content/images and I propose that we create a directory for each newsletter (i.e. july2020) and store the newsletter image in this directory
  145. peetah then they are refered like this in the newsletter: [profanity 0.9 screenshots](content/images/july2020/ "profanity 0.9")
  146. peetah then they are refered like this in the newsletter: [profanity 0.9 screenshots](content/images/july2020/profanity09.jpg "profanity 0.9")
  147. peetah then they are refered like this in the newsletter: [profanity 0.9 screenshots](/images/july2020/profanity09.jpg "profanity 0.9")
  148. peetah then they are refered like this in the newsletter: [profanity 0.9 screenshots](/images/newsletters/july2020/profanity09.jpg "profanity 0.9")
  149. peetah I correct: images could be stored in /content/images/newsletters/<monthYYY>/
  150. emus has left
  151. arnaudj has left
  152. arnaudj has joined
  153. emus has joined
  154. arnaudj has left
  155. arnaudj has joined
  156. peetah this way pelican should deal with it automatically, but I don't know about the emailed newsletter and others ways of publication
  157. peetah emus: ^
  158. emus I have no clue tbh
  159. debacle has left
  160. Alex has left
  161. Alex has joined
  162. DebXWoody peetah: Markdown format for images it '![Alt Text](URL)' Alt Text will be displayed, if your browser do not support images.
  163. DebXWoody peetah: Markdown format for images is '![Alt Text](URL)' Alt Text will be displayed, if your browser do not support images.
  164. peetah DebXWoody: right, I missed the '!', but I'm pretty sure the text between double-quotes inside the parenthesis is the one used as the image title when you hover it
  165. arnaudj has left
  166. arnaudj has joined
  167. DebXWoody peetah: Ah, right. https://nl.movim.eu/?blog/debxwoody%40movim.eu/182ed65c-c0cc-498e-a8d3-7b24bf60f9f0 this is like '![Test](https://codeberg.org/xmpp-messenger/eagle/wiki/raw/img/eagle/Screenshot_Addressbook_abook.png "ABC")'
  168. DebXWoody hover,.. Neumodischer Schnickschnack :-)
  169. peetah ya mein herr, whatever you said :)
  170. emus 😂
  171. kikuchiyo has left
  172. DebXWoody BTW, I like the idea of https://planet.debian.org/ this is a feed aggregator.
  173. raspbeguy has left
  174. raspbeguy has joined
  175. Licaon_Kter DebXWoody: there's one for XMPP too...
  176. emus Planet Jabber
  177. kikuchiyo has joined
  178. alacer has left
  179. alacer has joined
  180. DebXWoody Ah, on jabber.org
  181. jcbrand has left
  182. jcbrand has joined
  183. kikuchiyo has left
  184. kikuchiyo has joined
  185. debacle has joined
  186. DebXWoody has left
  187. emus peetah - I have no clue how to do the picutre situation right now. There are claims to provoke high traffic to website for the direct links. There are claims that we should not bloat the XSF repository. However, I prefer to keep our responsiblity on our side. And its not that we have many MB of data each time. I think it would be best to keep it at XSF as you said. To keep the data low we can reduce the number of pictures to 2. What do you think. But I would like to do that to the next version as I want to talk to the iTeam first on this
  188. emus ralphm: Hello ralph, may I have administrator rights? I want to edit the MUC description for each newsletter.
  189. peetah has left
  190. peetah has joined
  191. emus Another question: There are a bunch of open PRs in the xmpp.org repo - https://github.com/xsf/xmpp.org/pulls Shall we consider to act on those from our side? SouL?
  192. arnaudj has left
  193. arnaudj has joined
  194. arnaudj has left
  195. peetah The picture situation has already been discussed several times. From my understanding, as jcbrand suggested, it was considered a better solution to keep images in the xsf control, and as verified with Nÿco , technically it is already feasible on the pelican side
  196. arnaudj has joined
  197. emus okay
  198. emus Will try tomorrow. You can also PR if you want
  199. arnaudj has left
  200. arnaudj has joined
  201. jcbrand has left
  202. SouL has left
  203. Vaulor has left
  204. debacle has left
  205. Licaon_Kter has left