emus: I'm not sure that we should link to you existing pull request
jcbrand
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.
emus
jcbrand: Hmm, you mean for the people? I dont understand yet why to creat new PR?
ahh you mean for muc. Then we can davise to the PR general site and look for the recent month?✎
emus
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? ✏
emus
Anyway, do you have all information you need for the release?
jcbrand
I think we can create a newsletter label for the PR and mark it with that. Then we can probably fine a URL which will link to the latest PR via there label.✎
jcbrand
I think we can create a "newsletter" label for the PR and mark it with that. Then we can probably fine a URL which will link to the latest PR via there label.✎✏
jcbrand
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. ✏
jcbrand
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.
jcbrand
I can do that manually, just put the URLs to the messages in a comment in the PR.
jcbrand
I'll look into merging the PR and sending it the newsletter tonight✎
jcbrand
I'll look into merging the PR and sending out the newsletter tonight ✏
emus
> 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
emus
jcbrand: Alright, ping me if I can do anything
arnaudjhas left
arnaudjhas joined
debaclehas left
jcbrandhas left
debaclehas joined
jcbrandhas joined
DebXWoodyhas left
jcbrand
emus: I left a message on github regarding images, perhaps others here can also have a look there.
jcbrand
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.
jcbrand
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.
emus
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
jcbrand
I'm not referring to you uploading them there
jcbrand
My point is they need to be hosted somewhere
jcbrand
And originally I thought we'll put them in the repo, but now I think we shouldn't.
emus
jcbrand: but how have you processdd them before?
peetahhas left
emus
ok. so you uploaded those to the repo?
peetahhas joined
emus
I think there is a way to work around storing in the repo
emus
you can send the newsletter without this time
jcbrand
We never included images in the newsletter before, at least not when I sent it out
emus
🤔
thats wrong, all the recent ones had images? Or what do I not understand?
emushas left
debaclehas left
peetahhas left
peetahhas joined
Wojtekhas joined
emushas joined
DebXWoodyhas joined
DebXWoodyhas left
emushas left
emushas joined
debaclehas joined
jcbrand
I didn't work on the recent ones. I see that the last one simply points to an image on someone else's blog.
jcbrand
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
emus
jcbrand: You mean working with links?
jcbrand
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
jcbrand
In any case, I've merged the newsletter now
jcbrand
Once it's live I'll send out the email
jcbrand
hmmm... I checked locally and I see there are a bunch of broken links... for example to the translations
jcbrand
I'll have to fix that first... but I have to go now
emus
jcbrand: Can I do something?
emus
yes I understand about the domain
DebXWoodyhas joined
DebXWoodyhas left
DebXWoodyhas joined
jcbrand
No worries, I've now pushed a commit to fix various links
DebXWoodyhas left
jcbrand
Ok, I've sent out the newsletter. Fingers crossed it's all OK