XSF Communications Team - 2020-06-09


  1. intosi has left

  2. emus has left

  3. debacle has left

  4. intosi has joined

  5. intosi has left

  6. wurstsalat has left

  7. intosi has joined

  8. Wojtek has left

  9. intosi has left

  10. intosi has joined

  11. intosi has left

  12. intosi has joined

  13. intosi has left

  14. intosi has joined

  15. intosi has left

  16. wurstsalat has joined

  17. peetah has left

  18. peetah has joined

  19. Licaon_Kter has joined

  20. intosi has joined

  21. intosi has left

  22. intosi has joined

  23. intosi has left

  24. kikuchiyo has left

  25. kikuchiyo has joined

  26. jcbrand has joined

  27. emus has joined

  28. Martin

    Newsletter day?

  29. winfried has left

  30. winfried has joined

  31. intosi has joined

  32. Nÿco

    yes it is, I'm copy-pasting into Tinyletter

  33. Nÿco

    who wants to proof-read the test emailing? (it is only sent to me, I will forward it)

  34. winfried has left

  35. winfried has joined

  36. SouL

    I can't unfortunately :( I'm on a long meeting starting now

  37. winfried has left

  38. winfried has joined

  39. Nÿco

    so it's very dfficult, I don't know how to handle the copy-paste, as both Atom and GitHub rendered Markdown suck

  40. Nÿco

    oops, btw the markdown is not right in the Specs section with unordered lists with - and *

  41. wurstsalat

    I did that just like in the last newsletter

  42. Nÿco

    ok

  43. Nÿco

    well it does not work on Tinyletter, nor on GitHub's MD flavor, I don't know for Pelican

  44. Nÿco

    I'll have to pause for a series of meetings

  45. debacle has joined

  46. Martin has left

  47. Martin has joined

  48. Martin has left

  49. Martin has joined

  50. leirda has joined

  51. leirda has left

  52. leirda has joined

  53. leirda has left

  54. leirda has joined

  55. leirda has left

  56. leirda has joined

  57. leirda has left

  58. leirda has joined

  59. kikuchiyo has left

  60. Guus has left

  61. Guus has joined

  62. kikuchiyo has joined

  63. kikuchiyo has left

  64. Licaon_Kter has left

  65. kikuchiyo has joined

  66. Licaon_Kter has joined

  67. intosi has left

  68. intosi has joined

  69. kikuchiyo has left

  70. Nÿco

    I've resumed the newsletter: if you can review it in the next 30 min, I'd be happy to have any help

  71. Nÿco

    done

  72. peetah

    gajim screenshots appear above their introducing line

  73. Nÿco

    I've seen that, but the is good

  74. Nÿco

    code

  75. Nÿco

    anyway, I've got it right in the newsletter

  76. peetah

    extensions bullet points are all at the same level

  77. Nÿco

    yeah, noticed as weel, commented in thr PR

  78. Nÿco

    it is a mix of - and *

  79. peetah

    oh you mean it is a github rendering issue rather than a problem with the markdown

  80. Nÿco

    yes, on that one precisely

  81. Nÿco

    it renders correctly on Atom (by GitHub)

  82. leirda has left

  83. peetah

    Version 1.3.0 of [XEP-0068] => the link is not rendered on github

  84. Nÿco

    yes, commented as well

  85. Nÿco

    it seems a copy-paste issue

  86. peetah

    sorry I did not notice you made comments, I was looking at the raw file and the github rendering

  87. Nÿco

    oh and wrong yax.im link

  88. Nÿco

    ok yax.im is rendered in the newsletter... 😢

  89. Martin has left

  90. Martin has joined

  91. kikuchiyo has joined

  92. kikuchiyo has left

  93. kikuchiyo has joined

  94. kikuchiyo has left

  95. Nÿco

    the newsletter is ready to go

  96. vanitasvitae

    \o/

  97. Nÿco

    no help on reviewing it in your inbox?

  98. Nÿco

    you trust me too much... 😢

  99. kikuchiyo has joined

  100. Nÿco

    on the blog, we can always fix it afterwards, it is a PR away on the newsletter, once it's sent... well, too late 🙂

  101. debacle

    Eat your own dog food! allo asks rightfully, why they cannot subscribe to the newsletter via XMPP https://chaos.social/@allo/104310253258280020 I suggest to arrange with edhelas, that XSF commteam has their own pubsub node on movim.eu and post there. This can currently only used by movim and salutatoi, but DebXWoody is working on a desktop client for pubsub ;-) Nice about pubsub: Typos can be fixed!

  102. vanitasvitae

    Thats a great idea 😀

  103. debacle

    the idea comes from the first comment by mastodon user j.r

  104. Nÿco

    absolutely, I tried in the past, but first you have to create a specific account, easy, but then you must again copy-paste it here, and I had issues, so that was way too much time spent for me

  105. vanitasvitae

    Can't you just bridge the RSS feed over?

  106. Nÿco

    so, no red light for the newsletter? I'll send it

  107. vanitasvitae

    I think edhelas had some rss2pubsub tool

  108. Nÿco

    > Can't you just bridge the RSS feed over? I had not thought of that, so I have not looked for it

  109. Nÿco

    oh even "gooder" if that can be automated

  110. vanitasvitae

    https://github.com/edhelas/atomtopubsub

  111. debacle

    vanitasvitae Nÿco AFAIK it must be clean Atom XMPP

  112. debacle

    vanitasvitae Nÿco AFAIK it must be clean Atom XML

  113. vanitasvitae

    debacle, > Nÿco AFAIK it must be clean Atom XML https://github.com/edhelas/feedcleaner 😀

  114. Nÿco

    good catch

  115. vanitasvitae

    edhelas thought of everything!

  116. Nÿco

    wanna try?

  117. vanitasvitae

    Maybe edhelas can be talked into bridging the newsletter?

  118. vanitasvitae

    afaik he already bridges a number of feeds

  119. debacle

    I'm subscribed to Planet Jabber via Movim.

  120. Nÿco

    I'm sending the newsletter

  121. vanitasvitae

    nice

  122. Nÿco

    388 subscribers last issue, it was 361

  123. Nÿco

    so now I'm on the social media content

  124. pep.

    Yeah one would "just" need to run atomtopubsub / feedcleaner and put that on an xmpp.org pubsub component to make it somewhat official

  125. Nÿco

    "somewhat"

  126. pep.

    Otherwise anybody can run these things and put that on their own pubsub component

  127. Nÿco

    yes

  128. pep.

    Nÿco, yeah.. since it's not really defined what's official and what's not :p

  129. Nÿco

    for example, I have created the fosstodon/mastodon @xmpp account and I'm the only one having the password

  130. Nÿco

    indeed, that's what I meant

  131. Nÿco

    from my perspective, I prefer to have something setup and non-official, as long as it is benevolent

  132. DebXWoody

    AFAIK there is a Blog for the newsletter on movim. The problem, for RSS Feeds there are some things nor possible (Share, Comments). It would be nice to have a real pubsub for XMPP. I think it will be possible give access on this node for different accounts.

  133. Nÿco

    right

  134. Nÿco

    oh wait, I have the first stats for this newsletter! 🙂

  135. Nÿco

    https://upload.movim.eu/files/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/82HkfrSRXrLrjA7pzgnqlXHU5CRxSz37PCjGgpyi/Capture_d_%C3%A9cran_de_2020-06-09_14-57-02.png

  136. DebXWoody

    https://uploads.debxwoody.de/upload/dmdz0KRnWQhD0HBU/Movim-roles.png

  137. Nÿco

    👍️

  138. emus

    > Eat your own dog food! > allo asks rightfully, why they cannot subscribe to the newsletter via XMPP > https://chaos.social/@allo/104310253258280020 > I suggest to arrange with edhelas, that XSF commteam has their own pubsub node on movim.eu and post there. > This can currently only used by movim and salutatoi, but DebXWoody is working on a desktop client for pubsub ;-) > Nice about pubsub: Typos can be fixed! And RSS feed?

  139. DebXWoody

    It looks that Movim is using XEP-0277: Microblogging over XMPP. On Movim you can just write you information in md-syntax and will be pushed via PubSub. At least what I understood so far. I started to write a application to be able to read those microblogs: https://nl.movim.eu/?blog/DebXWoody/b1fb0016-1992-425e-ae45-0c7d9d027e3c

  140. vanitasvitae

    Nÿco, can you add a link to the rss feed of the newsletter as "Newsletter" to the @xmpp fosstodon account's profile?

  141. vanitasvitae

    Maybe below "Website"?

  142. vanitasvitae

    Hm, I don't find the newsletter landing page particularly appealing.

  143. vanitasvitae

    I'd prefer if the link would automatically contain the latest issue of the newsletter

  144. vanitasvitae

    Not sure if that's easy to do though

  145. vanitasvitae

    But having the newsletter page contain the latest post would be a nice improvement in my opinion

  146. Martin

    Maybe the paragraph advertising to sign up to the newsletter could be omitted from the email newsletter in the future. It's not very helpful for people who read the newsletter in their mailclient because they already are subscribed.

  147. debacle

    DebXWoody Note, that you can post to Movim using "jp", the command line tool of salutatoi. With jp, you can even create the id for your article yourself, which then is used by Movim for the URL. E.g. "eagle_movim_microblog" instead of "b1fb0016-1992-425e-ae45-0c7d9d027e3c".

  148. debacle

    But you might have the feature in eagle soon, anyway :-)

  149. DebXWoody

    Cool! Still working on OX

  150. DebXWoody

    But I'm able to send a OX message from eagle to profanity.

  151. kikuchiyo has left

  152. debacle

    DebXWoody Gajim also can talk 🐂 with the gajim-openpgp plugin.

  153. DebXWoody

    profanity -> gajim is also working

  154. DebXWoody needs longer weekends ;-)

  155. kikuchiyo has joined

  156. kikuchiyo has left

  157. kikuchiyo has joined

  158. Nÿco

    > Nÿco, can you add a link to the rss feed of the newsletter as "Newsletter" to the @xmpp fosstodon account's profile? let me check

  159. emus has left

  160. emus has joined

  161. Nÿco

    I got caught, but it's done: is it ok?

  162. Nÿco

    > Maybe the paragraph advertising to sign up to the newsletter could be omitted from the email newsletter in the future. It's not very helpful for people who read the newsletter in their mailclient because they already are subscribed. that's correct differentiating by channel is the way to go but I already have to manage so many differences that not adding one can help

  163. emus

    SouL I merged the pull request. Now I just need to wait? https://github.com/xsf/xmpp.org/blob/master/content/posts/newsletter/2020-05-01.md

  164. kikuchiyo has left

  165. kikuchiyo has joined

  166. kikuchiyo has left

  167. kikuchiyo has joined

  168. kikuchiyo has left

  169. kikuchiyo has joined

  170. kikuchiyo has left

  171. kikuchiyo has joined

  172. kikuchiyo has left

  173. kikuchiyo has joined

  174. kikuchiyo has left

  175. kikuchiyo has joined

  176. Nÿco

    yes, wait... and cry or celebrate 🙂

  177. Nÿco

    so, I've not been able to find time to draft the social media content... argh

  178. kikuchiyo has left

  179. kikuchiyo has joined

  180. wurstsalat

    emus, as soon as you open the next PR I’ll add the newest XEP updates ;)

  181. debacle has left

  182. peetah

    before opening the next PR, why does it have to be done via emus repo ? would'nt it be easier for any newcomer to modify the file directly on xsf repo ?

  183. Wojtek has joined

  184. Nÿco

    well, can you edit on both repos wia the website?

  185. peetah

    nope only via emus repo

  186. peetah

    and I can't understand why

  187. emus

    peetah: I dont know actually and dont understand neither

  188. emus

    I thought you could just merge request directly

  189. Nÿco

    emus, I used to do this, create a PR from the XSF repo

  190. emus

    Nÿco: I did so

  191. emus

    will check later

  192. Nÿco

    ok

  193. peetah

    thanks emsu

  194. peetah

    thanks emus

  195. Martin

    peetah: emus creates a PR against the xsf repo and the you PR against his PR therefore in his repo. So the work is done in his fork and merged when it's ready. At least this was my understanding when I participated last month.

  196. emus

    Martin: I think you are right. But is that the normal way?

  197. emus

    Martin: I think you are right. But is that the way togo?

  198. peetah

    so this allows someone (here emus) to have the lead on the PR, rather than having everything going through xsf repo authorized users , am I right ?

  199. Martin

    Don't know I'm no Gitguru.

  200. Martin

    > so this allows someone (here emus) to have the lead on the PR, rather than having everything going through xsf repo authorized users , am I right ? I think that's the intention.

  201. emus

    peetah: I think I will add a default @mynick, so I will be informed all the time

  202. emus

    I can offer you guys merge rights to my repo?

  203. emus

    I you guys want to go back to use the wiki, feel free to do so. I have no motivation at the moment anyway

  204. peetah

    I don't need it, I was more concerned about the non intuitive way of going through the xsf PR, then click on emus PR and then look for the file to edit it

  205. emus

    We can also go for full open, and just use yo pad or something. then we just archive the final step or log for review

  206. emus

    The intention for Github was to remove one step of formating. Also with a midterm view to host translations by xsf aswell. So you have fewer formatting hassle. Thats anyway not good as there are so many different formatying steps...

  207. DebXWoody

    I think it is quite nice: https://nl.movim.eu/?node/pubsub.movim.eu/xmpp

  208. emus has left

  209. emus has joined

  210. intosi has left

  211. intosi has joined

  212. intosi has left

  213. intosi has joined

  214. intosi has left

  215. emus has left

  216. emus has joined

  217. intosi has joined

  218. arnaudj has left

  219. intosi has left

  220. arnaudj has joined

  221. arnaudj has left

  222. arnaudj has joined

  223. emus

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

  224. emus

    I don't know how to improve PR commit situation. I can try to give you rights in my repository.

  225. DebXWoody

    Profanity 0.9.0 has been released: https://profanity-im.github.io/blog/post/release-090/

  226. emus

    Can someone just test to make a PR - eventually, there is no fork inbetween anymore

  227. emus

    Can someone just test to make a PR? - eventually, there is no fork inbetween anymore

  228. emus

    I think newsletter-july2020 is now just a branch in the XSF repostiory, not in mine, maybe that is better now. But I am not a gitguru either

  229. emus

    I think newsletter-july2020 is now just a branch in the XSF repository, not in mine, maybe that is better now. But I am not a gitguru either

  230. debacle has joined

  231. debacle has left

  232. debacle has joined

  233. intosi has joined

  234. peetah

    emus: done

  235. peetah

    but I can't edit from the draft PR: I have to click on newletter-July2020 branch, look for the file and then edit it.

  236. peetah

    it feels counter intuitive to me, but may be that's the only way to achieve what we're trying to do

  237. peetah

    anyway, thanks for successfully removing one layer in this process

  238. peetah

    anyway, thanks for having successfully removed one layer in this process

  239. peetah

    anyway, thanks for having successfully removed one layer of this process

  240. intosi has left

  241. emus

    😅️ ehh that you now cannot edit anything doesn not sound like success to me 😀

  242. emus

    I dont see any commits anywhere

  243. emus

    so you went to Files Changed, then the three dots?

  244. peetah

    emus: check the PR list or xsf repo

  245. emus

    ahhhh

  246. emus

    thats very good!

  247. emus

    Just @mention me in the next one!

  248. emus

    but is that harder for you now?

  249. peetah

    not harder, not easier :)

  250. peetah

    it just doesn't take me to your repo anymore

  251. emus

    🙏️

  252. emus

    very good

  253. emus

    why are their two commits? Because I renamed the one from peetah? that was not good?

  254. emus

    https://github.com/xsf/xmpp.org/pull/714/commits

  255. emus

    there*

  256. emus

    peetah, if you did any mistakes you should be able to edit your own PR. However, if nothings works I can merge it and you create a new one.

  257. peetah

    I did only one commit, the second comes from you, but I don't know why

  258. peetah

    ahhh you changed the title

  259. emus

    Yeah, my bad

  260. intosi has joined

  261. emus

    wont do it anymore

  262. emus

    Story on Cisco Jabber https://blog.windfluechter.net/content/blog/2020/06/09/1758-jabber-vs-xmpp

  263. intosi has left

  264. intosi has joined

  265. arnaudj has left

  266. arnaudj has joined

  267. intosi has left

  268. arnaudj has left

  269. intosi has joined

  270. jcbrand has left

  271. intosi has left

  272. intosi has joined

  273. intosi has left

  274. emus has left