[PBSD-docs] PC-BSD Documentation Project

[Gerard v. E. <gva...@gm...>]

Dear all,

 

Just to introduce myself, my name is Gerard van Essen and I'm now
responsible for the PC-BSD Documentation Project. I am Dutch, live in the UK
because I'm married to an English girl and have a little girl of 2 years.
Work wise, I'm not working for an IT company ;-) but for a mortgage bank.

 

As most of you will be aware, it has been fairly quiet on the PC-BSD
Documentation Project front. Thanks to Kris' hard work, PC-BSD has been
going from strength to strength, but the documentation has been lingering
behind. It's now time we put together some proper documentation for our
(future) users to make them "feel at home" quickly.

 

We need to concentrate on updating and adding to the Wiki and the FAQ's.
There's also the PC-BSD Quick Guide that Charles has worked on that needs
finishing. (http://www.auriance.com/docs/pcbsd/documentation/quick-guide/).
Plans are to ship this guide with PC-BSD when it is finished.

 

A few things that need to be done or need to be looked at are:

 

- Quick Guide:

As said above, this guide needs finishing. I think this is a priority, and
it would be great if we could ship this with v1.3

 

- FAQ

We need to add more questions/answers and update those that are out-of-date

Browse the PC-BSD forums and put often recurring (newbie) questions in the
FAQ

 

- Wiki:

Explain general Unix concepts (what Unix is, how does it defer from Linux,
user/wheel groups, su etc)

Explain related to KDE, i.e how to change your desktop background, how to
change the colour scheme, how to download and install stuff from
KDE-look.org

Check Wiki and update/correct where necessary.

Create some step-by-step tutorials (e.g. setting up a new printer using
cups, running windows software using Wine etc)

Creation of PBI 's

 

I'm sure there's still loads of other things that we could add, so if you
can think of any, just email me.

 

I'd like to create a roadmap for this project, so it would be great if you
could let me know how you'd like to contribute or what you're planning to
do. Doing it this way will avoid duplication.

 

Looking forward to working with you all.

 

Gerard

ge...@pc...