Difference between revisions of "XMPP Newsletter"

From XMPP WIKI
Jump to navigation Jump to search
(22 intermediate revisions by 2 users not shown)
Line 21: Line 21:
Make sure you read the [[Basic communication guide for XMPP techies]]
Make sure you read the [[Basic communication guide for XMPP techies]]


=== TODO/checklist/process ===
=== Process ===


For the newsletter editors:
# Before: duration 1 month
 
## Collect links in this wiki page: duration 3-4 weeks
# Collect links in this wiki page, read and validate the content // including the credits!
##* Read and validate the content
# Copywriting so each content is readable by humans // including the credits!
##* Include the reporters credits!
#* Add images
## Copywrite so each content is readable by humans: duration 2-3 days
#* Add clear CTA
##* Add links
#* Subject line and preview text
##* Add images
# PR on website git repo for blog post (Markdown, Pelican), and peer review
##* Add CTAs
# Analytics from latest newsletter in spreadsheet
##* Carefully craft the subject/title line, and the preview text (first lines that are sometimes previewed on email UAs)
# Newsletter via Tinyletter
##* Include the copywriters credits!
# Start the translations:
## PR on website git repo for blog post (Markdown, Pelican): duration the week-end before posting
#* French (JabberFr.org)
##* Include Pelican header
#* German (jabber.de?)
##* Change == in #
#* Spanish ()
##* Change links format
# Twitter:
##* Change images format
#* Posts scheduling: text, image, hashtags, link, timestamp
##* Need at least 2 or 3 peer reviews
#* Monthly metrics
##* Include the reviewers credits!
# LinkedIn (would be nice to get it back)
## Twitter:
# Empty this page, keep structure
##* 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: published on jabber.de, review see below
##* [[Spanish translation of the newsletter|Spanish]]: published jabber.de (looking for spanish publisher, evtl. suchat.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 ===


November
December
* 2019-10-28 Mon: copywriting starts
* 2019-11-25 Mon: copywriting starts
* 2019-11-01 Fri: end of link submission, PR on GitHub
* 2019-11-29 Fri: end of link submission, PR on GitHub
* 2019-11-05 Tue: newsletter publication, blog post, promotion tweets
* 2019-12-03 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) ]
 
*
 
=== Intro ===
 
Welcome to the XMPP newsletter...
 
New this month:
 
[CTA]
 
=== Articles ===
 
=== Videos ===
 
=== Tutorials ===
 
=== Events ===
 
=== Software releases ===
         
==== Servers ====
 
==== Clients and applications ====
 
==== Libraries ====
 
=== Other ===
 
=== Services ===
 
=== GSoC ===
 
=== Extensions and specifications ===
 
==== Last Call ====
 
==== New ====


==== Proposed ====
=== Current newsletter ===


==== Obsoleted ====
* [[XMPP Newsletter December 2019]]


==== Updated ====
=== Past newsletters ===


==== Friendly specs ====
* Soon... [[XMPP Newsletter November 2019]]
* Soon... [[XMPP Newsletter December 2019]]


=== Thanks and CTA, Call To Action (remove this mention before publishing) ===


This XMPP Newsletter is a community collaborative effort. Thanks to xxx for aggregating the news. Thanks to xxx for the copywriting. Thanks to xxx for the reviewing. Thanks to xxx for the translations.
=== Translations ===


Please follow and relay the XMPP news on our Twitter account [https://twitter.com/xmpp @xmpp].
[[German translations|German translations]]


=== License ===
=== Metrics, statistics, analytics===


This newsletter is published under CC by-sa license: https://creativecommons.org/licenses/by-sa/4.0/
[[File:https://framapic.org/fg2QAKKv3yfy/JIVbhNNmyTF1.png|XMPP newsletter metrics November 2019]]

Revision as of 07:55, 15 November 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
      • Include Pelican header
      • Change == in #
      • Change links format
      • Change images format
      • 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 translation of the newsletter: published on jabber.de, review see below
      • Spanish: published jabber.de (looking for spanish publisher, evtl. suchat.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

December

  • 2019-11-25 Mon: copywriting starts
  • 2019-11-29 Fri: end of link submission, PR on GitHub
  • 2019-12-03 Tue: newsletter publication, blog post, promotion tweets

Current newsletter

Past newsletters


Translations

German translations

Metrics, statistics, analytics

XMPP newsletter metrics November 2019