XSF Communications Team - 2020-07-06


  1. peetah

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

  2. wurstsalat

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

  3. emus

    πŸ‘‹

  4. emus

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

  5. peetah

    what should be fine ?

  6. emus

    Should be fine to do so

  7. emus

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

  8. peetah

    ok

  9. peetah

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

  10. DebXWoody

    :-D

  11. wurstsalat

    are there still images needed for the current issue?

  12. wurstsalat

    emus?

  13. 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

  14. 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

  15. peetah

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

  16. 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)

  17. 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

  18. emus

    peetah: I have the permission I think

  19. emus

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

  20. peetah

    great

  21. emus

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

  22. emus

    anyway I can contact them

  23. 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

  24. peetah

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

  25. 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

  26. emus

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

  27. peetah

    sure :)

  28. emus

    maybe that is the easiest way^^

  29. peetah

    then I'll do it

  30. peetah

    but it will have to be uploaded on the repo

  31. peetah

    permission to reuse profanity screenshot granted

  32. peetah

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

  33. peetah

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

  34. emus

    Will ask them

  35. peetah

    thanks

  36. emus

    I cobtected him

  37. emus

    I contacted him

  38. emus

    Apart fromt the picture thing - any last points?

  39. peetah

    can't think of anything else

  40. emus

    Hmm, formating is weird. It shows each picture twice

  41. emus

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

  42. emus

    are rendered twice

  43. emus

    waite

  44. emus

    wait

  45. emus

    ahh, omg the preview also renders the diff!

  46. emus

    that really weird

  47. peetah

    are you inserting the html directy inside the markdown ?

  48. peetah

    are you inserting the html directly inside the markdown ?

  49. emus

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

  50. emus

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

  51. emus

    so I will release now

  52. peetah

    you should not, because pelican won't understand

  53. emus

    Ah wait

  54. emus

    no tomorrow

  55. emus

    But I will close now

  56. emus

    Are you sure?

  57. emus

    wait, then I have to resize the picutre manually

  58. peetah

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

  59. peetah

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

  60. peetah

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

  61. peetah

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

  62. peetah

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

  63. peetah

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

  64. peetah

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

  65. peetah

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

  66. peetah

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

  67. emus

    Okay wait

  68. emus

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

  69. emus

    pep. are you here?

  70. emus

    can you create a folder in here?

  71. emus

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

  72. emus

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

  73. emus

    "newsletter" ?

  74. peetah

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

  75. emus

    ok

  76. pep.

    !

  77. peetah

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

  78. pep.

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

  79. pep.

    it doesn't make sense

  80. emus

    Okay, but how did they do πŸ˜€

  81. peetah

    git does not understand the "folder" concept

  82. peetah

    you have to create a file into that folder

  83. emus

    ah okay

  84. emus

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

  85. pep.

    hmmm, maybe you can enter slashes in there :/

  86. pep.

    yeah

  87. emus

    Yes ok

  88. emus

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

  89. emus

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

  90. pep.

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

  91. emus

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

  92. pep.

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

  93. emus

    ok

  94. emus

    I just try

  95. peetah

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

  96. peetah

    add files > upload fil

  97. peetah

    add files > upload file

  98. peetah

    add files > upload files

  99. emus

    Yes, but there I cannot create an location πŸ˜•

  100. pep.

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

  101. emus

    yes was wondering

  102. peetah

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

  103. peetah

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

  104. peetah

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

  105. pep.

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

  106. peetah

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

  107. peetah

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

  108. peetah

    then push

  109. peetah

    ?

  110. emus

    Ok, now I know how it works

  111. emus

    give me another 5 minutes

  112. 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

  113. emus

    in the future

  114. peetah

    great ! thanks !

  115. emus

    Okay guys, we are close! Just the new linking missing ... πŸƒβ€β™‚οΈοΈ

  116. emus

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

  117. emus

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

  118. emus

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

  119. emus

    Si?

  120. peetah

    I guess so

  121. peetah

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

  122. emus

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

  123. emus

    Shouldnt be a problem or?

  124. peetah

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

  125. emus

    Okay, then I ignore it and leave it like this

  126. emus

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

  127. emus

    πŸ€Έβ€β™‚οΈοΈ

  128. vanitasvitae

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

  129. emus

    okay, but also for pelican?

  130. emus

    I focus on what pelican wants to see

  131. peetah

    no you have to keep the leading /

  132. emus

    ok

  133. peetah

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

  134. vanitasvitae

    okay, havent used pelican

  135. vanitasvitae

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

  136. peetah

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

  137. peetah

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

  138. emus

    we will see tomorrow

  139. 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 ?

  140. peetah

    I have absolutely no clue about the possible consequences

  141. emus

    fuck, I knew I did something wrong

  142. emus

    how was that possible πŸ™ˆοΈ

  143. peetah

    not wrong, open to improvements :)

  144. emus

    but wait - in the master branch everything is fine?

  145. peetah

    it is

  146. pep.

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

  147. vanitasvitae

    Oh boy, dat commit history πŸ˜›

  148. pep.

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

  149. peetah

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

  150. pep.

    renaming should be fine

  151. pep.

    I think

  152. emus

    vanitasvitae: πŸ™„ I know I know

  153. emus

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

  154. emus

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

  155. emus

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

  156. emus

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

  157. vanitasvitae

    squashing on master is a bad idea

  158. vanitasvitae

    guess for that it's too late.

  159. vanitasvitae

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

  160. vanitasvitae

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

  161. peetah

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

  162. emus

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

  163. vanitasvitae

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

  164. emus

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

  165. vanitasvitae

    protecting the branch is a good thing imho

  166. vanitasvitae

    that way you can only contribute to it via merge requests

  167. emus

    yeah

  168. pep.

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

  169. vanitasvitae

    yup

  170. emus

    Now I ruined it for everyone πŸ˜„

  171. pep.

    haha

  172. emus

    No fun anymore guys Β―\_(ツ)_/Β―

  173. vanitasvitae

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

  174. peetah

    :D

  175. emus

    Haha - actually I wonder how I commited to the wrong branch. it is hard in the Github interface πŸ€”

  176. vanitasvitae

    πŸ˜€

  177. 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 πŸ™‚

  178. peetah

    thanks emus for your work on this new newsletter

  179. emus

    Sure - now we all dance XMPP like YMCA:

  180. emus

    πŸ™…β€β™‚οΈοΈπŸ™†β€β™‚οΈοΈπŸ€¦β€β™‚οΈοΈπŸ€¦β€β™‚οΈοΈ

  181. emus

    πŸ˜„οΈ

  182. emus

    uhh, you have icon duplication? I do in Conversations

  183. emus

    Dino is doing weird things maybe?

  184. 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] = πŸ™…β€β™‚οΈοΈοΈ

  185. la|r|ma

    ahaa it's not getting better when trying to send these things from dino πŸ˜€

  186. la|r|ma

    where is my unicode codepoint input field πŸ˜€

  187. la|r|ma

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

  188. la|r|ma

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

  189. 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.

  190. 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)

  191. pep.

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

  192. 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

  193. DebXWoody

    question?

  194. DebXWoody

    What is the question?

  195. emus

    DebXWoody: jonas was evaluating if Gitlab is interesting for XSF

  196. DebXWoody

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

  197. 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.

  198. DebXWoody

    administrate the beast?

  199. pep.

    peetah, it's not gitlab but gitlab.com

  200. pep.

    So same as github.com

  201. pep.

    "same", admin-wise

  202. peetah

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

  203. peetah

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

  204. DebXWoody

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

  205. pep.

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

  206. peetah

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

  207. pep.

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

  208. 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.

  209. peetah

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

  210. DebXWoody

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

  211. emus

    Guys --> offtopic, didnt wanted to provoke a discussing πŸ‘¨

  212. vanitasvitae

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

  213. emus

    The German helps the German πŸ™‚

  214. emus

    https://github.com/xsf/xmpp.org/pull/714 πŸ˜‰οΈ

  215. 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 )

  216. emus

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

  217. pep.

    Yeah I think I agree with both points

  218. 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)

  219. 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?

  220. 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?

  221. 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?

  222. emus

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

  223. emus

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

  224. wurstsalat

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

  225. 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

  226. 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

  227. pep.

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

  228. pep.

    NΓΏco, ^

  229. pep.

    It's very inactive at the moment

  230. NΓΏco

    Nope

  231. pep.

    Is it possible?

  232. emus

    pep.: there are people subscribed