A lot of these technical writers have github accounts, where presumably they contribute to open source projects in the form of documentation. Does anyone have any tips for attracting such people to a project?
I'm not sure how general my situation is, but in my case, a few friends were starting a company  and they had open sourced their log collector. Their initial team didn't have the writing skills / bandwidth to maintain great documentation , so they looked in their circle of friends to find a few people (including myself) with strong writing skills and a decent technical background (I work full time elsewhere).
The current workflow has developers writing the core / original documentation, which is then edited by more writing-centric people like myself (I edit heavily!).
One thing that might help, is to add the writer-friend as a committer to the project, even though he only writes documentation (this is the case for me). I think it helps with the obvious motivation issues, and also sends a message to the project at large that the project leadership deems documentation to be just as (or nearly as) important as the code itself!
 The CEO used to work for RedHat, which apparently treats documentation as a vital piece of their product. I remember him saying, "the documentation really is the face of a technical company".
Now we have some of the best NoSQL docs around (clearly there's still more to do). A nice side-effect of cleaner navigation is that PRs to our repo have increased dramatically.
However, we know that not everyone can make it. It's a conference about documentation, so documenting the talks just seems like a natural thing to do :) Hopefully it will be a good aid for others trying to write documentation, and serve as a resource for the good of the community in general.
If an organization is really serious about documentation, they will not only devote resources to writing it, they will also devote serious attention to a mechanism for figuring out where it needs improvement.
Come to think of it, this would be a decent metric for figuring out which big software companies to invest in, especially if you can detect the "uncanny valley" docs efficiently. (Not only equity, but in use of their SDK/APIs.) For small software companies, there may not be enough people to write docs at first.
It isn't so much about how to write documentation, but adding that section is something we want to do.
We also have a section currently linked to a couple of interesting projects: http://docs.writethedocs.org/en/latest/about/alternatives.ht...
We will also be announcing speakers as we get them confirmed throughout the following weeks. We know it's short notice, so we're trying to get the information out to people as quickly as we can.
The timing is a bit constrained because I am going to be hiking the Pacific Crest Trail from Mexico to Canada starting later in April: http://ericholscher.com/blog/2013/jan/10/walk-woods/
If my schedule permits I plan on attending.
I was expecting some advices like: "please be short when asking questions to conferencers", "no phone calls in conf rooms" and maybe even "please go to the leisure room tif you need to play Tetris", but I got a long thing about sexual harrassment: why? Is it so that each conf is a mine field haunted with sexual predators??
And I was planning a trip to the US in May ... this is less then perfect.
Decisions, decisions decisions.
Congrats on the book, it's a tenacious endeavor.