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

> > > 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.

Good point about linux being case sensitive, but.. how many commands are 
different by one capitalization?

not very many

The unfortunate part of the wikipedia case sensitivity is that the first 
letter's capitalization doesn't matter.

When I learned of this by reading a description of a change, my jaw dropped...   
So that's why we have such wierd titles and strange capitalization of wiki 
names all over the place...

Software Development    is a title
Software development    is the start of a sentence
software development    is more easily forgiven (in my own questioning of my 
opinion)  It's also easier to do.

So, I am going to write wikilinks as lowercase unless I know otherwise..

>
> 	Talks about the wiki itself are *not* on topic for the main
> namespace.
There is no namespace for all i can tell, just an awkward convention... I made 
a few suggestions on how to make the convention a bit better, but.. we are 
having overlapping conversations.... a nice IRC chat would clear this all up 
and we could post the history to the mailing list...


>
> > > 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.

And I think I have a very valid argument as to the way i made it.  

That was a deletion.. a time waster...  one of the things that if dysprosia 
doesn't like it, he should wait a bit before doing some deletions.. deletions 
are just So easy to do... it's scary how quickly things can get deleted.

>
> > > 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.
Horray, a wiki where the wiki gets upgraded!!

>
> > > 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
... that is just sitting there...
A nice way to do a main page upgrade, is to copy the  main page, make that be 
a protected page  [[main page backup]]  and let people hack around.   A link 
to a prototype page, [[sandbox:new main page]]  would be made, so that people 
can test experimental updates on it.


>
> > > 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.

i explain why backlinks >> what links here in in the document that i sent 
before this. oh.. right there above this...  Try using a what links here 
button on a wiki that you are unfamiliar with,  vs a backlinks page on one 
that you are unfamiliar with...  
>
> > > 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.

i covered the different types, and the real estate argument applies

> 	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.

Yes, there _should_ be.


-- 
509 332 7697
ICQ 2302806