XSF Communications Team - 2020-07-05

I will have a look some times before the end of today

okay, is fine

currently reviewing july newsletter: should'nt the images be hosted on xsf github accounts ?

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

then they are refered like this in the newsletter: [profanity 0.9 screenshots](content/images/july2020/profanity09.jpg "profanity 0.9") ✏

then they are refered like this in the newsletter: [profanity 0.9 screenshots](/images/july2020/profanity09.jpg "profanity 0.9") ✏

then they are refered like this in the newsletter: [profanity 0.9 screenshots](/images/newsletters/july2020/profanity09.jpg "profanity 0.9") ✏

I correct: images could be stored in /content/images/newsletters/<monthYYY>/

this way pelican should deal with it automatically, but I don't know about the emailed newsletter and others ways of publication

emus: ^

I have no clue tbh

peetah: Markdown format for images is '' Alt Text will be displayed, if your browser do not support images. ✏

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

peetah: Ah, right. https://nl.movim.eu/?blog/debxwoody%40movim.eu/182ed65c-c0cc-498e-a8d3-7b24bf60f9f0 this is like ''

hover,.. Neumodischer Schnickschnack :-)

ya mein herr, whatever you said :)

😂

BTW, I like the idea of https://planet.debian.org/ this is a feed aggregator.

DebXWoody: there's one for XMPP too...

Planet Jabber

Ah, on jabber.org

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

ralphm: Hello ralph, may I have administrator rights? I want to edit the MUC description for each newsletter.

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?

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

okay

Will try tomorrow. You can also PR if you want