XSF Communications Team - 2020-07-06


  1. emus has left

  2. peetah has left

  3. peetah has joined

  4. SouL has joined

  5. DebXWoody has joined

  6. alacer has left

  7. alacer has joined

  8. alacer has left

  9. alacer has joined

  10. alacer has left

  11. alacer has joined

  12. alacer has left

  13. alacer has joined

  14. Vaulor has joined

  15. Licaon_Kter has joined

  16. jcbrand has joined

  17. emus has joined

  18. peetah

    emus: I tried, but uploading files requires push access to the repository

  19. wurstsalat

    maybe we can start a link collection for potential images, and then someone with access pushes them?

  20. arnaudj has left

  21. arnaudj has joined

  22. emus

    馃憢

  23. emus

    yeah, should be fine. Maybe at the end of the month we drop some links in the PR

  24. arnaudj has left

  25. N每co has left

  26. debacle has joined

  27. arnaudj has joined

  28. N每co has joined

  29. peetah

    what should be fine ?

  30. emus

    Should be fine to do so

  31. emus

    > maybe we can start a link collection for potential images, and then someone with access pushes them?

  32. peetah

    ok

  33. peetah

    so, for now, nobody has the possibility to upload images ?

  34. DebXWoody

    :-D

  35. arnaudj has left

  36. arnaudj has joined

  37. debacle has left

  38. wurstsalat

    are there still images needed for the current issue?

  39. wurstsalat

    emus?

  40. peetah

    JSCX images are free to reuse for "reviews and similar", I'm waiting for permission to resuse screenshot from profanity since their blog does not have copyright notice, and wolfieanmmol gsocmblog does not have copyright notice either

  41. peetah

    JSCX images are free to reuse for "reviews and similar", I'm waiting for permission to resuse screenshot from profanity since their blog does not have copyright notice, and wolfieanmmol gsoc-blog does not have copyright notice either

  42. peetah

    emus, as an XSF member, could you join him to ask for permission to reuse the gif linked in the july newsletter ?

  43. wurstsalat

    for the 1.2 release of gajim we could use https://gajim.org/img/news/account-badges.png (which is CC-BY-SA, from the release post on gajim.org)

  44. SouL

    emus, regarding the other PRs that there are, no, none of the current ones apart from the newsletter belong to commteam, so don't worry

  45. alacer has left

  46. alacer has joined

  47. alacer has left

  48. alacer has joined

  49. arnaudj has left

  50. arnaudj has joined

  51. Alex has left

  52. Alex has joined

  53. alacer has left

  54. alacer has joined

  55. emus

    peetah: I have the permission I think

  56. emus

    SouL: okay, but I think there is no one in general

  57. peetah

    great

  58. N每co has left

  59. emus

    peetah: I think there is a right to quote someones publications?

  60. emus

    anyway I can contact them

  61. arnaudj has left

  62. peetah

    reusing images is not the same as quoting someone, and if there is nothing indicating the licence for republication, it is legally required to get an authorization first

  63. N每co has joined

  64. peetah

    so I guess it would be better to ask for it, if not for legal reason, at least for courtesy

  65. alacer has left

  66. alacer has joined

  67. arnaudj has joined

  68. arnaudj has left

  69. arnaudj has joined

  70. emus

    If I get all that managed by tonight I can do so otherweise I prefer to take it out and we do for the next version this procedure

  71. emus

    or we just drop our own screenshot... I mean that is allowed, right?

  72. peetah

    sure :)

  73. emus

    maybe that is the easiest way^^

  74. peetah

    then I'll do it

  75. peetah

    but it will have to be uploaded on the repo

  76. DebXWoody has left

  77. DebXWoody has joined

  78. arnaudj has left

  79. arnaudj has joined

  80. peetah

    permission to reuse profanity screenshot granted

  81. peetah

    emus: sorry, when I said I would do it, for whatever reason, I had profanity screenshot in mind

  82. peetah

    the only image permission missing is now from wolfieanmmol gsoc-blog which I won't be able to reproduce

  83. emus

    Will ask them

  84. peetah

    thanks

  85. emus

    I cobtected him

  86. emus

    I contacted him

  87. N每co has left

  88. alacer has left

  89. alacer has joined

  90. N每co has joined

  91. Alex has left

  92. Alex has joined

  93. jcbrand has left

  94. jcbrand has joined

  95. N每co has left

  96. N每co has joined

  97. arnaudj has left

  98. arnaudj has joined

  99. arnaudj has left

  100. arnaudj has joined

  101. debacle has joined

  102. arnaudj has left

  103. arnaudj has joined

  104. DebXWoody has left

  105. DebXWoody has joined

  106. arnaudj has left

  107. arnaudj has joined

  108. DebXWoody has left

  109. DebXWoody has joined

  110. kikuchiyo has left

  111. Vaulor has left

  112. Vaulor has joined

  113. kikuchiyo has joined

  114. kikuchiyo has left

  115. DebXWoody has left

  116. DebXWoody has joined

  117. DebXWoody has left

  118. DebXWoody has joined

  119. Alex has left

  120. Alex has joined

  121. DebXWoody has left

  122. DebXWoody has joined

  123. DebXWoody has left

  124. DebXWoody has joined

  125. kikuchiyo has joined

  126. DebXWoody has left

  127. DebXWoody has joined

  128. jcbrand has left

  129. kikuchiyo has left

  130. jcbrand has joined

  131. kikuchiyo has joined

  132. kikuchiyo has left

  133. arnaudj has left

  134. arnaudj has joined

  135. kikuchiyo has joined

  136. alacer has left

  137. alacer has joined

  138. emus

    Apart fromt the picture thing - any last points?

  139. peetah

    can't think of anything else

  140. arnaudj has left

  141. arnaudj has joined

  142. Wojtek has joined

  143. kikuchiyo has left

  144. emus

    Hmm, formating is weird. It shows each picture twice

  145. emus

    things like this: <img src="https://github.com/xsf/xmpp.org/blob/master/content/images/blog/profanity090.png" width="500">

  146. emus

    are rendered twice

  147. emus

    waite

  148. emus

    wait

  149. emus

    ahh, omg the preview also renders the diff!

  150. emus

    that really weird

  151. peetah

    are you inserting the html directy inside the markdown ?

  152. peetah

    are you inserting the html directly inside the markdown ?

  153. emus

    ok lets see - the html think usually works in markdown. I need to resize the picture

  154. emus

    Muy bien: https://github.com/xsf/xmpp.org/pull/714/files?short_path=83d5783#diff-83d5783deabe9450b0964958b7ab9da3

  155. emus

    so I will release now

  156. peetah

    you should not, because pelican won't understand

  157. emus

    Ah wait

  158. emus

    no tomorrow

  159. emus

    But I will close now

  160. emus

    Are you sure?

  161. emus

    wait, then I have to resize the picutre manually

  162. peetah

    you should use the markdown formating with: ![[profanity 0.9 screenshots](/images/newsletters/july2020/profanity09.jpg "profanity 0.9")

  163. peetah

    you should use the markdown formating with: ![profanity 0.9 screenshots](/images/newsletters/july2020/profanity09.jpg "profanity 0.9")

  164. peetah

    pelocan will look for the /images path according to its configuration and generate the appropriate html

  165. peetah

    pelican will look for the /images path according to its configuration and generate the appropriate html

  166. kikuchiyo has joined

  167. peetah

    and from the current pelican conf, /images is the /content/images path in the repo

  168. peetah

    there is one blog post that did exactly that... give me a sec to find it

  169. peetah

    https://github.com/xsf/xmpp.org/blob/master/content/posts/blog/Return_of_experience_on_XMPP_meetup_in_Krakow.md

  170. peetah

    an we should not put the newsletter related images into the blog directory

  171. peetah

    we should create a /content/images/newsletters/<monthYYYY> directory and store them there

  172. emus

    Okay wait

  173. emus

    ![Piotr Nosek from Erlang Solutions](/images/blog/Piotr_Nosek_MongooseIM.jpg) but they dont use the ending nameing

  174. emus

    pep. are you here?

  175. emus

    can you create a folder in here?

  176. emus

    https://github.com/xsf/xmpp.org/tree/master/content

  177. emus

    sorr in here: https://github.com/xsf/xmpp.org/tree/master/content/images

  178. emus

    "newsletter" ?

  179. peetah

    the text between double-quotes inside the parenthesis is the one used as the image title when you hover it

  180. emus

    ok

  181. pep.

    !

  182. peetah

    of course, the images won't be displayed in the github preview

  183. pep.

    emus, you can't "create a folder" in git

  184. pep.

    it doesn't make sense

  185. emus

    Okay, but how did they do 馃榾

  186. peetah

    git does not understand the "folder" concept

  187. peetah

    you have to create a file into that folder

  188. emus

    ah okay

  189. emus

    so that is that I do in the "name file" field on the top?

  190. pep.

    hmmm, maybe you can enter slashes in there :/

  191. pep.

    yeah

  192. emus

    Yes ok

  193. emus

    but I dont need to add a file in that step, right?

  194. emus

    I just "commit" the new file (/../...)

  195. pep.

    what do you want to do? Add an image somewhere?

  196. emus

    in that location afterwards. but now it just has the editor look

  197. pep.

    I have no idea how to do that via github's interface

  198. emus

    ok

  199. emus

    I just try

  200. peetah

    if i remember correctly, there is a "upload file" button

  201. peetah

    add files > upload fil

  202. peetah

    add files > upload file

  203. peetah

    add files > upload files

  204. emus

    Yes, but there I cannot create an location 馃槙

  205. alacer has left

  206. alacer has joined

  207. pep.

    Have somebody else upload the first image? and upload the rest

  208. emus

    yes was wondering

  209. peetah

    I would go in the /content/images/ folder, then clich on upload files and proceed from ther

  210. peetah

    I would go in the /content/images/ folder, then clich on upload files and proceed from there

  211. peetah

    I guess it will ask for a file from your computer and a target folder

  212. pep.

    emus, wasn't there a desktop client for github? Maybe it's easier to use

  213. peetah

    but I can't say for sure since I just have a "File uploads require push access to this repository." message

  214. peetah

    can't you just clone the repo and commit the file from there

  215. peetah

    then push

  216. peetah

    ?

  217. emus

    Ok, now I know how it works

  218. emus

    give me another 5 minutes

  219. emus

    everything is ready, you can now commit resized (smaller sized) pictures to the new location: https://github.com/xsf/xmpp.org/tree/master/content/images/newsletter

  220. emus

    in the future

  221. peetah

    great ! thanks !

  222. emus

    Okay guys, we are close! Just the new linking missing ... 馃弮鈥嶁檪锔忥笍

  223. emus

    ![profanity 0.9 screenshots](/images/newsletter/june2020/profanity090.png "profanity 0.9")

  224. emus

    ![Desktop client JSXC](/images/newsletter/june2020/jsxc41.png "Desktop client JSXC")

  225. emus

    ![RTT User Interface](/images/newsletter/june2020/dino_rtt_demo.gif "RTT User Interface")

  226. emus

    Si?

  227. peetah

    I guess so

  228. peetah

    I'm looking for a way to limit image size via pelican conf

  229. emus

    ok, hmm Github is not rendering - are you sure I cannot use the full link?

  230. emus

    Shouldnt be a problem or?

  231. peetah

    if you want pelican to do its job, then I think it has to be this way

  232. emus

    Okay, then I ignore it and leave it like this

  233. emus

    ======= Redaction Closing for June 2020 XMPP Newsletter======

  234. emus

    馃じ鈥嶁檪锔忥笍

  235. vanitasvitae

    emus, I guess you have to remove the leading "/" from the image link

  236. emus

    okay, but also for pelican?

  237. emus

    I focus on what pelican wants to see

  238. peetah

    no you have to keep the leading /

  239. emus

    ok

  240. peetah

    this is how the blog post linked above did, and it is perfectly rendered on the web site

  241. vanitasvitae

    okay, havent used pelican

  242. vanitasvitae

    just for markdown you'd have to remove the slash.

  243. peetah

    if images was in the same folder as the md, which is not the case

  244. peetah

    if "images" folder was in the same folder as the md, which is not the case

  245. emus

    we will see tomorrow

  246. peetah

    emus: you created the folder in "master" : should'nt have been created in newsletter-july2020 branch and then merged with the rest of your PR ?

  247. peetah

    I have absolutely no clue about the possible consequences

  248. emus

    fuck, I knew I did something wrong

  249. emus

    how was that possible 馃檲锔

  250. peetah

    not wrong, open to improvements :)

  251. emus

    but wait - in the master branch everything is fine?

  252. peetah

    it is

  253. pep.

    fwiw, if the image is meant to stay it might be best just to leave it there

  254. vanitasvitae

    Oh boy, dat commit history 馃槢

  255. pep.

    since it's a big binary file, otherwise you're gonna have git storing big diffs

  256. peetah

    I would have used "newsletters" rather than "newsletter" though

  257. pep.

    renaming should be fine

  258. pep.

    I think

  259. emus

    vanitasvitae: 馃檮 I know I know

  260. emus

    I used newsletter because thats the general top term. details will come if you click it

  261. emus

    vanitasvitae: If you have well experience you can sqatsch the commits but I rather leave my hands of foe today 馃

  262. emus

    vanitasvitae: If you are well experience you can sqatsch the commits but I rather leave my hands of foe today 馃

  263. emus

    vanitasvitae: If you are well experienced you can sqatsch the commits but I rather leave my hands of foe today 馃

  264. vanitasvitae

    squashing on master is a bad idea

  265. vanitasvitae

    guess for that it's too late.

  266. vanitasvitae

    In general, you should work in feature branches and merge those into master once you are ready.

  267. vanitasvitae

    It may be a good idea to make the master branch protected, so that nobody can directly push to it

  268. peetah

    can't we just reset master to the latest good commit ?

  269. emus

    vanitasvitae: Yeah, I wonder actually why that is not the case

  270. vanitasvitae

    peetah, sure, but maybe someone/something already pulled and will then have to deal with merge conflicts and stuff

  271. emus

    but on the other side we need someone to continuiously manage this

  272. vanitasvitae

    protecting the branch is a good thing imho

  273. vanitasvitae

    that way you can only contribute to it via merge requests

  274. emus

    yeah

  275. pep.

    yeah maybe ask iteam. It's also good to do that just to avoid common mistakes

  276. vanitasvitae

    yup

  277. emus

    Now I ruined it for everyone 馃槃

  278. pep.

    haha

  279. emus

    No fun anymore guys 炉\_(銉)_/炉

  280. vanitasvitae

    quick! hide it under a ton of good commits!!!

  281. peetah

    :D

  282. emus

    Haha - actually I wonder how I commited to the wrong branch. it is hard in the Github interface 馃

  283. vanitasvitae

    馃榾

  284. emus

    Enough crazy commits for today. Thanks everyone for helping out and create the release for tomorrow. The new draft PR is already open. From now on only wonderful perfect commits 馃檪

  285. peetah

    thanks emus for your work on this new newsletter

  286. emus

    Sure - now we all dance XMPP like YMCA:

  287. emus

    馃檯鈥嶁檪锔忥笍馃檰鈥嶁檪锔忥笍馃う鈥嶁檪锔忥笍馃う鈥嶁檪锔忥笍

  288. emus

    馃槃锔

  289. emus

    uhh, you have icon duplication? I do in Conversations

  290. emus

    Dino is doing weird things maybe?

  291. Licaon_Kter has left

  292. Licaon_Kter has joined

  293. arnaudj has left

  294. arnaudj has joined

  295. kikuchiyo has left

  296. alacer has left

  297. alacer has joined

  298. kikuchiyo has joined

  299. kikuchiyo has left

  300. kikuchiyo has joined

  301. kikuchiyo has left

  302. kikuchiyo has joined

  303. kikuchiyo has left

  304. kikuchiyo has joined

  305. kikuchiyo has left

  306. kikuchiyo has joined

  307. arnaudj has left

  308. arnaudj has joined

  309. la|r|ma

    interesting. So dino sends [person gesuring no][join][male symbol][emojify][emojify] This makes sense to some degree, but [emojify] is often not needed. [male symbol] = 鈾 [male symbol][emojify] = 鈾傦笍 [person gesturing no] = 馃檯 [person gesturing no][join][male symbol] = 馃檯鈥嶁檪 [person gesturing no][join][male symbol][emojify] = 馃檯鈥嶁檪锔 [person gesturing no][join][male symbol][emojify][emojify] = 馃檯鈥嶁檪锔忥笍 [person gesturing no][join][male symbol][emojify][emojify][emojify] = 馃檯鈥嶁檪锔忥笍锔

  310. la|r|ma

    ahaa it's not getting better when trying to send these things from dino 馃榾

  311. la|r|ma

    where is my unicode codepoint input field 馃榾

  312. ldkjgoiwe has joined

  313. ldkjgoiwe has left

  314. ldkjgoiwe has joined

  315. la|r|ma

    emus, file a bug with Conversations, something is very weird with Conversations here...

  316. la|r|ma

    https://logs.xmpp.org/commteam/2020-07-06#2020-07-06-87caed30d601b091

  317. arnaudj has left

  318. arnaudj has joined

  319. arnaudj has left

  320. arnaudj has joined

  321. arnaudj has left

  322. arnaudj has joined

  323. arnaudj has left

  324. arnaudj has joined

  325. alacer has left

  326. alacer has joined

  327. DebXWoody has left

  328. DebXWoody has joined

  329. ldkjgoiwe has left

  330. ldkjgoiwe has joined

  331. DebXWoody

    Hi. I think it would be much easier for the team if the commteam would have an own repository where they can work. Maybe it's possible to give just access to this reposiory and the team would be able to work on master for the daily work.

  332. ldkjgoiwe has left

  333. ldkjgoiwe has joined

  334. kikuchiyo has left

  335. ldkjgoiwe has left

  336. ldkjgoiwe has joined

  337. arnaudj has left

  338. arnaudj has joined

  339. kikuchiyo has joined

  340. kikuchiyo has left

  341. emus

    la|r|ma: ouh you are seeing this :D pep. can you imagine I got that far 馃槀馃槀馃槀 (yesterday I made actually the joke to him with the emojis)

  342. jcbrand has left

  343. kikuchiyo has joined

  344. pep.

    Yeah I had to open Conversations because I wouldn't see it properly in poezio, but I'm used to that anyway :p

  345. emus

    DebXWoody: yes, I think we try to keep it easy. I will wait if there is any outcome of the Gitlab question. But lets keep that in mind fir the september release

  346. DebXWoody

    question?

  347. DebXWoody

    What is the question?

  348. emus

    DebXWoody: jonas was evaluating if Gitlab is interesting for XSF

  349. DebXWoody

    Ah,... +1, this would be nice. I would also start to help on some topics for XSF.

  350. peetah

    I'm not sure if being interesting is really the question鈥 the real question is rather what burden will it bring and who is going to administrate the beast.

  351. DebXWoody

    administrate the beast?

  352. pep.

    peetah, it's not gitlab but gitlab.com

  353. pep.

    So same as github.com

  354. pep.

    "same", admin-wise

  355. peetah

    I mean , being independent vs depending on a microsoft owned closed source forge => no brainer

  356. peetah

    ahhhh I thought we were talking about an independant instance of gitlab

  357. DebXWoody

    I think is not requiered to have an own server. gitlab.com would be fine.

  358. pep.

    DebXWoody, well.. moving from github.com to gitlab.com because you want to stop depending on Microsoft is somewhat missing the point :p

  359. peetah

    not for me: I've been there and fled when they changed their ToS to include sharing data with third parties

  360. pep.

    There are other reasons to do this move, but this is not really one IMO

  361. DebXWoody

    pep.: It's not only Microsoft. GoogleAPI, closed software, etc. I prefer codeberg.org, but gitlab has more features and is also quite nice.

  362. peetah

    what is codeberg ? I see several projects moving there, but I did not take the time to gather information about this platform.

  363. DebXWoody

    peetah: Is't Gitea hosted by a german e.V.

  364. emus

    Guys --> offtopic, didnt wanted to provoke a discussing 馃懆

  365. ldkjgoiwe has left

  366. ldkjgoiwe has joined

  367. kikuchiyo has left

  368. vanitasvitae

    emus: by the way, "Redaktionsschluss" is "copy deadline" or "editorial deadline" ;)

  369. emus

    The German helps the German 馃檪

  370. emus

    https://github.com/xsf/xmpp.org/pull/714 馃槈锔

  371. vaulor has joined

  372. vaulor has left

  373. vaulor has joined

  374. vaulor has left

  375. vaulor has joined

  376. debacle has left

  377. jcbrand has joined

  378. DebXWoody has left

  379. kikuchiyo has joined

  380. kikuchiyo has left

  381. kikuchiyo has joined

  382. vaulor has left

  383. Martin has left

  384. Martin has joined

  385. debacle has joined

  386. debacle has left

  387. debacle has joined

  388. kikuchiyo has left

  389. ldkjgoiwe

    Suggestion: I think the "Help us to build the newsletter" part would fit better in the end of the newsletter. It's rather long and has a rather narrow target group. With the current layout, everything I see when opening the newsletter is not actually news content. I'd also consider moving the "Subscribe to the newsletter" to the end - after the reader has seen how great the newsletter is and not before. ( cc emus )

  390. emus

    Okay, interesting point. I would be okay to change this. Other opinions?

  391. pep.

    Yeah I think I agree with both points

  392. pep.

    I'd be interesting to know if putting "subscribe to the newsletter" at the top is actually efficient in terms of getting people to subscribe, and also in terms of getting people to read the article (not close it because "pff I don't want to subscribe" or similar)

  393. emus

    ldkjgoiwe: Lets see if most agrees or have other suggestion - then - if you want create a PR and suggest the actual changes. Would that be possible for you?

  394. emus

    ldkjgoiwe: Lets see if most agrees or have other suggestions - then - if you want create a PR and suggest the actual changes. Would that be possible for you?

  395. emus

    ldkjgoiwe: Lets see if most agrees or have other suggestions - then you can create a PR if you want and suggest the actual changes. Would that be possible for you?

  396. emus

    pep.: I think that does not really happen. people have educated good filters for stuff they dont care about in the internet

  397. emus

    But I think its okay to first give peopl what they wanna read

  398. wurstsalat

    emus: I'd put the 'help us' part at the end as well. don't know about the subscribe part

  399. emus

    ok, I think both is fine. most have subscribed anyway and if they want to they likely will fine it there aswell. so we dont both readers with stuff they know

  400. pep.

    Tbh I'm not subscribed to it as I'll see it anyway either here or on mastodon or.. I wonder what is the target of the newsletter really, and who actually subscribes :p

  401. pep.

    Talking of Mastodon, did Nyco share credentials with anybody else in commteam?

  402. pep.

    N每co, ^

  403. pep.

    It's very inactive at the moment

  404. N每co

    Nope

  405. pep.

    Is it possible?

  406. emus

    pep.: there are people subscribed

  407. kikuchiyo has joined

  408. arnaudj has left

  409. arnaudj has joined

  410. arnaudj has left

  411. ldkjgoiwe has left

  412. arnaudj has joined

  413. arnaudj has left

  414. arnaudj has joined

  415. kikuchiyo has left

  416. kikuchiyo has joined

  417. jcbrand has left

  418. kikuchiyo has left

  419. debacle has left

  420. Vaulor has left

  421. kikuchiyo has joined

  422. emus has left

  423. kikuchiyo has left

  424. alacer has left

  425. alacer has joined