The FreeBSD Handbook, in Wiki form.

[Trevor Sullivan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Ryan J. Cavicchioni wrote:

> I would love to see a wiki for FreeBSD. I think that it would be
> really beneficial for the project. It would take some work to
> establish it but if there were enough participants, it could turn
> into a very robust documentation project. Some hard work would be
> required to make the wiki healthy and to police it but the spirit
> of a wiki is many users reviewing each other.
>
> Benjamin Keating wrote:
>
>> A wiki would eliminate that bottle neck (PR). Some parts are out
>> of date. Others fail to mention FAQ , etc. that could really
>> help. For instance, the NAT/DHCP articles could easily include a
>> 'typical home user' HOWTO rather then tricking the user into
>> reading that one line where it says you have to recompile your
>> kernel with IPFIREWALL support.
>>
>> Things like that bring noise to this mailing list. Idon't know
>> about you but I'd rather just add my new found info to the site
>> rather find a PR addy, submit it and wait for it to be added. We
>> have software that does this now. Lets use it! :)
>>
>> - bpk
>>
>> On 5/3/05, Kris Kennaway <kris at obsecurity.org> wrote:
>>
>>> On Tue, May 03, 2005 at 05:00:06PM -0700, Benjamin Keating
>>> wrote:
>>>
>>>> Is there anything being done to help keep the handbook just a
>>>> little more updated? It's a great handbook, if it's content
>>>> wasn't so out of date.
>>>
>>> What is out of date?
>>>
>>> Generally, if you want to improve something in the handbook,
>>> just submit a PR.
>>>
>>> Kris
>>>
>>>
>>>
>> _______________________________________________
>> freebsd-questions at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions To
>> unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe at freebsd.org"
>>
>
Wiki's in general are a great idea, I agree. However, you must still
consider that anyone can add to a wiki, and the content within could
become very cumbersome to maintain. It would (still) require the
FreeBSD development team considerable time to verify what is in it and
make sure that it isn't going to throw people off. For official
documentation, I would have to say that a wiki is not the best idea
(unless it is exclusively maintained by the FreeBSD team). Don't get
me wrong, wiki's are really cool, but if you want to get down to the
facts in official documentation, you can't allow it to get out of
hand. My 2 cents...any thoughts?  :-)

- -Trevor
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
 
iD8DBQFCeN/CoGycRpOgdeERAu0yAJ9nPTcBrW5unJyr4ljWd03t/+a2UgCdHnp0
7tT7lRLsLqHJnmMCZBtLOjU=
=BdIK
-----END PGP SIGNATURE-----