Yes, I am currently working on the 2.0 docs effort. The strategy is to follow the model set by 1.0 as closely as possible, while reusing and expanding on what's available in the current 2.0 documentation. This means using Sphinx and the same contribution model, etc. Most of the content will be ported from the old documentation and reorganized, and some new stuff will be added (like tutorials). In the meantime the current documentation, though rough around the edges, should cover everything and is updated with each release.
As far as contributing to the 2.0 docs, we currently don't have the full infrastructure set up yet. But we are very interested in hearing about errors, unclear sections, and general suggestions. I personally would like to know these issues so I can include fixes in the new docs 
. My suggestion would be to open issues on the Github tracker and use the Documentation label.