I will have a look some times before the end of today
alacerhas left
alacerhas joined
Nÿcohas joined
debaclehas joined
debaclehas left
debaclehas joined
Alexhas left
Alexhas joined
emus
okay, is fine
alacerhas left
alacerhas joined
Nÿcohas left
Nÿcohas joined
arnaudjhas left
arnaudjhas joined
arnaudjhas left
arnaudjhas joined
arnaudjhas left
arnaudjhas joined
Nÿcohas left
Nÿcohas joined
arnaudjhas left
arnaudjhas joined
peetahhas left
DebXWoodyhas left
DebXWoodyhas joined
Nÿcohas left
Nÿcohas joined
debaclehas left
Nÿcohas left
Nÿcohas joined
arnaudjhas left
arnaudjhas joined
arnaudjhas left
arnaudjhas joined
Nÿcohas left
DebXWoodyhas left
DebXWoodyhas joined
Nÿcohas joined
peetahhas joined
DebXWoodyhas left
DebXWoodyhas joined
Nÿcohas left
Nÿcohas joined
Nÿcohas left
Nÿcohas joined
peetahhas left
peetahhas joined
Nÿcohas left
Nÿcohas joined
debaclehas joined
Nÿcohas left
arnaudjhas left
arnaudjhas joined
jcbrandhas left
kikuchiyohas joined
kikuchiyohas left
kikuchiyohas joined
kikuchiyohas left
kikuchiyohas joined
jcbrandhas joined
Nÿcohas joined
peetah
currently reviewing july newsletter: should'nt the images be hosted on xsf github accounts ?
peetah
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
peetah
then they are refered like this in the newsletter: [profanity 0.9 screenshots](content/images/july2020/ "profanity 0.9")✎
peetah
then they are refered like this in the newsletter: [profanity 0.9 screenshots](content/images/july2020/profanity09.jpg "profanity 0.9") ✏
peetah
then they are refered like this in the newsletter: [profanity 0.9 screenshots](/images/july2020/profanity09.jpg "profanity 0.9") ✏
peetah
then they are refered like this in the newsletter: [profanity 0.9 screenshots](/images/newsletters/july2020/profanity09.jpg "profanity 0.9") ✏
peetah
I correct: images could be stored in /content/images/newsletters/<monthYYY>/
emushas left
arnaudjhas left
arnaudjhas joined
emushas joined
arnaudjhas left
arnaudjhas joined
peetah
this way pelican should deal with it automatically, but I don't know about the emailed newsletter and others ways of publication
peetah
emus: ^
emus
I have no clue tbh
debaclehas left
Alexhas left
Alexhas joined
DebXWoody
peetah: Markdown format for images it '' Alt Text will be displayed, if your browser do not support images.✎
DebXWoody
peetah: Markdown format for images is '' Alt Text will be displayed, if your browser do not support images. ✏
peetah
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
arnaudjhas left
arnaudjhas joined
DebXWoody
peetah: Ah, right. https://nl.movim.eu/?blog/debxwoody%40movim.eu/182ed65c-c0cc-498e-a8d3-7b24bf60f9f0 this is like ''
DebXWoody
hover,.. Neumodischer Schnickschnack :-)
peetah
ya mein herr, whatever you said :)
emus
😂
kikuchiyohas left
DebXWoody
BTW, I like the idea of https://planet.debian.org/ this is a feed aggregator.
raspbeguyhas left
raspbeguyhas joined
Licaon_Kter
DebXWoody: there's one for XMPP too...
emus
Planet Jabber
kikuchiyohas joined
alacerhas left
alacerhas joined
DebXWoody
Ah, on jabber.org
jcbrandhas left
jcbrandhas joined
kikuchiyohas left
kikuchiyohas joined
debaclehas joined
DebXWoodyhas left
emus
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
emus
ralphm: Hello ralph, may I have administrator rights? I want to edit the MUC description for each newsletter.
peetahhas left
peetahhas joined
emus
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?
arnaudjhas left
arnaudjhas joined
arnaudjhas left
peetah
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