XSF Communications Team - 2020-04-03

emus: I'm not sure that we should link to you existing pull request

Are we always going to use this PR? Otherwise we need to always immediately create a new or PR and then update the MUC subject.

jcbrand: Hmm, you mean for the people? I dont understand yet why to creat new PR? ahh you mean for muc. Then we can advise to the PR general site and look for the recent month? ✏

Anyway, do you have all information you need for the release?

I think we can create a "newsletter" label for the PR and mark it with that. Then we can probably find a URL which will link to the latest PR via there label. ✏

About the images, they can be added to a folder in the site, and then you link to them in the text. I don't think that can be done via the GitHub interface though.

I can do that manually, just put the URLs to the messages in a comment in the PR.

I'll look into merging the PR and sending out the newsletter tonight ✏

> I think we can create a "newsletter" label for the PR and mark it with that. Then we can probably find a URL which will link to the latest PR via there label. Yes taht works

jcbrand: Alright, ping me if I can do anything

emus: I left a message on github regarding images, perhaps others here can also have a look there.

TL/DR: On 2nd thought I'm not convinced that we should upload newsletter images to the xmpp.org repo, given that it bloats the repo for IMO negligible benefit.

So we need to find a proper solution here and I think we should just leave images this time. I'll admit that I personally don't care much for images in emails in any case.

jcbrand: I only uploaded it there because I didnt knew where to put those. You can delete the comment. However, I think its part of hightlighting things which is always good in a newsletter to let people have an glimpse over the horizon. I would continue on putting at least one or two pictures

I'm not referring to you uploading them there

My point is they need to be hosted somewhere

And originally I thought we'll put them in the repo, but now I think we shouldn't.

jcbrand: but how have you processdd them before?

ok. so you uploaded those to the repo?

I think there is a way to work around storing in the repo

you can send the newsletter without this time

We never included images in the newsletter before, at least not when I sent it out

🤔 thats wrong, all the recent ones had images? Or what do I not understand?

I didn't work on the recent ones. I see that the last one simply points to an image on someone else's blog.

I'm not sure that this is a good idea. We have no guarantee that the images will remain hosted and available and we're leeching off of other people's bandwidth

jcbrand: You mean working with links?

If you include an image by simply pasting a link that points to someone else's domain, then you're using their bandwidth and you're dependent on them keeping on hosting the image for you

In any case, I've merged the newsletter now

Once it's live I'll send out the email

hmmm... I checked locally and I see there are a bunch of broken links... for example to the translations

I'll have to fix that first... but I have to go now

jcbrand: Can I do something?

yes I understand about the domain

No worries, I've now pushed a commit to fix various links

Ok, I've sent out the newsletter. Fingers crossed it's all OK

Came to my mailbox. What about the website?