Difference between revisions of "XMPP Newsletter"

Jump to navigation Jump to search
1,237 bytes added ,  20:15, 10 October 2019
(131 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.


== TODO/checklist ==
Make sure you read the [[Basic communication guide for XMPP techies]]
 
For the newsletter editors:
 
# Collect links in this wiki page, read and validate content, copywriting so it is readable by humans
# PR on website git repo for blog post (Markdown, Pelican), and peer review
# Newsletter
# Twitter scheduling: text, image, hashtags, link, timestamp
# Empty this page, keep structure
 
== Submissions for next newsletter==
 
=== Friendly, human introduction for the month (remove this mention before publishing) ===
 
=== Articles ===
 
=== Videos ===
 
=== Tutorials ===
 
=== Events ===
 
=== Software releases ===
         
==== Servers ====
 
==== Clients ====
 
https://github.com/profanity-im/profanity/releases/tag/0.7.0
 
==== Libraries ====
 
=== Other ===
 
=== Services ===


=== GSoC ===
=== Process ===


=== Extensions and specifications ===
# 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


==== Last Call ====
=== Planning ===


==== New ====
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


==== Obsoleted ====
=== Current newsletter ===


==== Updated ====
* [[XMPP Newsletter November 2019]]


==== Friendly specs ====
=== Past newsletters ===


=== CTA, Call To Action (remove this mention before publishing) ===
* Soon... [[XMPP Newsletter November 2019]]
* Soon... [[XMPP Newsletter December 2019]]
698

edits

Navigation menu