XSF Communications Team - 2020-07-10

I have comments from readers concerning the opacity of the newsletter from simple XMPP users: I propose that we try to care wrapping each newsletter info in a user centric view, focusing on how such info may impact or not a reader that would be a simple user

Interesting, I thought only people who know xmpp read it

since linuxfr is a generalist open source oriented website, it brings all kind of people, from the most basic user to the hardcore developer

not the same audience than xmmp.org

do we have an idea of all the places where the newsletter is published ? I'm aware of emailing, xmpp.org, linuxfr.org, jabberfr.org , the german site where you publish the german translation ...

then it is advertised on social networks

did we do the social network thing for this last newsletter ?

I cannot do the translastions atm 😐 Helpers welcome I think it is a good point to consider making extra statements for non-xmpp people. but I would not expand the efforts at the moment. I can imagine to put an "Introduction to XMPP"/Newcomer link, but I wonder if we have the ressources for this

peetah: We basically publish on social networks, but I dont have the access to twitter mastadon

peetah: not sure I get it, they care about clients right? _"this client had updates"_ Ok But you want to explain XEPs? Why?

they want the newsletter to clearly state, when possible, how such changes, whether in clients or in XEPs, could impact a simple XMPP user

a kind of "Too Complex; Did'nt read" or "XMPP for noobs" additional line for each info

Was there a sentence or phrase as a typical example what thet dont get?

in previous newsletters, there were an abstract explaining what each cited XEP was about and I think we should put that back rather than just link to the official XEP

I mean usually we describe changes to a software, that is usually "impact" to the users

in june 9th newsletter the part about <rtcp-mux/> for example

Okay, but I think this passage is for developers. It has few impact to users normally I think

it's here for expert to understand, but does it have any impact for a simple user

it is not stated anywhere

XEPs don't have an impact until implemented, when they are... see "Clients" section.

I would be okay to add a sentence saying what the section is for

Licaon_Kter: we all know that in this room, but we are talking from a simple user perspective here

You keep saying "simple user" but asking for stuff not meant for that user.

for these users who may care to expand their understanding of the XMPP environment, it is a good idea to fill this gap in the newsletter

peetah: no, they should RTFM for the backstory...

Why you'd use the newsletter for what xmpp.org (should) cover?

Also, the introduction section for a XEP has info too.

because the newsletter is a communication tool to attract more people who could understand and contribute to XMPP

But simple users can't YET understand.p.

if you don't make the effort to explain, they won't

I see the problem, I wonder if the newsletter is the correct place for those people 🤔

Actually the XSF rather refuses to focus on endusers (which is not my personal view)

> Actually the XSF rather refuses to focus on endusers (which is not my personal view) That's another story....solved...not on the newsletter :)

happy to read any other participants willing to share their thoughts on the matter ! ✏

Licaon_Kter: I see you point - but honestly its not that we cannot put news which are interesting for newcommers aswell

emus: this is not about the news but about adding more description, checking more description, etc. But yeah....as you see fit.

ok

is there text stating clearly what is the goal and the target audience of the XMPP newsletter ?

No, but sofar the target are more developers or inside people, that those who are new to the network. (as said not my opinion). But I also dont see how we can manage newcomers with a newsletter and also how if we talk about XEPs

here what I propose: I'll try to work something around each news added for the next newsletter, and let's discuss how it goes then so that we decide if it is kept or not ✏

Okay yes should be fine, lets see

emus : are you automatically pinged when a PR is added to the xsf repo or should we not forget to mention you in each PR as I did not do right now ?

Please always ping me. but by time I check myself

does anyone know of a document or website that lists clients/servers/libraries supporting a given XEP ? ✏

The Conversations XMPP Compliance tester? there is also a Listing from.the German Datenschutzhelden

emus: i think peetah wants per software, not per server

Neustradamus (sp?) keeps spamming all the projects to include such a list, but...meh

Hmm