Merge branch 'ns/readme-status' into next

CONTRIBUTING.rst

@@ -27,6 +27,15 @@ contributions.
 .. contents:: :depth: 3
 
 
+Submit issues
+=============
+
+Issues are welcome to both Github_ and the `mailing list`_, at your own
+convenience.
+
+You might help closing some issues, too. :-)
+
+
 For the imaptients
 ==================
 
@@ -36,13 +45,6 @@ For the imaptients
 - All the `documentation`_
 
 
-Submit issues
-=============
-
-Issues are welcome to both Github_ and the `mailing list`_, at your own
-convenience.
-
-
 Community
 =========
 

README.md

@@ -1,6 +1,7 @@
-[offlineimap]: https://github.com/OfflineIMAP/offlineimap
+[offlineimap]: http://github.com/OfflineIMAP/offlineimap
 [website]: http://offlineimap.org
 [wiki]: http://github.com/OfflineIMAP/offlineimap/wiki
+[blog]: http://offlineimap.org/posts.html
 
 # OfflineIMAP
 
@@ -32,6 +33,26 @@ GNU General Public License v2.
 * It is **safe**.
 
 
+## Project status and future
+
+> As one of the maintainer of OfflineIMAP, I'd like to put my efforts into
+> [imapfw](http://github.com/OfflineIMAP/imapfw). **imapfw** is a software in
+> development that I intend to replace OfflineIMAP in the long term.
+>
+> That's why I'm not going to do development in OfflineIMAP. I continue to do
+> the minimal maintenance job in OfflineIMAP: fixing small bugs, (quick)
+> reviewing/merging patches and rolling out new releases, but that's all.
+>
+> While I keep tracking issues for OfflineIMAP, you should not expect support
+> from me anymore.
+>
+> You won't be left at the side. OfflineIMAP's community is large enough so that
+> you'll find people for most of your issues.
+>
+> Get news from the [blog][blog].
+>
+>                                  Nicolas Sebrecht. ,-)
+
 ## Downloads
 
 You should first check if your distribution already packages OfflineIMAP for you.