DebXWoodyWhen 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.
DebXWoodyI can help to do such screens.
DebXWoodyI thin there was a new release of pix art. I will check the notes and see what we can share.
emusThere is also www.omemo.top with lots of clients. I think it maybe makes more sense to advertise one client per week or so
emusspamming new updates is not of interest in the end. this is done in the newsletter already
Nÿcoscreenshots: 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
emusYou can bareley connect the presentation with new features or development steps
Nÿcostill, it is better than a logo or a screenshot of the website or repo
emusIt could be something like: This week we would like to present `Client XYZ`
Nÿcoso, we may have an issue
Nÿcothe XSF wants to keep neutrality
Nÿcowith Mastodon and Twitter "experiments" on contents related to software projects updates, we already break that neutrality
Nÿcowell, kind of
Nÿcoit is a matter of news: what comes in goes out, simple rule, factual
Nÿconow, 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?
Nÿcostill, that would be cool
GuusLet's be conservative
Nÿcohehehe, 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
GuusYou've already improved exposure a lot. I fear that there's a great chance of backlash if we're going further.
Nÿcowhat 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?
Nÿco> 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?
Guuspeople telling you to stop.
Nÿcowhy stop? what's the problem?
GuusA greater chance of people telling you to stop.
Guussome might (will) think this breaks the absolute neutrality that they feel is needed.
Guusnote that I do desperately not want to discuss that right here and now with you
GuusI'm just suggesting you to take it easy, to reduce the chance that others will gear into action against this. 🙂
emusThen 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ÿcoyes, something like that
Nÿcobut to be honest, most clients offer an obsolete UX, that's not my opnion, it's the market's
NÿcoI 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
DebXWoodyThe idea of my project https://xmpp-messenger.de/ is to have a kind of local "German" community.
Nÿcokind of the same as JabberFr.org
Nÿcowhat 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
DebXWoodyMy 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.
Nÿcooh, where is it?
DebXWoodyBut I don't know how translation is working. Maybe a private repo on codeberg.org I will check later.
DebXWoodyThis was the LaTeX Version,... but after this I changed to DocBook
DebXWoodyIf 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 :-)
NÿcoI personally find it interesting
my question would be: who would it be targetted for?
Nÿcouser manual, means users, ok, let's say end users, regular ones, not the technical ones
I guess it has to be localised then
Nÿcobut 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?
DebXWoodyFor 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.