Difference between revisions of "XMPP Newsletter"

From XMPP WIKI
Jump to: navigation, search
(Clients)
(Process)
 
(125 intermediate revisions by 5 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: TODO/checklist ==
+
=== Process ===
 
+
For the newsletter editors:
+
 
+
# Collect links in this wiki page, read and validate content
+
# Copywriting so it is readable by humans
+
# Add images
+
# Add clear CTA
+
# Subject line and preview text
+
# PR on website git repo for blog post (Markdown, Pelican), and peer review
+
# Analytics from latest newsletter in spreadsheet
+
# Newsletter via Tinyletter
+
# [[Twitter scheduling]]: text, image, hashtags, link, timestamp
+
# Empty this page, keep structure
+
 
+
== Submissions for next newsletter==
+
 
+
=== Newsletter subject ===
+
 
+
=== Friendly, human introduction for the month (remove this mention before publishing) ===
+
 
+
Be kind, inform your friends and colleagues: forward this newsletter!
+
 
+
=== Articles ===
+
 
+
* https://wiki.xmpp.org/web/Basic_communication_guide_for_XMPP_techies
+
* https://ralphm.net/blog/2019/09/09/fastening
+
* [https://gultsch.de/dino_multiple.html Multiple Vulnerabilities found in Dino]
+
 
+
=== Videos ===
+
 
+
=== Tutorials ===
+
 
+
=== Events ===
+
 
+
Summit 24 and FOSDEM, Brussels, Belgium
+
 
+
=== Software releases ===
+
         
+
==== Servers ====
+
 
+
Réda Housni Alaoui is reviving the formerly dormant Vysper XMPP server
+
https://github.com/apache/mina-vysper
+
 
+
Watching: To be included if source code released: https://github.com/redsolution/xabber-server
+
 
+
https://github.com/esl/MongooseIM/releases/tag/3.4.1
+
 
+
==== Clients ====
+
 
+
* https://github.com/profanity-im/profanity/releases/tag/0.7.0
+
* http://monal.im/blog/xmppsignalbluetoothp2p-wifi-serverless-chat/
+
* https://github.com/conversejs/converse.js/releases/tag/v5.0.2
+
* https://github.com/conversejs/converse.js/releases/tag/v5.0.3
+
* https://github.com/siacs/Conversations/releases/tag/2.5.8
+
 
+
==== Libraries ====
+
 
+
=== Other ===
+
 
+
=== Services ===
+
 
+
=== GSoC ===
+
 
+
=== Extensions and specifications ===
+
 
+
==== 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
+
  
 +
# Link collection: duration 1 month
 +
#* Read and validate the content
 +
#* Include the reporters credits!
 +
# Copywrite so each content is readable by humans: duration 1 week
 +
#* 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!
 +
# PR on website git repo for blog post (Markdown, Pelican): duration the week-end before posting
 +
#* Include Pelican header
 +
#* Change == in #
 +
#* Change links format
 +
#* Change images format
 +
#* Need at least 2 or 3 peer reviews
 +
#* Include the reviewers credits!
 +
# Sending the newsletter: on D-day
 +
## Copy-paste Newsletter on Tinyletter
 +
## Test it (peer review is not yet done)
 +
## Send it
 +
# Blog post: PR merge and deploy on website git repo on D-day
 +
# Social media posts
 +
#* text
 +
#* image
 +
#* hashtags
 +
#* link
 +
# Metrics/analytics in CommTeam MUC
 +
#* Twitter monthly metrics
 +
#* Newsletter analytics
 +
# Propose schedule for next issue
 +
# Translations: after D-day
  
XMPP Compliance Suites 2020
+
=== Planning ===
  
Abstract:
+
January:  
This document defines XMPP protocol compliance levels.
+
  
URL: https://xmpp.org/extensions/inbox/cs-2020.html
+
* 2020-01-30 Mon: copywriting starts
 +
* 2020-01-03 Fri: end of link submission, PR on GitHub
 +
* 2020-01-07 Tue: newsletter publication, blog post, promotion tweets
  
 +
=== Current newsletter ===
  
Authorization Tokens
+
* [[XMPP Newsletter January 2020]]
 +
* [[XMPP Newsletter template]]
  
Abstract:
+
=== Past newsletters ===
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
+
* [[XMPP Newsletter November 2019]]
 +
* [[XMPP Newsletter December 2019]]
  
==== Obsoleted ====
+
=== Translations ===
  
==== Updated ====
+
* [[German translations|German translations]]
 +
* [[French translations|French translations]]
 +
* [[Spanish translations|Spanish translations]]
 +
* [[Polish translations|Polish translations]]
  
==== Friendly specs ====
+
=== Metrics, statistics, analytics===
  
=== CTA, Call To Action (remove this mention before publishing) ===
+
https://framapic.org/xfMLsqTjDylE/j50GPasvyCed.png

Latest revision as of 20:51, 3 December 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. Link collection: duration 1 month
    • Read and validate the content
    • Include the reporters credits!
  2. Copywrite so each content is readable by humans: duration 1 week
    • 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
    • Include Pelican header
    • Change == in #
    • Change links format
    • Change images format
    • Need at least 2 or 3 peer reviews
    • Include the reviewers credits!
  4. Sending the newsletter: on D-day
    1. Copy-paste Newsletter on Tinyletter
    2. Test it (peer review is not yet done)
    3. Send it
  5. Blog post: PR merge and deploy on website git repo on D-day
  6. Social media posts
    • text
    • image
    • hashtags
    • link
  7. Metrics/analytics in CommTeam MUC
    • Twitter monthly metrics
    • Newsletter analytics
  8. Propose schedule for next issue
  9. Translations: after D-day

Planning

January:

  • 2020-01-30 Mon: copywriting starts
  • 2020-01-03 Fri: end of link submission, PR on GitHub
  • 2020-01-07 Tue: newsletter publication, blog post, promotion tweets

Current newsletter

Past newsletters

Translations

Metrics, statistics, analytics

https://framapic.org/xfMLsqTjDylE/j50GPasvyCed.png