Re: [OT] Euwiki
- Posted by Jason Gade <jaygade at y?hoo.?om> Jun 07, 2008
- 594 views
Jeremy Cowgar wrote: > Rywilly is the author of the wiki software so it's his choice. However, I'm > not too excited about a discussions tab. It makes it difficult to see the page > and discussion. Most successful wiki's I've ever used contain discussion at > the bottom of the page. > > Maintaining a successful wiki is actually hard work. When you have many > different > people contributing, everyone has their own idea of organization, > categorization, > etc... It's quite an art form. I would suggest that before we get too deep > into > loading up the new wiki, organizing, etc... that we look at a few well run > wikis. > Two really stick out to me: > > <a href="http://c2.com/cgi-bin/wiki">http://c2.com/cgi-bin/wiki</a> > <a > href="http://www.emacswiki.org/cgi-bin/wiki">http://www.emacswiki.org/cgi-bin/wiki</a> > > Those are three *highly* successful wikis. I would be interested if others > have > examples as well. I know someone will suggest wikipedia, but can I suggest we > cannot compare to them? They have a *huge* volunteer staff. We should look for > successful wiki examples that are maintained by very few people. > > A wiki can be a very helpful thing but can get out of control and become a > mess (spaghetti documentation > ) very quickly. Instead of figuring out > the right combination, let's borrow other peoples ideas. > > -- > Jeremy Cowgar > <a href="http://jeremy.cowgar.com">http://jeremy.cowgar.com</a> Yup, I've at least seen the c2 wiki before. It seems as though they put comments/questions/discussion at the bottom under a horizontal rule. Is that a style we want to adopt? Such as if I made a comment that the -lint option should be called -strict instead, or both, or whatever? Or should that stuff just stay in the development list? -- A complex system that works is invariably found to have evolved from a simple system that works. --John Gall's 15th law of Systemantics. "Premature optimization is the root of all evil in programming." --C.A.R. Hoare j.