[[mediawikiwiki:Manual:Interwiki|interwiki prefixes]] let you link between wikis. (That first link is an example of one, <tt><nowiki>[[mediawikiwiki:</nowiki>''Some link''</tt> generates an external link to an article on mediawiki.or. But the [http://techbase.kde.org/api.php?action=query&meta=siteinfo&siprop=interwikimap interwiki prefixes on techbase] have some problems:

+

[http://www.mediawiki.org/wiki/Manual:Interwiki interwiki prefixes]] let you link between wikis. But the [http://techbase.kde.org/api.php?action=query&meta=siteinfo&siprop=interwikimap interwiki prefixes on techbase] have some problems:

* It should be easy to link from one wiki to another, using [userbase:http://userbase.kde.org/Special:MyLanguage/Quick Start], but it isn't set up.

* It should be easy to link from one wiki to another, using [userbase:http://userbase.kde.org/Special:MyLanguage/Quick Start], but it isn't set up.

Line 44:

Line 44:

* There is a bug prefix, e.g. [[bug:1234|1234]], but why is it <tt>language="ᨅᨔ ᨕᨘᨁᨗ"</tt> attribute? Maybe that's why on userbase this doesn't do anything?

* There is a bug prefix, e.g. [[bug:1234|1234]], but why is it <tt>language="ᨅᨔ ᨕᨘᨁᨗ"</tt> attribute? Maybe that's why on userbase this doesn't do anything?

* Why is there an empty bugs prefix, e.g.[[bugs:1234|1234]] ?

* Why is there an empty bugs prefix, e.g.[[bugs:1234|1234]] ?

−

* 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]]; userbase has <nowiki>[[mediawikiwiki:</nowiki>, etc.!

=== Stylistic issues ===

=== Stylistic issues ===

Line 54:

Line 54:

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.

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

+

+

== Searching and browsing source ==

+

I brought back [[Getting Started#Browsing the code]] but the situation is confusing.

+

There are three systems that let you browse and search source code:

+

; http://projects.kde.org

+

: The git repositories, most KDE source code is in Git these days.

+

; http://api.kde.org

+

: API docs generated from the source code, but you can also scroll down and click to view the source code

+

; http://lxr.kde.org

+

: Cross-reference to files and names in the KDE source code.

+

+

But they give different results. Try searching for the class StrigiIndexWriter in 4.x ("the trunk"?) in each, or equivalently the file nepomukindexwriter.cpp

+

+

* [http://api.kde.org/mapsearcher.php?class=StrigiIndexWriter&module=ALL&version=4.x api.kde.org] finds the class in nepomukindexwriter.cpp in three different places!

* [http://lxr.kde.org/search?string=StrigiIndexWriter lxr.kde.org] finds the class in two different places, but with a completely different path:

+

*: [http://lxr.kde.org/source/kde/kdelibs/nepomuk-core/services/fileindexer/indexer/nepomukindexwriter.cpp in kdelibs/nepomuk-core in the directory services/fileindexer/indexer/]<br />[http://lxr.kde.org/source/kde/kde-runtime/nepomuk/services/fileindexer/indexer/nepomukindexwriter.cpp in kde-runtime/nepomuk in the same directory subtree]<br />

+

+

* Can't search for either in https://projects.kde.org/projects/kde/ or its subdirectories kdelibs and kdelibs/nepomuk-core. You can eventually browse to [https://projects.kde.org/projects/kde/kdelibs/nepomuk-core/repository/revisions/master/entry/services/fileindexer/indexer/nepomukindexwriter.cpp services / fileindexer / indexer / nepomukindexwriter.cpp] . This path in Git bears no relation to the path in api but matches the path in lxr. And projects and lxr agree on the file contents.

+

+

BUG: Ideally api.kde.org would generate a link to the actual file in Git.

+

+

== Nepomuk indexing mystery ==

+

I'm slogging through all this crap to try to figure out why Nepomuk isn't indexing my NTFS volumes. It could be something to do with "System Settings > Nepomuk/Strigi config > File indexing > Removable media handling > Ignore all removable media", but I can't find the glue that links this KCM with the actual indexing. I know this is in nepomuk/kcm/nepomukserverkcm.cpp (No thanks to the three search engines, I found it in Google), but searching for "RemovableMedia" doesn't find anything.

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 {{source}}, {{api}}, {{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:

Too many wikis!

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, common images, vandal patrolling), three copies of all these bugs, and for what? Users are three times more likely to look in the wrong wiki.

Techbase minor bugs

BUG: Template:Info is undocumented! Use <noinclude> </noinclude> to document what templates do!

techbase and userbase have different interwiki maps, e.g. techbase has no wikipedia prefix, but userbase does e.g. wikipedia:Git; userbase has [[mediawikiwiki:, etc.!

Stylistic issues

Don't capitalize each word in titles and section headings. It Makes the Wiki Look Imperious and Official, it conflicts with the default heading style (See the Toolbox links) and it makes linking to pages in the flow text flow unnatural to read. Compare

BUG: Ideally api.kde.org would generate a link to the actual file in Git.

Nepomuk indexing mystery

I'm slogging through all this crap to try to figure out why Nepomuk isn't indexing my NTFS volumes. It could be something to do with "System Settings > Nepomuk/Strigi config > File indexing > Removable media handling > Ignore all removable media", but I can't find the glue that links this KCM with the actual indexing. I know this is in nepomuk/kcm/nepomukserverkcm.cpp (No thanks to the three search engines, I found it in Google), but searching for "RemovableMedia" doesn't find anything.