Difference between revisions of "XMPP Newsletter"

From XMPP WIKI
Jump to navigation Jump to search
(42 intermediate revisions by 3 users not shown)
Line 2: Line 2:




== Contributors: What determines relevancy? ==
== To contributors, editors, reviewers, translators ==
 
=== Live discussion ===
 
xmpp:commteam@muc.xmpp.org?join
 
=== What determines relevancy? ===


The submission must ideally be a blog or article about XMPP/Jabber and/or
The submission must ideally be a blog or article about XMPP/Jabber and/or
Line 15: Line 21:
Make sure you read the [[Basic communication guide for XMPP techies]]
Make sure you read the [[Basic communication guide for XMPP techies]]


== Newsletter editors ==
=== Process ===
 
=== TODO/checklist ===
 
For the newsletter editors:


# Collect links in this wiki page, read and validate content
# Before: duration 1 month
# Copywriting so it is readable by humans
## Collect links in this wiki page: duration 3-4 weeks
# Add images
##* Read and validate the content
# Add clear CTA
##* Include the reporters credits!
# Subject line and preview text
## Copywrite so each content is readable by humans: duration 2-3 days
# PR on website git repo for blog post (Markdown, Pelican), and peer review
##* Add links
# Analytics from latest newsletter in spreadsheet
##* Add images
# Newsletter via Tinyletter
##* Add CTAs
# [[Twitter scheduling]]: text, image, hashtags, link, timestamp
##* Carefully craft the subject/title line, and the preview text (first lines that are sometimes previewed on email UAs)
# Empty this page, keep structure
##* Include the copywriters credits!
## PR on website git repo for blog post (Markdown, Pelican): duration the week-end before posting
##* Need at least 2 or 3 peer reviews
##* Include the reviewers credits!
## Twitter:
##* Copywrite and review draft tweet: text, image, hashtags, link
# Sending the newsletter: on D-day
## Copy-paste Newsletter on Tinyletter, test it (peer review is not yet done), send it
## Report analytics from latest newsletter in spreadsheet, send to commTeam MUC
## PR merge and deploy on website git repo for blog post
## Twitter:
##* post draft tweet
##* Report monthly metrics
# Translations: after D-day
## Start the translations: publish before next newsletter :)
##* [[French translation of the newsletter|French]]: published on JabberFr.org and LinuxFr.org, working on Etherpad, need format ?
##* [[German translation of the newsletter|German]]: published on jabber.de, working on ?, need format ?
##* [[Spanish translation of the newsletter|Spanish]]: published jabberes.org?, working on ?, need format ?
##* [[Polish translation of the newsletter|Polish]]: published ?, working on ?, need format ?
## LinkedIn (would be nice to get it back)
## Empty this page, keep structure for next newsletter


=== Planning ===
=== Planning ===


October
November
* 2019-09-27 Fri: end of submission
* 2019-10-28 Mon: copywriting starts
* 2019-09-27 Fri: PR on GitHub
* 2019-11-01 Fri: end of link submission, PR on GitHub
* 2019-10-01 Tue: newsletter publication, blog post, tweets
* 2019-11-05 Tue: newsletter publication, blog post, promotion tweets
 
== Submissions for next newsletter==
 
=== Newsletter subject/title ===
 
[ Friendly, human introduction for the month (remove this mention before publishing) ]
 
* Prepare for FOSDEM, modern XMPP features, and more news
* FOSDEM 2020 Feb, modernization of XMPP, peer networks
 
=== Intro ===
 
Welcome to the XMPP newsletter: October edition, covering the month of September.
 
New this month: we added the license (CC by-sa 4.0), and the credits as this is a community effort.
 
Be kind, inform your friends and colleagues: forward this newsletter!
 
=== Articles ===
 
Ralph Meijer, chairman of the Board of Directors of the XSF, has written an introductory piece about "[https://ralphm.net/blog/2019/09/09/fastening XMPP Message Attaching, Fastening, References]", specifications currently in progress.
 
