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

From XMPP WIKI
Jump to: navigation, search
(Events)
(Process)
 
(176 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.
  
== Submissions ==
+
Make sure you read the [[Basic communication guide for XMPP techies]]
 
+
=== Articles ===
+
 
+
 
+
https://blog.process-one.net/uniting-global-football-fans-with-an-xmpp-geocluster/
+
 
+
=== Videos ===
+
 
+
=== Tutorials ===
+
 
+
=== Events ===
+
 
+
https://bouah.net/2019/07/new-sprint-new-goodies/
+
 
+
https://wiki.xmpp.org/web/Sprints/2019_September_Stockholm
+
 
+
https://wiki.xmpp.org/web/Camp2019
+
 
+
https://wiki.xmpp.org/web/Meetups/Bavaria
+
 
+
=== Extensions and specifications ===
+
 
+
=== Software releases ===
+
         
+
==== Servers ====
+
 
+
https://github.com/horazont/prometheus-xmpp-blackbox-exporter (Announcement email https://mail.jabber.org/pipermail/operators/2019-July/003100.html ; docker images available --[[User:Jwi|Jwi]] ([[User talk:Jwi|talk]]) 14:55, 4 July 2019 (UTC))
+
 
+
 
+
https://discourse.igniterealtime.org/t/monitoring-service-1-8-0-and-inverse-4-2-0-1-plugins-released/85601
+
 
+
https://discourse.igniterealtime.org/t/smack-4-4-0-alpha2-released/85670
+
 
+
https://discourse.igniterealtime.org/t/openfire-4-4-1-release/85857
+
 
+
https://discourse.igniterealtime.org/t/thread-dump-1-0-0-plugin-released/85794
+
 
+
https://gitlab.com/nifker/xmpp-http-upload
+
 
+
https://blog.process-one.net/ejabberd-19-08/
+
 
+
https://www.goffi.org/b/XL5aGAa6wymUt4mAhnzGpm/pubsub-been-released
+
 
+
==== Clients ====
+
 
+
https://www.kaidan.im/2019/07/08/kaidan-0.4.0/
+
https://www.kaidan.im//2019/07/16/kaidan-0.4.1/
+
 
+
https://www.goffi.org/b/Gjm7Z5AUt4xh8gciV6wWSe/progress-note
+
 
+
 
+
Xabber 2.6.4(634)
+
WHAT'S NEW
+
 
+
+ Improved message archive synchronization
+
+ Greatly improved startup speed
+
+ Support of references in messages: files, forwards, markup (bold, italic, etc), mentions, quotes
+
+ Alert sound on receive and send messages in chat, that you can disable in settings
+
+ Image compression setting
+
+ Some visual changes
+
* Fixed avatars in notification
+
* Fixed some bugs and crashes
+
 
+
https://www.goffi.org/b/N29CuUQS4U4TK36JFuTQ5Q/salut-commune
+
 
+
https://nl.movim.eu/?post/pubsub.movim.eu/Movim/fd1921c6-219f-477b-a4be-ebb25e4cccc5
+
  
https://github.com/conversejs/converse.js/releases/tag/v5.0.0
+
=== Process ===
  
https://tigase.net/blog-entry/beagleim-32-and-siskin-im-52-released
+
# 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 ===
  
StanzaJS (formely known as Stanza.io) has been released in version 12 beta.
+
November
https://twitter.com/lancestout/status/1149743328323227648?s=03
+
* 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
  
https://github.com/strophe/strophejs/releases/tag/v1.3.4
+
=== Current newsletter ===
  
=== Other ===
+
* [[XMPP Newsletter November 2019]]
  
=== Services ===
+
=== Past newsletters ===
  
=== GSoC ===
+
* Soon... [[XMPP Newsletter November 2019]]
 +
* 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