I was thinking.... several open source projects are beginning to use OpenOffice for the master copies of their documentation, then converting to whatever they want to deliver (like PDF). Would that make sense here? Or would it be too tedious to convert to SVG? OO has an SVG export, but it has some problems.
I think it makes sense to do it the way you described (OO -> SVG). My guess is that the SVG export problems that OO currently has will be resolved at some point (how soon though is questionable). There are definitely benefits to having the source/original documentation in a real word processor (OO of course) and then converting to SVG for use within inkscape.
I don't know that it's really wise of me to do this, but I will offer myself up to handle/maintain inkscape's documentation if there is currently no other individual doing so. Currently it appears that everyone chips in (although I may be dead wrong). As I've mentioned before, I'll be fairly useless on the programming side, and if there is a need in this area I'd be willing to step up to the plate. I'm mainly talking about the documentation w/in inkscape, however copying it to the wiki should be relatively simple and I'd be willing to do that as well. Please let me know if this would be helpful or if there is even a need for it or not. And if there is someone who already oversees the documentation, let me know who it is so I can offer up some help.
-Josh