At the Moment i edit and write the Documentation alone and this is is for one Person a lot. So i need 2 more guys, who are willing to help writing the Documentation.

If someone wanted to help, please PM me or post here.

But note: i'm looking for people where helps longer then one Week

I would like help you a bit. But not fulltime. Im mainly a dev Although you havent seen much of my work yet

Hi gOOvER , I think I can help you, just tell me how

Yes, i can also help...not that full time but i can help

Greez BeNe

Hi gOOver, i´ve send you our old vhcs documentation.
I will make some new screenshots if you want

The content in the main parts should be the same.

xister Wrote:I will make some new screenshots if you want

That's i good idea. But first we should take a look at the Server. I think gdlib don't work correct.

I can carry out English documentation review, check spellings and grammar and ensure that content actually make sense and is easy to follow. I guess this role falls under Quality Control rather than Documentation Team?

That's a very good idea, BioALIEN.

Ok, i think it's time to start first of all we should start with the Userguide. Everybody where is willing to help, please tell me, which Part he wants to make.

I am in the process of doing a installation on Ubuntu Hardy Heron. I have copied the Debian installation notes into my wiki and am documenting what needs to be done different for Ubuntu. Will happily paste this back up once i have a successful installation and document every step along the way.

Hopefully this would be helpful for someone.
Also have another server running vhcs2.4.1 i believe which i will migrate as soon as i have this one online, i will also document that process if anything goes awry and post that back up.

Great job guys. love the work. I can try to help out a bit on the documentation side, perhaps keeping some of it up to date? i already work waaay more than fulltime but if i see something obviously wrong im happy to at least make corrections.
Tnt