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.
Yes, this would be a great way to contribute; we definitely need improved documentation across the board. Documentation was very poor when we started, and fortunately it's gotten tons better since we started, but it's far from being where it needs to be.
Awesome, count me in then. Is there currently a main person that is overseeing the documentation, or do all the devs keep up on what's where? (in other areas it seems like you guys know who's doing what, but not necessarily where they are on it)
By documentation w/in inkscape do you mean the items in the Help menu such as the tutorials, or documentation within the inkscape code?
Note that there is also an Inkscape manual that some folks have worked on; this is separate from the tutorials in the Help menu, and
definitely
welcomes help.
Sorry I wasn't clear, I did mean the items in the help menu, not documentation within the code. I'm really wanting to help with user documentation, and it probably would have made more sense if I worded it that way originally.
And who should I talk with regarding the manual? (who's currently working on it?)
In general we don't copy documentation to wiki, but only because we
want
to only maintain one copy. If web-oriented versions of tutorials, manuals, etc. can be generated for the website, that sort of stuff is definitely valuable to have set up.
Good to know. If only there was real support for SVG within web browsers we'd be set on both ends (using the same files, minus interaction such as the shapes tutorial has). Given that I am now going to be involved with the documentation, I'll put some thought into the easiest way to generate the "help content" for the website. And once again, I think that if we have it all based in OO's writer format, it'll be more flexible to do such things.
-Josh