XSF Communications Team - 2020-06-11

all I know: something takes the MD file once it's merged, and then it does someting, and finally it ends up on Pelican facing internet users

SouL: ? ^ do you know more details

If it does not work, we might need to contact iteam, emus

SouL: ok

Not long ago the server crashed and stuff was moved to a new one, maybe there's a connection there, I'm not sure

we will see what they respond

See what popped up in my feedreader: https://xmpp.org/2020/06/newsletter/

🎉

404 Not Found nginx/1.14.2

Ugh

My ttrss shows the newsletter.

same here

because we have the rss right does'nt mean the URL is right

We are working on it

At least me

do we consider the newsletter officially published, or do we wait for its publication on the blog to start translations ? ✏

peetah: You can start alreafy if you want

its the same which has been published to the other cahnnels

for those interested, the french translation is initiated here: https://linuxfr.org/redaction/news/xmpp-home-9-juin-2020

👍

it's done already? good job peetah as usual 🙂

if you wanna provide text for social media...

I'll be on a meeting

it needs review and improvements though

ok

I'm not used to social media, therefore I don't know what to provide :) any link to previous "social media" announcements ?

I published the newsletter on Movim: https://nl.movim.eu/?node/pubsub.movim.eu/xmpp/cdc4fb1e-5e96-47ff-b8bc-02e53916a9f5

last month jcbrand raised the issue of hijacked bandwidth when using linked image in the newsletter

Yeah, other people don't seem to care

I don't remember that a real decision was made

Another potential issue is that images get removed from the foreign host and then they don't render for us

should'nt they be hosted on xmmp.org then ?

I remember that you had a problem with hosting them in the github repo

this ia already the case for some images in the past: some of the former newsletters are broken there is no solution, afaik

the github repo is not an issue in terms of storage

the thing is we don't really know how to add images in Pelican, unless...

I used pelican once, and remember that there was a specific configuration to define where to store images

let me check

404

https://xmpp.org/category/newsletter.html

on both links: - the title - Continue reading...

https://docs.getpelican.com/en/stable/content.html#static-content

it's even configured in the current pelicanconf.py

so you add your picture in the PR in the right folder, and then you add the MD link: but I remember it does not work, I may be wrong

and there plenty of them right now in the repo xmpp.org/content/images/blog

well it works for the blog, then why not for the newsletter

we could fix each newsletter then

no, wait the newsletter is not the blog (tautology) in the newsletter, you upload pictures in the editor after that, I don't know where they are

you just have to put /images/newsletter/image.jpg in the relevant markdown link

so far, I've not seen any picture in the blog that was not hosted somewhere else

just that?

https://xmpp.org/2017/09/return-of-experience-on-xmpp-meetup-in-krakow/

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

oh and I was the author

well the /images/newsletter has to be created, but nothing else required

the proof it works

si I can't remember how to do it it would be nice to document it

just need to upload the image on github, which is limited to authorized users I guess

ok, so for now, we still have to fix that 404, because there is still no content available

emus: did you manage to find where the problem is ?

oh I see you 've just renamed the file ✏

oh I see you have just renamed the file ✏

so I guess we have to wait for some bot to do its job ?

peetah: Doing

i works !

thanks emus !

s/i/it/

was the issue only because of the name of the file ? ✏

😇 Thanks to Zash! who is not here

peetah: I think so, but he redeployed somehow

maybe that did it aswell

then thanks Zash as well

jcbrand: Board said we can go on with the jobs website, like linking it from the xsf site

Was the new blog announced in the newsletter back in January? Anyway https://pidgin.im/posts/2020-06-2.14.0-released/ and a 2.14.1 fixup

😨️

We should mention it, even if its very late

If you are motivated you can create pull request to the current Newsletter with a short summary on the content? ✏

there is acutally: https://pidgin.im/posts/2020-06-2.14.1-released/