(→Techbase problems and what I'm going to do about them: three wikis, are you f***ing kidding me?) |
(→Techbase problems and what I'm going to do about them: I brought back Getting_Started#Browsing_the_code) |
||
| Line 15: | Line 15: | ||
* BUG: doesn't say where the source is | * BUG: doesn't say where the source is | ||
* BUG: doesn't say where the API is | * BUG: doesn't say where the API is | ||
| − | * BUG: doesn't say what the service looks like. Is it a process I can look at? What's the process name | + | * BUG: doesn't say what the service looks like. Is it a process I can look at? What's the process name? |
* TODO: techbase needs to have {{tl|source}}, {{tl|api}}, {{tl|processname}} templates for creating links to these, and should have a series of form template that presents this sort of information about a project in an infobox: | * TODO: techbase needs to have {{tl|source}}, {{tl|api}}, {{tl|processname}} templates for creating links to these, and should have a series of form template that presents this sort of information about a project in an infobox: | ||
<nowiki>{{</nowiki>service| source= | api= | processname= | bugtracker= | kdemodule= | blog= }} | <nowiki>{{</nowiki>service| source= | api= | processname= | bugtracker= | kdemodule= | blog= }} | ||
| − | |||
| − | |||
| − | |||
| − | |||
=== Too many wikis! === | === Too many wikis! === | ||
| Line 51: | Line 47: | ||
* techbase and userbase have different interwiki maps, e.g. techbase has no wikipedia prefix, but userbase does e.g. [[wikipedia:Git]]?! | * techbase and userbase have different interwiki maps, e.g. techbase has no wikipedia prefix, but userbase does e.g. [[wikipedia:Git]]?! | ||
| − | ==== | + | === Stylistic issues === |
| + | * Don't Capitalize Headings. It Makes the Wiki Look Imperious and Official, and it makes linking to pages in text flow unpleasant. | ||
| + | |||
| + | === Layout issues === | ||
I think all these bugs are in the Chihuahua skin, and they all apply to userbase.kde.org as well. | I think all these bugs are in the Chihuahua skin, and they all apply to userbase.kde.org as well. | ||
| Line 67: | Line 66: | ||
=== TechBase problems fixed! === | === TechBase problems fixed! === | ||
| − | * fixed [[Template:Template]] to explain what it does | + | * I fixed [[Template:Template]] to explain what it does. |
| − | * pulled in [[Template:Tl]] from Wikipedia, so that instead of fiddling with <nowiki>{{</nowiki> you can use e.g. {{tl|bug}} to generate a nicely-formatted <nowiki>{{</nowiki>[[Template:bug|bug]]}} which is also a link to a template. | + | * I pulled in [[Template:Tl]] from Wikipedia, so that instead of fiddling with <nowiki>{{</nowiki> you can use e.g. {{tl|bug}} to generate a nicely-formatted <nowiki>{{</nowiki>[[Template:bug|bug]]}} which is also a link to a template. |
| + | * I revived a "Browsing the code" section in [[Getting_Started#Browsing_the_code|Getting Started]], it's critical! Someone deleted the old "Getting the source" section. | ||
I first used Projects/KDE_on_Windows but now run Kubuntu as my main operating system. I wrote an occasional journal of my adventures in getting Kubuntu working at userbase.kde.org user page
I mostly do documentation and support for Semantic MediaWiki, an extension to MediaWiki.
Contents |
2011-11-14: I'm frustrated as hell trying to figure out a problem with KDE (Strigi not indexing my stuff), and TechBase is not helping.
Some wiki woes also apply to userbase.
The Nepomuk blog's Documentation page has a Strigi Service link that goes to Development/Tutorials/Metadata/Nepomuk/StrigiService unfortunately this suffers from the same problems as the blog's Documentation page
KDE TechBase {{service| source= | api= | processname= | bugtracker= | kdemodule= | blog= }}
TODO: the split between userbase and techbase is dubious. I'm a user, but I want to go beyond the user documentation. You're just going to duplicate information like the processname, the blog, the bug tracker and the kdemodule in two wikis.
And it turns out there's a third wiki, http://community.kde.org. <rant>That is completely f***ing ridiculous.</rant> Three times the infrastructure to maintain (Help pages, templates, interwiki links, images, vandal patrolling), three copies of all these bugs, and for what? Users are three times more likely to look in the wrong wiki. Knock it off!
BUG: Template:Info is undocumented! Use <noinclude> </noinclude> to document what templates do!
BUG: Help:Contents says to use
<span class="bsBugLink bsError bsError-NoConnection"><span class="bsBugLink bsError bsError-NoConnection">{{bug|123456}}</span></span>
surely this HTML formatting junk should be part of a template, i.e. Template:Formatted bug
BUG: Template:Template has a silly confusing warning "If this page is not already in the "Template" namespace, it should probably be migrated to that location."
Instead, someone should just periodically look at WhatLinksHere/Template:Template and see if pages outside Category:Template are using it.
interwiki prefixes let you link between wikis. (That first link is an example of one, [[mediawikiwiki:Some link generates an external link to an article on mediawiki.or. But the interwiki prefixes on techbase have some problems:
I think all these bugs are in the Chihuahua skin, and they all apply to userbase.kde.org as well.
BUG: In three-column listings like , the techbase wiki skin makes the listing overlap the right-hand "Share your Knowledge" column.
BUG: In revision history the
crashes into the light header with [View the content page] [Discussion about the content page] icons.
BUG: justified text looks bad in a narrow window. Allow ragged right column
BUG: when you select, the highlight color makes highlighted text look identical to a link. Try it, select this text and link Schedules and this text. You can't tell!
MAYBE: pre text just goes on and on off the right side. Consider using the wrap attribute of pre so that stuff wraps.
