XSF Communications Team - 2020-06-09

Newsletter day?

yes it is, I'm copy-pasting into Tinyletter

who wants to proof-read the test emailing? (it is only sent to me, I will forward it)

I can't unfortunately :( I'm on a long meeting starting now

so it's very dfficult, I don't know how to handle the copy-paste, as both Atom and GitHub rendered Markdown suck

oops, btw the markdown is not right in the Specs section with unordered lists with - and *

I did that just like in the last newsletter

ok

well it does not work on Tinyletter, nor on GitHub's MD flavor, I don't know for Pelican

I'll have to pause for a series of meetings

I've resumed the newsletter: if you can review it in the next 30 min, I'd be happy to have any help

done

gajim screenshots appear above their introducing line

I've seen that, but the is good

code

anyway, I've got it right in the newsletter

extensions bullet points are all at the same level

yeah, noticed as weel, commented in thr PR

it is a mix of - and *

oh you mean it is a github rendering issue rather than a problem with the markdown

yes, on that one precisely

it renders correctly on Atom (by GitHub)

Version 1.3.0 of [XEP-0068] => the link is not rendered on github

yes, commented as well

it seems a copy-paste issue

sorry I did not notice you made comments, I was looking at the raw file and the github rendering

oh and wrong yax.im link

ok yax.im is rendered in the newsletter... 😢

the newsletter is ready to go

\o/

no help on reviewing it in your inbox?

you trust me too much... 😢

on the blog, we can always fix it afterwards, it is a PR away on the newsletter, once it's sent... well, too late 🙂

Eat your own dog food! allo asks rightfully, why they cannot subscribe to the newsletter via XMPP https://chaos.social/@allo/104310253258280020 I suggest to arrange with edhelas, that XSF commteam has their own pubsub node on movim.eu and post there. This can currently only used by movim and salutatoi, but DebXWoody is working on a desktop client for pubsub ;-) Nice about pubsub: Typos can be fixed!

Thats a great idea 😀

the idea comes from the first comment by mastodon user j.r

absolutely, I tried in the past, but first you have to create a specific account, easy, but then you must again copy-paste it here, and I had issues, so that was way too much time spent for me

Can't you just bridge the RSS feed over?

so, no red light for the newsletter? I'll send it

I think edhelas had some rss2pubsub tool

> Can't you just bridge the RSS feed over? I had not thought of that, so I have not looked for it

oh even "gooder" if that can be automated

https://github.com/edhelas/atomtopubsub

vanitasvitae Nÿco AFAIK it must be clean Atom XML ✏

debacle, > Nÿco AFAIK it must be clean Atom XML https://github.com/edhelas/feedcleaner 😀

good catch

edhelas thought of everything!

wanna try?

Maybe edhelas can be talked into bridging the newsletter?

afaik he already bridges a number of feeds

I'm subscribed to Planet Jabber via Movim.

I'm sending the newsletter

nice

388 subscribers last issue, it was 361

so now I'm on the social media content

Yeah one would "just" need to run atomtopubsub / feedcleaner and put that on an xmpp.org pubsub component to make it somewhat official

"somewhat"

Otherwise anybody can run these things and put that on their own pubsub component

yes

Nÿco, yeah.. since it's not really defined what's official and what's not :p

for example, I have created the fosstodon/mastodon @xmpp account and I'm the only one having the password

indeed, that's what I meant

from my perspective, I prefer to have something setup and non-official, as long as it is benevolent

AFAIK there is a Blog for the newsletter on movim. The problem, for RSS Feeds there are some things nor possible (Share, Comments). It would be nice to have a real pubsub for XMPP. I think it will be possible give access on this node for different accounts.

right

oh wait, I have the first stats for this newsletter! 🙂

https://upload.movim.eu/files/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/82HkfrSRXrLrjA7pzgnqlXHU5CRxSz37PCjGgpyi/Capture_d_%C3%A9cran_de_2020-06-09_14-57-02.png

https://uploads.debxwoody.de/upload/dmdz0KRnWQhD0HBU/Movim-roles.png

👍️

> Eat your own dog food! > allo asks rightfully, why they cannot subscribe to the newsletter via XMPP > https://chaos.social/@allo/104310253258280020 > I suggest to arrange with edhelas, that XSF commteam has their own pubsub node on movim.eu and post there. > This can currently only used by movim and salutatoi, but DebXWoody is working on a desktop client for pubsub ;-) > Nice about pubsub: Typos can be fixed! And RSS feed?

It looks that Movim is using XEP-0277: Microblogging over XMPP. On Movim you can just write you information in md-syntax and will be pushed via PubSub. At least what I understood so far. I started to write a application to be able to read those microblogs: https://nl.movim.eu/?blog/DebXWoody/b1fb0016-1992-425e-ae45-0c7d9d027e3c

Nÿco, can you add a link to the rss feed of the newsletter as "Newsletter" to the @xmpp fosstodon account's profile?