In case of internet shut down, whether by disaster or voluntarily, peer networks are useful. [http://monal.im/blog/xmppsignalbluetoothp2p-wifi-serverless-chat/ Monal uses Airdrop] (wifi and bluetooth) along with XMPP and OMEMO end-to-end encryption.
 
[[File:https://framapic.org/Qg1mv43w1673/akPmtepp0nfH.png|Monal and Airdrop screenshots]]
 
JabberFr, the French XMPP/Jabber community, has again [https://news.jabberfr.org/2019/09/lettre-dactualite-xmpp-du-3-septembre-2019/ translated the XMPP newsletter in French], merci beaucoup.
 
For the poor lonesome techies, we wrote a very minimalistic [https://wiki.xmpp.org/web/Basic_communication_guide_for_XMPP_techies communication guide], could be worth for some.
 
=== Videos ===
 
=== Tutorials ===
 
=== Events ===
 
As usual every year, that time has come: we proudly announce the XMPP Summit 24 and the FOSDEM. The 24th XMPP Summit will happen on Thursday 30th and Friday 31st of January, and the FOSDEM will be held on Saturday 1st and Sunday 2nd of February. Prepare for the community gathering.
 
=== Software releases ===
         
==== Servers ====
 
Réda Housni Alaoui is reviving the formerly dormant [https://github.com/apache/mina-vysper Vysper XMPP server], please pronounce "whisper".
 
[https://blog.xabber.com/xabber-server-v-0-9-alpha-is-released/ Xabber Server v.0.9 alpha is released], with quick installation and management panel, and interesting innovations.
 
The Fastpath Service plugin has been released in versions [https://discourse.igniterealtime.org/t/fastpath-service-plugin-4-4-4-released/86155 4.4.4] and [https://discourse.igniterealtime.org/t/fastpath-service-plugin-4-4-5-released/86198 4.4.5]., bringing support for managed queued chat requests, such as a support team might use.
 
[https://www.erlang-solutions.com/resources/download.html MongooseIM 3.4.1 is out now] with and important security upgrade, fixing a vulnerability that increased the chance of a cluster node crash. [https://twitter.com/MongooseIM/status/1176111308430815232 Read the whole thread on Twitter] for more precise info.
 
==== Clients and applications ====
 
Profanity, the console/terminal app, has been released in [https://github.com/profanity-im/profanity/releases/tag/0.7.0 version 0.7.0] after five months of work, brining OMEMO end-to-end encryption, followed by a [https://github.com/profanity-im/profanity/releases/tag/0.7.1 0.7.1] bug fix release.
 
[https://gultsch.de/dino_multiple.html Multiple Vulnerabilities found in Dino], please update as soon as possible.
 
Converse, the web app for team chat, has been released in versions [https://github.com/conversejs/converse.js/releases/tag/v5.0.2 5.0.2] and [https://github.com/conversejs/converse.js/releases/tag/v5.0.3 5.0.3] fixing security issues among others. A [https://github.com/conversejs/converse.js-docker Converse Docker image] has been released by odajay, and Agayon has released a [https://blog.agayon.be/converse_xep_0070.html plugin to verify HTTP Requests via XMPP].
 
The Android chat app [https://github.com/siacs/Conversations/releases/tag/ Conversations has been released in version 2.5.8].
 
==== Libraries ====
 
=== Other ===
 
=== Services ===
 
[https://search.jabbercat.org/ Christopher Muclumbus], a listing and search engine of public XMPP/Jabber chat rooms/groups, has been updated with visual redesign, groupchats avatars, link to anonymous web chat if available, and software version pie chart.
 
=== GSoC ===
 
=== Extensions and specifications ===
 
This month, three proposed XEP, and two updated. No XEP in Last Call, New, or Obsoleted.
 
==== Last Call ====
 
==== New ====
 
==== Proposed ====
 
Message Fastening
 
Abstract:
This specification defines a way for payloads on a message to be marked as being logically fastened to a previous message.
 
URL: https://xmpp.org/extensions/inbox/fasten.html
 
 
XMPP Compliance Suites 2020
 
Abstract:
This document defines XMPP protocol compliance levels.
 
URL: https://xmpp.org/extensions/inbox/cs-2020.html
 
 
Authorization Tokens
 
Abstract:
This document defines an XMPP protocol extension for issuing authentication tokens to client applications and provides methods for managing сlient connections.
 
URL: https://xmpp.org/extensions/inbox/auth-tokens.html
 
==== Obsoleted ====
 
==== Updated ====
 
* Version 0.13.1 of XEP-0280 (Message Carbons) has been released. Changelog: Add clear example on problematic (spoofed) carbon messages and that they need to be handled. (gl). URL: https://xmpp.org/extensions/xep-0280.html
* Version 1.16.0 of XEP-0060 (Publish-Subscribe) has been released. Changelog:Add a pubsub#rsm disco#info feature to clear confusion (edhelas). URL: https://xmpp.org/extensions/xep-0060.html
 
==== Friendly specs ====
 
=== Thanks and CTA, Call To Action (remove this mention before publishing) ===


This XMPP Newsletter is a community collaborative effort. Thanks to Nÿco, Daniel, Jwi, and MDosch for aggregating the news. Thanks Nÿco and SouL for the copywriting.
=== Current newsletter ===


Please follow and relay the XMPP news on our Twitter account [https://twitter.com/xmpp @xmpp].
* [[XMPP Newsletter November 2019]]


=== License ===
=== Past newsletters ===


This newsletter is published under CC by-sa license: https://creativecommons.org/licenses/by-sa/4.0/
* Soon... [[XMPP Newsletter November 2019]]
* Soon... [[XMPP Newsletter December 2019]]

Revision as of 20:15, 10 October 2019

Here you can submit news items for inclusion in the next XMPP Newsletter (as managed by the CommTeam).


To contributors, editors, reviewers, translators

Live discussion

xmpp:commteam@muc.xmpp.org?join

What determines relevancy?

The submission must ideally be a blog or article about XMPP/Jabber and/or XMPP-based software (clients, servers, libs).

Some exceptions might be made, for example for a release page showing a new release of some XMPP-based software.

However, marketing brochures (e.g. single-page marketing sites) for new products which don't contain information on XMPP, won't be included.

Make sure you read the Basic communication guide for XMPP techies

Process

  1. Before: duration 1 month
    1. Collect links in this wiki page: duration 3-4 weeks
      • Read and validate the content
      • Include the reporters credits!
    2. Copywrite so each content is readable by humans: duration 2-3 days
      • Add links
      • Add images
      • Add CTAs
      • Carefully craft the subject/title line, and the preview text (first lines that are sometimes previewed on email UAs)
      • Include the copywriters credits!
    3. PR on website git repo for blog post (Markdown, Pelican): duration the week-end before posting
      • Need at least 2 or 3 peer reviews
      • Include the reviewers credits!
    4. Twitter:
      • Copywrite and review draft tweet: text, image, hashtags, link
  2. Sending the newsletter: on D-day
    1. Copy-paste Newsletter on Tinyletter, test it (peer review is not yet done), send it
    2. Report analytics from latest newsletter in spreadsheet, send to commTeam MUC
    3. PR merge and deploy on website git repo for blog post
    4. Twitter:
      • post draft tweet
      • Report monthly metrics
  3. Translations: after D-day
    1. Start the translations: publish before next newsletter :)
      • French: published on JabberFr.org and LinuxFr.org, working on Etherpad, need format ?
      • German: published on jabber.de, working on ?, need format ?
      • Spanish: published jabberes.org?, working on ?, need format ?
      • Polish: published ?, working on ?, need format ?
    2. LinkedIn (would be nice to get it back)
    3. Empty this page, keep structure for next newsletter

Planning

November

  • 2019-10-28 Mon: copywriting starts
  • 2019-11-01 Fri: end of link submission, PR on GitHub
  • 2019-11-05 Tue: newsletter publication, blog post, promotion tweets

Current newsletter

Past newsletters