Difference between revisions of "XMPP Newsletter"

From XMPP WIKI
Jump to navigation Jump to search
Line 85: Line 85:
 
=== Metrics, statistics, analytics===
 
=== Metrics, statistics, analytics===
  
[[File:https://framapic.org/fg2QAKKv3yfy/JIVbhNNmyTF1.png|XMPP newsletter metrics November 2019]]
+
https://framapic.org/xfMLsqTjDylE/j50GPasvyCed.png

Revision as of 20:35, 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. 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

Metrics, statistics, analytics

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