XSF Communications Team - 2019-11-21

https://upload.movim.eu/files/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/O9ebNLAyvYzI8xmk5UfEWdrodB54nfGkPZ0bn4Va/Capture_d_e_cran_2019-11-21_a__10.09.59.png

and boom, all green (if that means anything)

Good work everyone

I processed the German translation already. Waiting on Sven to release it

cool

Luckily my Kubuntu is back 🙂 I had to run it in nomodeset - but still I can work ٩(◕‿◕｡)۶ ✏

https://www.jabber.de/xmpp-newsletter-08-november-2019-sprints-iot-und-die-anfaenge-von-twitter/#more-1716 Danke Sven! Its online!

oh yeah!

draft tweet/toot: ===== The XMPP newsletter is again also readable in German! https://www.jabber.de/xmpp-newsletter-08-november-2019-sprints-iot-und-die-anfaenge-von-twitter/ =====

I am not inspired, have you got any original idea?

> I am not inspired, have you got any original idea? Me? about what?

a toot/tweet

It OK, just the information about translation. For me it's fine.

> a toot/tweet If I think whether its good? or you want me to translate in DE?

not even sure of that :)

simple and minimalistic is cool...

Soon, we will have 30 languages, we can not be much work just for this info. 😂

hehehe

there is only one language: XML :)

I think its fine like this

ok, go

Jabber.de will post a German tweet aswell

oh good

when?

> oh good > when? maybe today?

btw, on Mastodon we have 318 followers

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

https://fosstodon.org/web/statuses/103175457807661214

I have drafted the two next toots/tweets: https://wiki.xmpp.org/web/Twitter_and_Mastodon_content

Nÿco: https://mobile.twitter.com/jabberde

ups

its the site, but not the tweet itself

sorry

somehow I cannot extract from my phone

https://twitter.com/jabberde/status/1197465717794377729

thanks

When there is a new release of a client. We should make a screen of the client in action. It will help non technical people to understand xmpp as IM.

I can help to do such screens.

👍

I thin there was a new release of pix art. I will check the notes and see what we can share.

There is also www.omemo.top with lots of clients. I think it maybe makes more sense to advertise one client per week or so

spamming new updates is not of interest in the end. this is done in the newsletter already

screenshots: very good idea! :) always good to have visual content, well the lack of visuals is an issue imho it is kind of risky to put screenshots, because it is static (better than nothing) also the state of XMPP apps is not that good, not sure we do positive justice

You can bareley connect the presentation with new features or development steps

right

still, it is better than a logo or a screenshot of the website or repo

It could be something like: This week we would like to present `Client XYZ`

yeah...

so, we may have an issue

the XSF wants to keep neutrality

with Mastodon and Twitter "experiments" on contents related to software projects updates, we already break that neutrality

well, kind of

it is a matter of news: what comes in goes out, simple rule, factual

now, if we focus on one software project, which is cool, how would we select those projects? what schedule? in what terms should we talk about those?

still, that would be cool

contribute visibility

Let's be conservative

hehehe, I know what you think Guus :) as an XSF member and contributor, I kind of agree with this posture now, as a promoter/evangeliser, I suffer from our painful lack of content

You've already improved exposure a lot. I fear that there's a great chance of backlash if we're going further.

what the XSF could do is host a community effort that community would write those articles then the local communities could translate and publish on their own websites?

let's first see how this work

agree

The XSF is stopping no-one from doing that.

I know

Guus FYI/reminder: https://wiki.xmpp.org/web/Twitter_and_Mastodon_content 1 Week 2019-11-18/22: software 2 Week 2019-11-25/29: XSF online+offline 3 Week 2019-12-02/06: XMPP advantages

> You've already improved exposure a lot. not completely sure, we've only filled some empty spaces, well that's my feeling/opinion, maybe a matter of glass half full/empty the different XMPP projects are still not publishing enough content (long blog posts, short tweets/toots) > I fear that there's a great chance of backlash if we're going further. what kind of backblash do you thin about?

why stop? what's the problem?

A greater chance of people telling you to stop. ✏

some might (will) think this breaks the absolute neutrality that they feel is needed.

note that I do desperately not want to discuss that right here and now with you

I'm just suggesting you to take it easy, to reduce the chance that others will gear into action against this. 🙂

Then we could expand the list of Client on the xsf site and advertise something like: "Have you already check the 100 available Client we listed on our site?"

Nÿco:

yes, something like that

but to be honest, most clients offer an obsolete UX, that's not my opnion, it's the market's

I can't help but compare: when you go to the Matrix website to select a client, it is depressing, all of them are alpha or beta, nothing finished, a lot of abandonware

The idea of my project https://xmpp-messenger.de/ is to have a kind of local "German" community.

that's great

kind of the same as JabberFr.org

what about a "content factory'? we co-construct content here, on the wiki, or an etherpad, or whatever tool because we have potentially more contributors than local communities then, when the content is finished, we push it to local communities, for translation and publication

My idea is still to have a docbook xmpp user manual. Docbook is also XML. It possible to generate HTML and PDF. It possible to work on big documents because you can split the files. I do have an example somewhere.

oh, where is it?

But I don't know how translation is working. Maybe a private repo on codeberg.org I will check later.

https://uploads.debxwoody.de:5281/upload/Gtt1I7v7juEhgQhB/handbuch01.png

cool

This was the LaTeX Version,... but after this I changed to DocBook

If you think it would be a good idea to have a user manual, I can try to prepare an example. Just found https://packages.debian.org/buster/po4a ( manpage: https://manpages.debian.org/buster/po4a/po4a.7.en.html ). Sound like a tool to translate docbook :-)

I personally find it interesting my question would be: who would it be targetted for?

user manual, means users, ok, let's say end users, regular ones, not the technical ones I guess it has to be localised then

but then we could write "user" manuals, such as libraries users, that means devs those who deploy XMPP/Jabber servers are admins companies using (or willing to use) an XMPP/Jabber server for their employees/collaborators, would benefit from the "pros and cons"-style manual, probably "server/client-selection"-style doc?

For user (install Client and create an account) it is fine to have one page (md file) per operating system. The book will start with introduction, clients and accounts. This chapter is just for user. The next will be the xmpp basics. Users which would like to have more information. One chapter for provider which needs information about xmpp servers etc. Maybe is a xmpp guide along with the RFCs and XEPs.

ok, we will see