add info about development branches and link it.

please verify and tell if there is more that should be linked ...

doc/contact.rst

@@ -19,11 +19,13 @@ you may:
 .. _`github Autocrypt repo`: https://github.com/autocrypt/autocrypt
 
 
+See :doc:`dev-status` for links to ongoing development.
 Currently involved are developers from `K9/Android`_,
 `OpenKeyChain/Android`_, `Enigmail`_, `Mailpile`_, `Bitmask/LEAP`_ as
 well as people from the `nextleap`_, `enzevalos`_ research projects
 and the ACLU_.
 
+
 .. _`ACLU`: https://www.aclu.org/
 .. _`K9/Android`: https://k9mail.github.io/
 .. _`Enigmail`: https://enigmail.net/

doc/contents.rst

@@ -22,6 +22,10 @@ and contributors, MUA developers and privacy enthusiasts.
      Minimum requirements and implementer guidance for Level 0
      Autocrypt-capable MUAs.
 
+:doc:`MUA development branches <dev-status>`
+     a first collection of current autocrypt developments (Jan 2017) with
+     various mail programs.
+
 :doc:`other-crypto-interop`
      Guidance for integrating Autocrypt with other e-mail encryption
      mechanisms and UI for existing MUAs.
@@ -46,6 +50,7 @@ and contributors, MUA developers and privacy enthusiasts.
    contact
    examples
    level0
+   dev-status
    address-canonicalization
    ecosystem-dangers
    other-crypto-interop

doc/dev-status.rst

@@ -0,0 +1,21 @@
+
+Mail Program Autocrypt Development Branches
+-------------------------------------------
+
+Last updated: 17th January 2017
+
+Enigmail: `Enigmail autocrypt branch <https://sourceforge.net/p/enigmail/source/ci/master/tree/>`_
+
+Android K9: `K9 autocrypt branch <https://github.com/k9mail/k-9/commits/trust-id>`_
+
+Mailpile: XXX to-be-filled-in
+
+Notmuch/Alot: XXX to-be-filled-in
+
+Bitmask/LEAP: `ongoing refactorings <https://0xacab.org/leap/bitmask-dev/merge_requests/55/diffs>`_
+
+Python: `Python Autocrypt Bot <https://github.com/autocrypt/autocrypt>`_
+
+Go: `Go Autocrypt <https://github.com/autocrypt/go-autocrypt>`_
+
+**Please-fill-in-your-development-branch here**