![]() |
Now serving 108 guides. |
|
Should BSDGuides become a Wiki?
There are 73 total votes. 15 Comments Posted by taulant on August 09, 2007 at 7:13:41 am PDT
It is better like this
Posted by dnperfors on August 10, 2007 at 7:33:13 am PDT
It would be easier to update articles with a Wiki than without. Of course the pages should be editable for members only ;)
Posted by X-Istence on August 30, 2007 at 12:03:24 pm PDT
No, it should not be a Wiki, that would destroy the site!
Posted by jogge on September 23, 2007 at 11:57:05 pm PDT
Its better this way.
Posted by leegold on October 16, 2007 at 5:30:21 pm PDT
I find WIKIs unintuitive. It's a fad that I hope will eventually go away.
Posted by taromaru on November 25, 2007 at 11:33:11 am PST
I'd like to see this site turn into a good example of wiki collaboration. Just like gentoo wiki. Otherwise, I agree with X-Istence. It will destroy the site
Posted by rhyous on April 25, 2008 at 2:04:47 pm PDT
Only if there is a great database that tracks who changed it and maintains the old version and allows you to restore the old version (like jive's community software does).
Posted by biniar on July 09, 2008 at 10:17:02 am PDT
To some extent I think it would help organize the guides if only they were on the wiki standalone.
Posted by pointer on August 08, 2008 at 1:10:43 pm PDT
wikis are good for some content sites, but it is not intended to be very friendly to tutorial/guide sites.
Posted by rkyrk on October 02, 2008 at 3:51:15 pm PDT
I'm with leegold. I hope wiki's just fade away.
Posted by Joupin on October 12, 2008 at 3:15:31 pm PDT
It should be
Posted by jackal on November 06, 2008 at 8:01:29 pm PST
I like wiki'es. I manage a couple of wiki sites myself. But still prefer bsdguides as it is.
Posted by PaulB on December 05, 2008 at 12:04:28 pm PST
It seems to me the only real difference between a wiki and what is there now is that wiki's are collaborative. Given the way things update frequently I think wikifying essential. Look at the success of wikipedia - wiki's are not going away. It's an excellent form for a knowledge base and it shares the editing burden. It doesn't mean the entire site has to be a wiki - but the current situation where you have to read through all the comments to make sure you didn't miss anything is more error prone.
So, my 2 cents... 1) limit editing to members 2) track changes 3) create an editing policy to guide people and worst-case, limit editing to "core/experienced" members. Posted by akoola on April 04, 2009 at 2:11:59 pm PDT
Creating policy for wiki contributions would be an good idea for begining,
Posted by RichAustin on November 10, 2010 at 2:56:54 am PST
It always seems to me that a good article, with corrections / additions at the end works best. I'm not a major fan of wiki's, but sensible amendments are of course a bonus. Overall, I have to say "keep it as it is - if it ain't broke, don't fix it!".
|
||||||||
Copyright 2003 - 2012 BSD Guides. All rights reserved. |
About | Terms of Use | Privacy | Contact |

