Re: The FreeBSD Handbook, in Wiki form.
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 pgpZe0jH1II8e.pgp Description: PGP signature
Re: The FreeBSD Handbook, in Wiki form.
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 <[EMAIL PROTECTED]> 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: The FreeBSD Handbook, in Wiki form.
Sure any public person can post junk to wiki and that is just what is wrong with it for official handbook. There would be no peer review of info for correctness. There is no single person who knows everything about FreeBSD and has time to review all the personal opinions posted to some wiki. And if you search this questions archives you will see that there is all ready an wiki for FreeBSD and it has very little activity. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Benjamin Keating Sent: Tuesday, May 03, 2005 8:29 PM To: Kris Kennaway Cc: freebsd-questions@freebsd.org Subject: Re: The FreeBSD Handbook, in Wiki form. 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 <[EMAIL PROTECTED]> 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
On 2005-05-03 17:29, Benjamin Keating <[EMAIL PROTECTED]> wrote: >On 5/3/05, Kris Kennaway <[EMAIL PROTECTED]> 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. > > A wiki would eliminate that bottle neck (PR). A wiki comes with its own set of problems though. It's not easy to mirror, its markup language is arbitrarily defined (as opposed to DocBook/SGML), it still requires constant review by a group of dedicated freebsd-doc people, etc. > 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. Useful comments can always posted to freebsd-doc for discussion. Helpful comments are not only those that contain patches, but also comments of the form: "This section sucks a bit. I can't really understand what the exact steps to rebuild my kernel are." > Things like that bring noise to this mailing list. It's ok. This is part of the purpose of having the list :) - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
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. > > A wiki would be a great way to acheive this. If there isn't a project > like it yet, I'd like to propose we set one up. I can contribute quite > a bit of time and resources towards this. Save me wiki.freebsd.org and > I'll get a move on! What about http://www.freebsdwiki.net? It needs a better home page and some content, but it's there. Besides, I completely agree with you that wiki-kind software must replace all pointless hand-editing and mail shuffling. -- Regards, Karel Miklav ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
On May 4, 2005, at 2:30 AM, Giorgos Keramidas wrote: On 2005-05-03 17:29, Benjamin Keating <[EMAIL PROTECTED]> wrote: Things like that bring noise to this mailing list. It's ok. This is part of the purpose of having the list :) You wouldn't think so from the flak some people have received for not googling for a "common problem" or searching through the mailing list archives...Or maybe I'm confusing this with another list? *shrug* oh well, it's only Wednesday :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
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. > > A wiki would be a great way to acheive this. If there isn't a project > like it yet, I'd like to propose we set one up. I can contribute quite > a bit of time and resources towards this. Save me wiki.freebsd.org and > I'll get a move on! What about http://www.freebsdwiki.net? It needs a better home page and some content, but it's there. Besides, I completely agree with you that wiki-kind software must replace all pointless hand-editing and mail shuffling. -- Regards, Karel Miklav I am a long-time FreeBSD user. I rarely consult the handbook because of the problems mentioned in this thread. A Wikipedia approach would be great but it would require constant attention by a dedicated group of people. A compromise approach could be to do what www.php.net does. On this site they have the official manual, which has the same flaws as the FBSD handbook (out of date pages, obtuse descriptions, ...). In addition, postings from users are attached to each page. These postings often contain information more pertinent to a particular query than the manual page itself. With this scheme, it is easy for a manual user to distinguish the "official" information from the information from general users. So one can apply the appropriate mental filters on the information. I am sure there is some monitoring and selection of posts by some responsible people. But the effort involved should be considerably less than that required for the Wikipedia model. dayton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
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 <[EMAIL PROTECTED]> 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@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Ryan Cavicchioni GPG ID: C271BCA8 GPG Public Key: http://confabulator.net/gpg/ryan.asc GPG Fingerprint: 83E4 2495 6194 0F66 ED85 22B4 4CC0 DA01 C271 BCA8 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
On 5/3/2005 at 5:29 PM 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! :) = When I found a spot in the Handbook that was a bit sparce, I send in an email describing what I was looking for, what I found, and what i expected to find. The Handbook was updated within a few days, and the update was much better than what I could have written. Maybe a wiki would supplement the Handbook, rather than replace it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
-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 <[EMAIL PROTECTED]> 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@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions To >> unsubscribe, send any mail to >> "[EMAIL PROTECTED]" >> > 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- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
On Wed, May 04, 2005 at 08:54:10AM -0400, [EMAIL PROTECTED] wrote: > A compromise approach could be to do what www.php.net does. On this site > they have the official manual, which has the same flaws as the FBSD handbook > (out of date pages, obtuse descriptions, ...). In addition, postings from > users are attached to each page. These postings often contain information > more pertinent to a particular query than the manual page itself. > > With this scheme, it is easy for a manual user to distinguish the "official" > information from the information from general users. So one can apply the > appropriate mental filters on the information. FWIW, enabling discussions like these on otherwise more tightly controlled pages is fairly trivial in Plone (http://plone.org/). If someone would like to set up a plone site with the handbook as content, and with enabled discussions, perhaps the official handbook pages could point to the inofficial pages which would also contain the discussions (links like: -> user discussions)? Wether linked to or not, the REAL problem here would be that the handbook gets updated now and then, and keeping the plone site (together with its discussions) in sync with the official handbook looks like a major time sink and will soon be abandoned eventually. > I am sure there is some monitoring and selection of posts by some > responsible people. But the effort involved should be considerably less > than that required for the Wikipedia model. > > dayton Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
On Wed, 04 May 2005 09:12:09 -0400 "MikeM" <[EMAIL PROTECTED]> wrote: > On 5/3/2005 at 5:29 PM 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! :) > = > > When I found a spot in the Handbook that was a bit sparce, I send in an > email describing what I was looking for, what I found, and what i expected > to find. The Handbook was updated within a few days, and the update was > much better than what I could have written. > > > Maybe a wiki would supplement the Handbook, rather than replace it. > There's some benefits to the present documentation approach that are being overlooked. It has a revision control system. This enables you to obtain a version of a handbook for any given date thru CVS. This magic is also what allows you to update your local documentation and use a minimum of bandwidth. It can produce output in a number of formats (HTML, PDF, PS, etc) from a single set of sources. Don't forget that the FreeBSD Handbook is also published occasionally from these same sources. The documentation is available in a variety of languages due to the efforts of the translation teams. They use the revision control system to determine when updated translations are needed. The documentation is available as part of the system and web access isn't required. It can also be freely distributed whereas I'm not sure who owns the content of a wiki. As others have mentioned, peer review is very important especially with documentation. The wording and syntax needs to be very clear since many users do not speak english as a first language. I'm probably overlooking some other aspects of the benefits but the present system does produce documentation that many consider to be the best of any comprable OS's. Granted, the centralized approach to documentation doesn't produce instant gratification that a wiki might but it seems to lend itself well for a variety of uses in a quality manner. In the end, its the content that is important and not the method. It probably doesn't take any more time on the part of a user to fill out a wiki-form than it takes to send-pr. There might be some niche that a wiki might be useful but I'd need to see a rough implementation showing how it addresses something that is lacking in the present method. There's always room for improvement. I just thought I'd throw a few things out for thought before we continue building the Big Bikeshed ;-) Randy -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
MikeM wrote: > On 5/3/2005 at 5:29 PM 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! :) = > > When I found a spot in the Handbook that was a bit sparce, I send > in an email describing what I was looking for, what I found, and > what i expected to find. The Handbook was updated within a few > days, and the update was much better than what I could have > written. > > > Maybe a wiki would supplement the Handbook, rather than replace it. > Now I think that would be a better idea. It would be cool to have a very active handbook wiki but just like forums, starting and running a successful one is not easy work. > > > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions To > unsubscribe, send any mail to > "[EMAIL PROTECTED]" > -- Ryan Cavicchioni GPG ID: C271BCA8 GPG Public Key: http://confabulator.net/gpg/ryan.asc GPG Fingerprint: 83E4 2495 6194 0F66 ED85 22B4 4CC0 DA01 C271 BCA8 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
Trevor Sullivan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 know it's off-topic, but I thought it might surprise some folks, and it's possible it could prove important to some, I guess. Notice the words above, about him using the sha-1 hash. You realize it's been broken? The crypto world is unambiguous about it, and firmly reocmmening that everyone immediately move over to using the sha256, which is already implemented on FreeBSD. Since it's already here, and hopefully possible (maybe) to modify your amil system to use it, I thought I would toss in the data here. If you would like (as I usually do) to read it from the hourses mouth, Bruce Schneier is the best authority around, and here's his take on it: http://http://www.schneier.com/blog/archives/2005/02/sha1_broken.htmlwww.schneier.com/blog/archives/2005/02/sha1_broken.html BTW, if you haven't bought his "Applied Cryptography", shame on you. He wrote this thing, and it alone tosses his name up against lights such as Richard Stevens, because he explains ALL of the horrible math, explains all of the algorithms in detail enouigh to program from, actually manages to make it entertaining, and I hope he lives forever. 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 <[EMAIL PROTECTED]> 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" 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- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
This is great! I'd love to contribute my mediawiki template and graphic design knowledge to spice it up a bit if you're interested. Either way, I'll be using / populating that thing with as much quality info as I can. Thanks! Are you in charge of this? - bpk On 5/4/05, Karel Miklav <[EMAIL PROTECTED]> wrote: > 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. > > > > A wiki would be a great way to acheive this. If there isn't a project > > like it yet, I'd like to propose we set one up. I can contribute quite > > a bit of time and resources towards this. Save me wiki.freebsd.org and > > I'll get a move on! > > What about http://www.freebsdwiki.net? It needs a better home page and > some content, but it's there. Besides, I completely agree with you that > wiki-kind software must replace all pointless hand-editing and mail > shuffling. > > -- > > Regards, > Karel Miklav > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
Benjamin Keating ([EMAIL PROTECTED]) [050504 10:00]: > 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. > A wiki would be a great way to acheive this. If there isn't a project > like it yet, I'd like to propose we set one up. I can contribute quite > a bit of time and resources towards this. Save me wiki.freebsd.org and > I'll get a move on! Seconded. I read it and wish for such a thing (rather than the bug-patch-wait-wait-wait cycle). Wish we'd had MediaWiki on hand for Mozilla 1.0 three years ago. - d. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
Karel Miklav ([EMAIL PROTECTED]) [050504 21:19]: > Benjamin Keating wrote: > > A wiki would be a great way to acheive this. If there isn't a project > > like it yet, I'd like to propose we set one up. I can contribute quite > > a bit of time and resources towards this. Save me wiki.freebsd.org and > > I'll get a move on! > What about http://www.freebsdwiki.net? It needs a better home page and > some content, but it's there. Besides, I completely agree with you that > wiki-kind software must replace all pointless hand-editing and mail > shuffling. If it fits in enough with what they want to do, it might be just the right place for a wiki-developed version of the Handbook. (The PR-patch-wait-wait-wait cycle really is incredibly painful and a frequently convincing reason to just not bother.) - d. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The FreeBSD Handbook, in Wiki form.
Benjamin Keating wrote:
> Either way, I'll be using / populating that thing with as much quality
> info as I can. Thanks! Are you in charge of this?
No, you should talk to the Jimbo guy ("Jimbo is a FreeBSD enthusiast /
professional / zealot, depending on who you ask, and is the maintainer
of this wiki.") For more information about him try your luck with 'whois
freebsdwiki.net'
--
Regards,
Karel Miklav
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
