XSF Communications Team - 2019-11-21


  1. Nÿco

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

  2. Nÿco

    and boom, all green (if that means anything)

  3. emus

    Good work everyone

  4. emus

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

  5. Nÿco

    cool

  6. emus

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

  7. emus

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

  8. emus

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

  9. Nÿco

    oh yeah!

  10. Nÿco

    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/ =====

  11. Nÿco

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

  12. emus

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

  13. Nÿco

    a toot/tweet

  14. DebXWoody

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

  15. emus

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

  16. Nÿco

    not even sure of that :)

  17. Nÿco

    simple and minimalistic is cool...

  18. DebXWoody

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

  19. Nÿco

    hehehe

  20. Nÿco

    there is only one language: XML :)

  21. emus

    I think its fine like this

  22. Nÿco

    ok, go

  23. emus

    Jabber.de will post a German tweet aswell

  24. Nÿco

    oh good

  25. Nÿco

    when?

  26. emus

    > oh good > when? maybe today?

  27. Nÿco

    btw, on Mastodon we have 318 followers

  28. Nÿco

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

  29. Nÿco

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

  30. Nÿco

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

  31. emus

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

  32. emus

    ups

  33. emus

    its the site, but not the tweet itself

  34. emus

    sorry

  35. emus

    somehow I cannot extract from my phone

  36. Nÿco

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

  37. emus

    thanks

  38. DebXWoody

    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.

  39. DebXWoody

    I can help to do such screens.

  40. emus

    👍

  41. DebXWoody

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

  42. emus

    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

  43. emus

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

  44. Nÿco

    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

  45. emus

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

  46. Nÿco

    right

  47. Nÿco

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

  48. emus

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

  49. Nÿco

    yeah...

  50. Nÿco

    so, we may have an issue

  51. Nÿco

    the XSF wants to keep neutrality

  52. Nÿco

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

  53. Nÿco

    well, kind of

  54. Nÿco

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

  55. Nÿco

    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?

  56. Nÿco

    still, that would be cool

  57. Nÿco

    contribute visibility

  58. Guus

    Let's be conservative

  59. Nÿco

    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

  60. Guus

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

  61. Nÿco

    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?

  62. Guus

    let's first see how this work

  63. Nÿco

    agree

  64. Guus

    The XSF is stopping no-one from doing that.

  65. Nÿco

    I know

  66. Nÿco

    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

  67. 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?

  68. Guus

    people telling you to stop.

  69. Nÿco

    why stop? what's the problem?

  70. Guus

    A greater chance of people telling you to stop.

  71. Guus

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

  72. Guus

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

  73. Guus

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

  74. emus

    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?"

  75. emus

    Nÿco:

  76. Nÿco

    yes, something like that

  77. Nÿco

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

  78. Nÿco

    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

  79. DebXWoody

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

  80. Nÿco

    that's great

  81. Nÿco

    kind of the same as JabberFr.org

  82. Nÿco

    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

  83. DebXWoody

    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.

  84. Nÿco

    oh, where is it?

  85. DebXWoody

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

  86. DebXWoody

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

  87. Nÿco

    cool

  88. DebXWoody

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

  89. DebXWoody

    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 :-)

  90. Nÿco

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

  91. Nÿco

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

  92. Nÿco

    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?

  93. DebXWoody

    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.

  94. emus

    ok, we will see