Difference between revisions of "News and Articles for the next XMPP Newsletter"

From XMPP WIKI
Jump to: navigation, search
(Articles)
(Process)
 
(323 intermediate revisions by 13 users not shown)
Line 1: Line 1:
Here you can submit news items for inclusion in the next XMPP Newsletter (as managed by the [[CommTeam]]).
+
Here you can submit news items for inclusion in the next [https://xmpp.org/category/newsletter.html XMPP Newsletter] (as managed by the [[CommTeam]]).
  
  
== 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.
  
== Submissions ==
+
Make sure you read the [[Basic communication guide for XMPP techies]]
 
+
=== Articles ===
+
 
+
A look at the XMPP chat app being developed for the Purism mobile phone https://puri.sm/posts/librem5-progress-report-19/
+
 
+
QR Code generator for OMEMO https://blog.jabberhead.tk/2018/11/03/qr-code-generator-for-omemo/
+
 
+
Dutch article about IronChat, XMPP/OTR app (apparently a fork of Conversations) with centralized server used by criminals. The server was hacked and they MITM'd the messages. Lots of people arrested.
+
https://nos.nl/artikel/2258309-beveiliging-door-politie-gekraakte-cryptofoons-was-twijfelachtig.html
+
 
+
https://www.kuketz-blog.de/messenger-xmpp-ist-nicht-der-heilsbringer-aber-eine-loesung/
+
 
+
https://mailbox.org/en/post/a-new-logo-a-new-website-new-software-versions-and-new-features-at-mailbox-org
+
 
+
https://www.golem.de/news/quicksy-mit-der-telefonnummer-ins-jabber-netz-1811-137855.html
+
 
+
https://starbeamrainbowlabs.com/blog/article.php?article=posts/327-Write-an-XMPP-bot-in-half-an-hour.html
+
 
+
=== Videos ===
+
 
+
=== Tutorials ===
+
 
+
 
+
 
+
=== Events ===
+
 
+
https://xmpp.org/2018/11/xmpp-summit-23/
+
 
+
=== Extensions and specifications ===
+
 
+
=== Software releases ===
+
         
+
==== Servers ====
+
 
+
https://blog.prosody.im/prosody-0-11-0-released/
+
 
+
==== Clients ====
+
 
+
https://dev.gajim.org/gajim/gajim/blob/gajim-1.1.0/ChangeLog
+
 
+
https://github.com/credija/opa
+
 
+
https://twitter.com/iNPUTmice/status/1062868073072484352
+
  
https://github.com/conversejs/converse.js/releases/tag/v4.0.5
+
=== Process ===
  
New Yaxim version 0.9.3 https://yaxim.org/download/ (FDroid or Google play)
+
# 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
  
==== Libraries ====
+
=== Planning ===
  
https://github.com/strophe/strophejs/releases/tag/v1.3.1
+
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
  
=== Other ===
+
=== Current newsletter ===
  
https://nl.movim.eu/?node/pubsub.movim.eu/Movim/movim-0-14-scotty-anniversary-edition-J8qk3N
+
* [[XMPP Newsletter November 2019]]
  
=== Services ===
+
=== Past newsletters ===
  
jonas’> Seve, I’d like to append that the [Public Chat Room search Muclumbus](https://search.jabber.network/) now lives on the search.jabber.network domain and has seen some minor extensions, such as [software 
+
* Soon... [[XMPP Newsletter November 2019]]
        version and service type statistics](https://search.jabber.network/stats)
+
* Soon... [[XMPP Newsletter December 2019]]

Latest 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

  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
      • 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: published on jabber.de, working on ?, need format ?
      • Spanish: published jabberes.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

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