XSF Communications Team - 2020-06-29


  1. peetah has left

  2. peetah has joined

  3. la|r|ma has left

  4. la|r|ma has joined

  5. winfried has left

  6. pep.

    not what I meant. I regularly see report notes articles from goffi in the newsletter. just like that gajim article

  7. peetah has left

  8. peetah has joined

  9. Licaon_Kter has joined

  10. alacer has left

  11. alacer has joined

  12. Martin has left

  13. Martin has joined

  14. arnaudj has joined

  15. arnaudj has left

  16. arnaudj has joined

  17. emus has joined

  18. emus

    pep.: I think software releases. peetah: I would agree to rename to software releases

  19. emus

    pep.: I think software releases. peetah: I would agree to rename to software news!

  20. debacle has joined

  21. wurstsalat

    > The blog post you propose to include is about what has been done since last report about a XMPP related softaware and should be considered as a step leading to the next release of this software I totally agree, and I think renaming the section to # Software News would be best then

  22. wurstsalat

    ## Software releases > ## Software News next question: should the dev post be filed in ### Clients and applications or in a separate ### News section then?

  23. peetah

    the less we split the best it is, so the dev post of a software should go where the release of the same software goes, everything related to the same software being ordered timely

  24. peetah

    the less we split the best it is, so the dev post of a software should go where the release of the same software goes, everything related to the same software being ordered according to its publication date

  25. wurstsalat

    alright!

  26. kikuchiyo has left

  27. kikuchiyo has joined

  28. kikuchiyo has left

  29. kikuchiyo has joined

  30. emus has left

  31. emus has joined

  32. emus

    yes, lets keep it simple, almost all people won't care. wurstsalat: may you just change the PR accordingly? Then I can merge

  33. debacle has left

  34. wurstsalat

    emus, I already did :)

  35. emus

    wurstsalat: ah yeah, I should check my mails^^

  36. emus

    Github ist down?? 🤔

  37. emus

    ah works again

  38. emus

    wurstsalat, peetah, Martin, vanitasvitae, pep., DebXWoody, Licaon_Kter: So question to the recent contributors, how happy have you been so far with the Newsletter drafting on Github?

  39. wurstsalat

    emus, perfectly happy. It’s pretty easy, you don’t even need to clone the repo

  40. Licaon_Kter

    emus: didn't had time look, albeit I didn't have any news to report either :)

  41. Martin

    emus: It's fine. At least we can startvin markdown and don't have to use wiki syntax and transfer it to markdown later.

  42. emus

    Licaon_Kter: I thought you did

  43. emus

    > emus: It's fine. At least we can startvin markdown and don't have to use wiki syntax and transfer it to markdown later. that was one thought I had

  44. peetah

    It's fine for me.

  45. peetah

    The wiki needs to be updated though to detail current github workflow for new contributors who would not be familiar with it.

  46. emus

    peetah: Yes. I can do so

  47. peetah

    we also need to test the insertion of images from the github repo as discussed some week ago woth Nyco

  48. peetah

    we also need to test the insertion of images from the github repo as discussed some weeks ago with Nÿco

  49. peetah

    emus: thanks that would be great

  50. peetah

    Should'nt the addition of flags according to the language used by links, wether audio, video or text, be located next to the said links , rather than at the beginning of the related text block ?

  51. wurstsalat

    I’d say so, too

  52. debacle has joined

  53. emus

    I think at the beginning is fine, as its somehow more unified and people see where its coming from. I also lile to advertise the bunch of local background we have But if you prefer to put it to the links its fine aswell

  54. vanitasvitae

    > wurstsalat, peetah, Martin, vanitasvitae, pep., DebXWoody, Licaon_Kter: So question to the recent contributors, how happy have you been so far with the Newsletter drafting on Github? Not as happy as I thought. Editing by creating PRs adds overhead. While I dont like how dated the xmpp wiki looks, editing was easier there. Maybe we could try out drafting in githubs wiki? A big disadvantage is githubs noisiness when it comes to mails. I received around 20mails from nycos feedback on the draft.

  55. emus

    Hmn okay. So the Wiki is the same markdown format? I thought it would be good to have a merge request to increase the quality and have formulated text from the beginning. Wikis tend to most people drop links, which is much work in the end of the months. And I also prefer to have many people actually feeling they contributed more then just dropping a link

  56. pep.

    https://post.lurk.org/@pep/104426847433984774

  57. Martin

    The show me the results doesn't work for me.

  58. pep.

    ah?

  59. pep.

    What do you mean it doesn't work

  60. emus

    I need an account to vote?

  61. pep.

    yeah, mastodon account

  62. pep.

    It's fine if it's not supposed to be a really broad view, it's obviously a specific subset of the community

  63. Martin

    > yeah, mastodon account Ah, I thought I can watch the result without account.

  64. pep.

    Martin, when it's over :p

  65. Martin

    😢

  66. pep.

    That option is if you have an account and you want results right now. I think it's a shame you can't see results before

  67. winfried has joined

  68. winfried has left

  69. winfried has joined

  70. emus

    vanitasvitae: would it be possible to switch off notifications? like when creating a PR already

  71. kikuchiyo has left

  72. kikuchiyo has joined

  73. kikuchiyo has left

  74. vanitasvitae

    Sure

  75. vanitasvitae

    But I guess it gets re-enabled for each contribution of the user

  76. vanitasvitae

    And also for each new PR

  77. alacer has left

  78. alacer has joined

  79. kikuchiyo has joined

  80. kikuchiyo has left

  81. kikuchiyo has joined

  82. vanitasvitae has left

  83. vanitasvitae has joined

  84. Martin has left

  85. Martin has joined

  86. emus

    🤔 thought so. hmm, I think switching to the wiki would be fine, but I still prefer people to write fornulated sentences. A wiki invites to not do so 😐

  87. wurstsalat

    does githubs permission model permit wiki editing for specific users?

  88. DebXWoody

    vanitasvitae: I'm busy, I will come back on this topic this afternoon. Just for technical feedback. I can not provided feedback on github, I don't use it (just for profanity :-( ) .

  89. DebXWoody

    I recommend to use a tool which can md-file format, because at the end of the day it's the format which. The tool should support versions and diff. I think git and a git-frontend should be able to manage this. I also agree, the process should be easy. Maybe some contributors to not have much know-how of git. They should also be able to contribute. Process (proposal) : Day 1 to 31 the newsletter can be managed within a wiki page on git. It's possible to use vim+git+push for the technical members or git frontend for non-technical. You see what you get in the wiki page (md-file will be rendered). I think the access model of github is different as gitlab - no idea. Maybe a now repo for "newsletter" will be an option. Contribution of newsletter should be "open", but not the work o n the official website. After 31 the newsletter will be merged from the wiki git into the repository. A official review phase will start and translation. This should be fine via Merge-Requests.

  90. kikuchiyo has left

  91. kikuchiyo has joined

  92. kikuchiyo has left

  93. kikuchiyo has joined

  94. emus

    I thought about this as well. However if we go back to a wiki Id prefer a stricter policy, as I prefer not to have any links dropped as this was the case in the o'd wiki. Its okay if here and there me or soneone else has to do some work. but not for all links

  95. emus

    many topics I also have no insights and its hard to formulate a decent sentence on the topic

  96. DebXWoody

    I prefer not to have any links dropped?

  97. emus

    Many people just post their links, I saw that in the old wiki. So at the end of the month we had a bunch of links where we had to formulate the News for. I would like to make that a more community based workflow and encourage everyone to do write a few sentences on the news they are dropping. that should at least be the case for most contributions.

  98. DebXWoody

    Link: This should not be a problem - e.g. gitlab has a page edit frontend and the user is able to klick on "link" button to include links in md-file format.

  99. Wojtek has joined

  100. kikuchiyo has left

  101. peetah has left

  102. emus

    Hmm, I meant to formulate a text, not about formating links (?)

  103. peetah has joined

  104. kikuchiyo has joined

  105. kikuchiyo has left

  106. kikuchiyo has joined

  107. kikuchiyo has left

  108. kikuchiyo has joined

  109. kikuchiyo has left

  110. kikuchiyo has joined

  111. kikuchiyo has left

  112. kikuchiyo has joined

  113. kikuchiyo has left

  114. kikuchiyo has joined

  115. kikuchiyo has left

  116. kikuchiyo has joined

  117. kikuchiyo has left

  118. kikuchiyo has joined

  119. kikuchiyo has left

  120. kikuchiyo has joined

  121. kikuchiyo has left

  122. kikuchiyo has joined

  123. kikuchiyo has left

  124. kikuchiyo has joined

  125. kikuchiyo has left

  126. kikuchiyo has joined

  127. kikuchiyo has left

  128. kikuchiyo has joined

  129. kikuchiyo has left

  130. kikuchiyo has joined

  131. kikuchiyo has left

  132. kikuchiyo has joined

  133. kikuchiyo has left

  134. kikuchiyo has joined

  135. kikuchiyo has left

  136. kikuchiyo has joined

  137. kikuchiyo has left

  138. kikuchiyo has joined

  139. kikuchiyo has left

  140. kikuchiyo has joined

  141. kikuchiyo has left

  142. kikuchiyo has joined

  143. kikuchiyo has left

  144. kikuchiyo has joined

  145. kikuchiyo has left

  146. kikuchiyo has joined

  147. kikuchiyo has left

  148. kikuchiyo has joined

  149. kikuchiyo has left

  150. kikuchiyo has joined

  151. kikuchiyo has left

  152. kikuchiyo has joined

  153. kikuchiyo has left

  154. kikuchiyo has joined

  155. kikuchiyo has left

  156. kikuchiyo has joined

  157. kikuchiyo has left

  158. kikuchiyo has joined

  159. kikuchiyo has left

  160. kikuchiyo has joined

  161. kikuchiyo has left

  162. kikuchiyo has joined

  163. kikuchiyo has left

  164. kikuchiyo has joined

  165. kikuchiyo has left

  166. kikuchiyo has joined

  167. kikuchiyo has left

  168. kikuchiyo has joined

  169. kikuchiyo has left

  170. kikuchiyo has joined

  171. kikuchiyo has left

  172. kikuchiyo has joined

  173. kikuchiyo has left

  174. kikuchiyo has joined

  175. kikuchiyo has left

  176. kikuchiyo has joined

  177. kikuchiyo has left

  178. kikuchiyo has joined

  179. kikuchiyo has left

  180. kikuchiyo has joined

  181. kikuchiyo has left

  182. kikuchiyo has joined

  183. kikuchiyo has left

  184. kikuchiyo has joined

  185. kikuchiyo has left

  186. kikuchiyo has joined

  187. kikuchiyo has left

  188. kikuchiyo has joined

  189. kikuchiyo has left

  190. kikuchiyo has joined

  191. kikuchiyo has left

  192. kikuchiyo has joined

  193. kikuchiyo has left

  194. kikuchiyo has joined

  195. kikuchiyo has left

  196. kikuchiyo has joined

  197. kikuchiyo has left

  198. kikuchiyo has joined

  199. kikuchiyo has left

  200. kikuchiyo has joined

  201. kikuchiyo has left

  202. kikuchiyo has joined

  203. kikuchiyo has left

  204. kikuchiyo has joined

  205. kikuchiyo has left

  206. kikuchiyo has joined

  207. kikuchiyo has left

  208. kikuchiyo has joined

  209. kikuchiyo has left

  210. kikuchiyo has joined

  211. kikuchiyo has left

  212. kikuchiyo has joined

  213. kikuchiyo has left

  214. kikuchiyo has joined

  215. kikuchiyo has left

  216. kikuchiyo has joined

  217. kikuchiyo has left

  218. kikuchiyo has joined

  219. kikuchiyo has left

  220. kikuchiyo has joined

  221. kikuchiyo has left

  222. kikuchiyo has joined

  223. kikuchiyo has left

  224. DebXWoody

    Ah! I see. But this is not an issue which can be solved by a tool. ;-)

  225. kikuchiyo has joined

  226. kikuchiyo has left

  227. kikuchiyo has joined

  228. kikuchiyo has left

  229. kikuchiyo has joined

  230. kikuchiyo has left

  231. kikuchiyo has joined

  232. kikuchiyo has left

  233. kikuchiyo has joined

  234. kikuchiyo has left

  235. kikuchiyo has joined

  236. kikuchiyo has left

  237. kikuchiyo has joined

  238. kikuchiyo has left

  239. kikuchiyo has joined

  240. kikuchiyo has left

  241. kikuchiyo has joined

  242. kikuchiyo has left

  243. kikuchiyo has joined

  244. kikuchiyo has left

  245. kikuchiyo has joined

  246. kikuchiyo has left

  247. kikuchiyo has joined

  248. kikuchiyo has left

  249. kikuchiyo has joined

  250. peetah has left

  251. peetah has joined

  252. alacer has left

  253. alacer has joined

  254. emus has left

  255. debacle has left

  256. jcbrand has left

  257. jcbrand has joined

  258. debacle has joined

  259. debacle has left

  260. debacle has joined

  261. emus has joined

  262. jcbrand has left

  263. alacer has left

  264. alacer has joined

  265. alacer has left

  266. jcbrand has joined

  267. alacer has joined

  268. alacer has left

  269. alacer has joined

  270. arnaudj has left

  271. arnaudj has joined

  272. emus has left

  273. alacer has left

  274. alacer has joined

  275. alacer has left

  276. alacer has joined

  277. jcbrand has left

  278. peetah has left

  279. peetah has joined

  280. wurstsalat has left