Maybe below "Website"?

Hm, I don't find the newsletter landing page particularly appealing.

I'd prefer if the link would automatically contain the latest issue of the newsletter

Not sure if that's easy to do though

But having the newsletter page contain the latest post would be a nice improvement in my opinion

Maybe the paragraph advertising to sign up to the newsletter could be omitted from the email newsletter in the future. It's not very helpful for people who read the newsletter in their mailclient because they already are subscribed.

DebXWoody Note, that you can post to Movim using "jp", the command line tool of salutatoi. With jp, you can even create the id for your article yourself, which then is used by Movim for the URL. E.g. "eagle_movim_microblog" instead of "b1fb0016-1992-425e-ae45-0c7d9d027e3c".

But you might have the feature in eagle soon, anyway :-)

Cool! Still working on OX

But I'm able to send a OX message from eagle to profanity.

DebXWoody Gajim also can talk 🐂 with the gajim-openpgp plugin.

profanity -> gajim is also working

> Nÿco, can you add a link to the rss feed of the newsletter as "Newsletter" to the @xmpp fosstodon account's profile? let me check

I got caught, but it's done: is it ok?

> Maybe the paragraph advertising to sign up to the newsletter could be omitted from the email newsletter in the future. It's not very helpful for people who read the newsletter in their mailclient because they already are subscribed. that's correct differentiating by channel is the way to go but I already have to manage so many differences that not adding one can help

SouL I merged the pull request. Now I just need to wait? https://github.com/xsf/xmpp.org/blob/master/content/posts/newsletter/2020-05-01.md

yes, wait... and cry or celebrate 🙂

so, I've not been able to find time to draft the social media content... argh

emus, as soon as you open the next PR I’ll add the newest XEP updates ;)

before opening the next PR, why does it have to be done via emus repo ? would'nt it be easier for any newcomer to modify the file directly on xsf repo ?

well, can you edit on both repos wia the website?

nope only via emus repo

and I can't understand why

peetah: I dont know actually and dont understand neither

I thought you could just merge request directly

emus, I used to do this, create a PR from the XSF repo

Nÿco: I did so

will check later

ok

thanks emus ✏

peetah: emus creates a PR against the xsf repo and the you PR against his PR therefore in his repo. So the work is done in his fork and merged when it's ready. At least this was my understanding when I participated last month.

Martin: I think you are right. But is that the way togo? ✏

so this allows someone (here emus) to have the lead on the PR, rather than having everything going through xsf repo authorized users , am I right ?

Don't know I'm no Gitguru.

> so this allows someone (here emus) to have the lead on the PR, rather than having everything going through xsf repo authorized users , am I right ? I think that's the intention.

peetah: I think I will add a default @mynick, so I will be informed all the time

I can offer you guys merge rights to my repo?

I you guys want to go back to use the wiki, feel free to do so. I have no motivation at the moment anyway

I don't need it, I was more concerned about the non intuitive way of going through the xsf PR, then click on emus PR and then look for the file to edit it

We can also go for full open, and just use yo pad or something. then we just archive the final step or log for review

The intention for Github was to remove one step of formating. Also with a midterm view to host translations by xsf aswell. So you have fewer formatting hassle. Thats anyway not good as there are so many different formatying steps...

I think it is quite nice: https://nl.movim.eu/?node/pubsub.movim.eu/xmpp

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

I don't know how to improve PR commit situation. I can try to give you rights in my repository.

Profanity 0.9.0 has been released: https://profanity-im.github.io/blog/post/release-090/

Can someone just test to make a PR? - eventually, there is no fork inbetween anymore ✏

I think newsletter-july2020 is now just a branch in the XSF repository, not in mine, maybe that is better now. But I am not a gitguru either ✏

emus: done

but I can't edit from the draft PR: I have to click on newletter-July2020 branch, look for the file and then edit it.

it feels counter intuitive to me, but may be that's the only way to achieve what we're trying to do

anyway, thanks for having successfully removed one layer in this process ✏

anyway, thanks for having successfully removed one layer of this process ✏

😅️ ehh that you now cannot edit anything doesn not sound like success to me 😀

I dont see any commits anywhere

so you went to Files Changed, then the three dots?

emus: check the PR list or xsf repo

ahhhh

thats very good!

Just @mention me in the next one!

but is that harder for you now?

not harder, not easier :)

it just doesn't take me to your repo anymore

🙏️

very good

why are their two commits? Because I renamed the one from peetah? that was not good?

https://github.com/xsf/xmpp.org/pull/714/commits

there*

peetah, if you did any mistakes you should be able to edit your own PR. However, if nothings works I can merge it and you create a new one.

I did only one commit, the second comes from you, but I don't know why

ahhh you changed the title

Yeah, my bad

wont do it anymore

Story on Cisco Jabber https://blog.windfluechter.net/content/blog/2020/06/09/1758-jabber-vs-xmpp