XSF Communications Team - 2019-09-30

https://github.com/xsf/xmpp.org/pull/614

lots of reviews, thx very much!

one last check before tomorrow merge-and-deploy? :)

https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/oTNiv2ht80AsWxAQ5CUT89RmcCYPQXiSBO9UPjlm/Capture_d_e_cran_2019-09-30_a__12.07.16.png

how about such a tweet today? "The XSF commTeam is finalising the next newsletter to be published this Tuesday 1st of October, covering the month of September: https://xmpp.org/newsletter.html"

+16 subscribers to the newsletter this month, that 6+% growth

https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/IQZXcOT1VzZEPBlV4Qc5xi6lrJSq4fVXCuC2fhpc/Capture_d_e_cran_2019-09-30_a__12.19.35.png

this month is our worst click rate so far

I explain this by the new specifications section

we continue the experiment, and we'll survey at the end of year

> how about such a tweet today? "The XSF commTeam is finalising the next newsletter to be published this Tuesday 1st of October, covering the month of September: https://xmpp.org/newsletter.html"

Tomorrow we are tweeting about it again, right?

Good ! I would add a “call to action” verb before the link, maybe “subscribe”

I would say maybe subscribe before it is published or something

arnaudj, you are too fast!

:D

SouL: Sometimes, not often! 😃

" The XSF commTeam is finalising the next newsletter to be published this Tuesday 1st of October, covering the month of September Subscribe before we send it: https://xmpp.org/newsletter.html "

" Subscribe before we send it! https://xmpp.org/newsletter.html "

just to sound more exciting :D

let's gooo

Go go go!

Thank you nyco

ok

https://twitter.com/xmpp/status/1178646822803386369

please retweet

so now, what tweet do we send tomorrow?

that's Tuesday what about Wednesday and Thursday?

It could start like "As promised yesterday [...]"

" The XMPP newsletter is out! [link] Read it while it is fresh Please subscribe to receive the next one in your inbox Share and Like this tweet! "

I would avoid using relative times on social media, as a post can last a few days I usually go for absolute dates

I have to agree with you, you are right, yes

Your tweet sounds good to me!

https://movim.eu:5280/upload/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/KFXu7SaKBDTSWME5rWXWyL8IoJngFMIsyeT2RwWk/Capture_d_e_cran_2019-09-30_a__14.35.19.png

So it is out already?

wat

the tweet, yes

please check the link

> https://twitter.com/xmpp/status/1178646822803386369

and please Like/Retweet, if you want

for the newsletter, that's tomorrow: https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter#Planning

The newsletter. As I still don't understand how I can attach my commits to your PR. I'm no dev so github sometimes is irritating me. I just used the edit in your branch and githab made PRS out of it...

😡

I would not add any changes, Martin. Just add a comment and the person working on that PR can make the changes after

I'm no dev either

for this month, opening up the newsletter-making to other people has been a huge pain

> some people feed me one thing back, some tell other things, even opposite sometimes

> the process remains open, progresses each week/month, there is still much room for improvement

> > I juggle with Mediawiki markup, then Markdown for Pelican on our blog, then Tinyletter's WYSIWYG > please ease my job, do no complexify it, it is already super hard

nyco: sorry, I didn't want to make it difficult for you, I just wanted to improve it.

I know the intention, thx very much

I still have a work in parallel, that has been a time block hole this month

*black hole

so, I observe many more people wanna contribute, that is excellent, thx very much to all

but today, our tools don't scale

the reference has always been https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter will remain there for... I don't know how long

this wiki page is cool to host the checklist, planning, etc.

but it's not Markdown

Anyway I don't have time to dig in to github thingies today. So maybe someone who has time and knowhow can put the stuff from my PR tlin the right form. I will check out this review thing this month and do it properly next time.

on GitHub, I did not see a Markdown validation/test thing

yes, time and tools, I agree

we can definitely do BaC :) (Blog as Code)

but I wouldn't do a month-long PR

that's during the link collection/aggregation

nyco, I just submitted a couple of suggestions

thx!

One was selfish, we just made a Prosody release ;)

cool

changes ported @Martin

nyco: thanks a lot

Hi, you are looking for people making the German translations?

nyco, no promises, but if we publish a blog post/something about this weekend's sprint tonight, can that get into the newsletter? When do you publish it?

> Hi, you are looking for people making the German translations? the JabberFr team translates it in French, I guess German would be super cool

pep. is it possible to push that online tonight? if yes, then... let's negociate: what's your price??? :)

nyco, what's your price :P

we don't have an article yet

how much time?

can you write without too much pressure?

Ok the current mood is "we can get it into the next one" :x

I also do have a deadline for tomorrow and I've got lots of stuff to write down

Sorry for the trouble

no trouble

this leaves us time to start the translation in French

> the JabberFr team translates it in French, I guess German would be super cool Ok, probably cant make it for this release but for the next one with some more time in advance

Or is translation afterwards possible as well

emus, yeah you can certainly translate it afterwards :)

Thought so, fine 🙂