Re: lists of what Aaron thinks is important for the wiki Re: Idea for navigation

On Fri, 2 Apr 2004, David Ross wrote:

> > 3.  General names are natural seeds, they don't need any plunge ahead note, 
> > Once  a page like.. Media has become non-dense, then break it up into audio, 
> > video, and what not, to keep it navigateable. 
> I assume you are meaning the stub notice?  I think that it is quite 
> useful especially for new members who may feel reluctant to edit long 
> standing pages.

	I agree - the stub notice is useful.
> 
> > 4. the case sensitivity of wikipedia is unfortunate.  is there a work around?
> Yes - use the search feature before creating a new page.
> 
	I'd say that being case insensitive would be unfortunate.  When it 
comes to Linux case matters and I think the wiki should reflect that.

> > 5.What is on topic?
> >   talks about the current wiki, linux questions, and linux, and software that 
> > runs on linux are all ON TOPIC, and deserve to be MOVED if they are in a very 
> > inconvenient spot
> Where are they just now and where should they be moved to?  All linux 
> content is valid for posting on the wiki as long as it is not offensive 
> and does not enfringe on any copyright licencing.
> 
	Talks about the wiki itself are *not* on topic for the main 
namespace.

> > 2.  I am especially annoyed about bug reporting -- feature request links being 
> > removed.  Try going to kde.org and asking for a tiny feature that you'd like 
> > to see... and don't do it over their bugzilla software...
> Again - examples please.  We do have 2500 pages on the wiki.

	I think this was explained pretty well by Dysprosia on the talk 
page.

> > 2. Make protected pages be source readable!  I can't clone/ fork a page to 
> > show you guys what i mean, because I not only can't submit changes to it, I 
> > can't see the source to the page.
> I'm not sure if this functionality is already in MediaWiki but I'll look 
> into it.

	If I recall this will be in a future version of the software.

> > 2.
> > un-protect the main page, or do some work on it.  Specifically, it needs 
> > expanded info on how to use the wiki.  etiquite (sp), conflict resolution, 
> > etc.  I've looked over your pages, and I'm still stumbling across new 
> > formatting thingies.
> There is a talk page for "Main Page" - what do you think should be 
> added, the etiquet type documents are being worked on but these things 
> take time and this is a fairly new project and things are being dealt 
> with as they come up:
> http://wiki.linuxquestions.org/wiki/Talk:Main_Page

	...and http://wiki.linuxquestions.org/wiki/Section_Request
> 
> > 3.  backlinks are most usefull when they can be seen WITH the content, page 
> > flipping is nasty on web pages.

	Our implementation of backlinks is the "what links here" 
functionality.

> > 7.  Multiple navigation systems do not harm a wiki, the multiple navigation 
> > systems are the web,  I don't think of a cross referenced books as being much 
> > of a web.  

	The web should be the interlinking of documents, in the article 
text.

> > 8.  People VERY often enter the wiki  at where the search engine drops them, 
> > all pages need to serve as a minimal "table of contents" to the rest of the 
> > wiki.
> You can't really link to 2500 pages from each individual page.  Would it 
> not be more likely that people would use the "See also" section to see 
> related material or go to the main page to see the main categories?
> 
	If a person is searching for foo and get dropped on the [[foo]] 
page, there should be sufficient links to items related to foo in the foo 
article that to get them started browsing the wiki - and so the web is 
woven.

--jeremy