-
peetah
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
-
emus
Interesting, I thought only people who know xmpp read it
-
peetah
since linuxfr is a generalist open source oriented website, it brings all kind of people, from the most basic user to the hardcore developer
-
peetah
not the same audience than xmmp.org
-
peetah
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 ...
-
peetah
then it is advertised on social networks
-
peetah
did we do the social network thing for this last newsletter ?
-
emus
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
-
emus
peetah: We basically publish on social networks, but I dont have the access to twitter mastadon
-
Licaon_Kter
peetah: not sure I get it, they care about clients right? _"this client had updates"_ Ok But you want to explain XEPs? Why?
-
peetah
they want the newsletter to clearly state, when possible, how such changes, whether in clients or in XEPs, could impact a simple XMPP user
-
peetah
a kind of "Too Complex; Did'nt read" or "XMPP for noobs" additional line for each info
-
emus
Was there a sentence or phrase as a typical example what thet dont get?
-
peetah
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
-
emus
I mean usually we describe changes to a software, that is usually "impact" to the users
-
peetah
in june 9th newsletter the part about <rtcp-mux/> for example
-
emus
Okay, but I think this passage is for developers. It has few impact to users normally I think
-
peetah
it's here for expert to understand, but does it have any impact for a simple user
-
peetah
it is not stated anywhere
-
Licaon_Kter
XEPs don't have an impact until implemented, when they are... see "Clients" section.
-
emus
I would be okay to add a sentence saying what the section is for
-
peetah
Licaon_Kter: we all know that in this room, but we are talking from a simple user perspective here
-
Licaon_Kter
You keep saying "simple user" but asking for stuff not meant for that user.
-
peetah
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
-
Licaon_Kter
peetah: no, they should RTFM for the backstory...
-
Licaon_Kter
Why you'd use the newsletter for what xmpp.org (should) cover?
-
Licaon_Kter
Also, the introduction section for a XEP has info too.
-
peetah
because the newsletter is a communication tool to attract more people who could understand and contribute to XMPP
-
Licaon_Kter
But simple users can't YET understand.p.
-
peetah
if you don't make the effort to explain, they won't
-
emus
I see the problem, I wonder if the newsletter is the correct place for those people 🤔
-
emus
Actually the XSF rather refuses to focus on endusers (which is not my personal view)
-
Licaon_Kter
> Actually the XSF rather refuses to focus on endusers (which is not my personal view) That's another story....solved...not on the newsletter :)
-
peetah
happy to read any other participant willing to share their thoughts on the matter !✎ -
peetah
happy to read any other participants willing to share their thoughts on the matter ! ✏
-
emus
Licaon_Kter: I see you point - but honestly its not that we cannot put news which are interesting for newcommers aswell
-
Licaon_Kter
emus: this is not about the news but about adding more description, checking more description, etc. But yeah....as you see fit.
-
emus
ok
-
peetah
is there text stating clearly what is the goal and the target audience of the XMPP newsletter ?
-
emus
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
-
peetah
here what I propose: I'll try to work something around the 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✎ -
peetah
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 ✏
-
emus
Okay yes should be fine, lets see
-
peetah
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 ?
-
emus
Please always ping me. but by time I check myself
-
peetah
does anyone know of document that lists clients/servers/libraries supporting a given XEP ?✎ -
peetah
does anyone know of a document or website that lists clients/servers/libraries supporting a given XEP ? ✏
-
emus
The Conversations XMPP Compliance tester? there is also a Listing from.the German Datenschutzhelden
-
Licaon_Kter
emus: i think peetah wants per software, not per server
-
Licaon_Kter
Neustradamus (sp?) keeps spamming all the projects to include such a list, but...meh
-
emus
Hmm