Difference between revisions of "XMPP Newsletter"
Jump to navigation
Jump to search
(142 intermediate revisions by 5 users not shown) | |||
Line 2: | Line 2: | ||
== 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 13: | Line 19: | ||
which don't contain information on XMPP, won't be included. | which don't contain information on XMPP, won't be included. | ||
Make sure you read the [[Basic communication guide for XMPP techies]] | |||
=== Process === | |||
# Before: duration 1 month | |||
## Collect links in this wiki page: duration 3-4 weeks | |||
##* Read and validate the content | |||
##* Include the reporters credits! | |||
## 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! | |||
## 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 === | |||
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 === | |||
* [[XMPP Newsletter November 2019]] | |||
=== Past newsletters === | |||
* 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
- Before: duration 1 month
- Collect links in this wiki page: duration 3-4 weeks
- Read and validate the content
- Include the reporters credits!
- 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!
- 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
- Collect links in this wiki page: duration 3-4 weeks
- 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 :)
- LinkedIn (would be nice to get it back)
- 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
- Soon... XMPP Newsletter November 2019
- Soon... XMPP Newsletter December 2019