Wiki

Wiki
Participants
Skills	Wiki
Status	Operational
Niche	Software
Purpose	Infrastructure
Tool	No
Location
Cost
Tool category

Wiki Property "Tool Image" (as page type) with input value "File:{{{Picture}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. {{{Picture}}} {{#if:No | [[Tool Owner::{{{ProjectParticipants}}} | }} {{#if:No | [[Tool Cost::{{{Cost}}} | }}

This page is about the very wiki you're currently reading. It can hold ideas, thoughts, discussions, and feature requests.

Tips

• To make an image-map (like on the Infra and 19" rack page) check out http://www.image-maps.com.

Feature requests

• http://www.mediawiki.org/wiki/Manual:$wgCapitalLinks
• Single sign-on for this wiki and future stuff
• Ajax support for space state
• Keep edits marked as 'minor edit' out of the RSS to reduce spam on IRC 'hideminor' => 1 in ~/includes/DefaultSettings.php
• Use http://www.mediawiki.org/wiki/Extension:Include to get rid of the iframe for the PingScan (ExternalData and converting the pingscan output to JSON could also work) and the homepage. The security risks can be controlled now that users can only be created in the LDAP and the use of the Include extension can be limited to certain URL's/domains in LocalSettings.php.
• Make spaceapi output available as XML as well to include it on the homepage with ExternalData.
• "Watch"-link on pages does nothing: pages don't appear on the Special:Watchlist. (it does work when you open the "watch" link in another tab/window)
• CSS tweaking so H2 (==) doesn't look bigger than H1 (=). Same for H3 vs H2.
• http://www.mediawiki.org/wiki/Extension:MsUpload for nice inplace uploads with drag&drop
• Remove the captcha, new users are impossibru now
• Lightbox for images instead of hyperlinks to the File: page

Todo

• SSL
• Migrate current users to LDAP (including password if possible and use LDAP for authentication from then on.
• Build a todo scraper to summarize all todo's on different pages
• Fix space status updates. It is now cached and will update on refresh (and possibly on other triggers???). It looks like it's impossible to turn off caching on a single page :<

Status

The wiki can read information from the LDAP through the External Data extension. This is in the LocalSettings.php:

#LDAP lookups
$edgLDAPServer['ldap.nurdspace.nl'] = "ldaps://ldap.nurdspace.nl/";
$edgLDAPBaseDN['ldap.nurdspace.nl'] = "dc=nurdspace,dc=lan";
$edgLDAPUser['ldap.nurdspace.nl'] = "cn=read-user,ou=systems,dc=nurdspace,dc=lan";
$edgLDAPPass['ldap.nurdspace.nl'] = "xxxxxxx";

You can list information from a single entry like so:

{{#get_ldap_data:
domain=ldap.nurdspace.nl
|filter=(uid=username)
|data=CommonName=cn
}}

{{#external_value:CommonName}}

Here "cn" is the name of the attribute in the LDAP for the entry where attribute "uid" has value "username". This gives the attribute the local variable name "CommonName" which is then displayed by the template.

Possible replacement of mediawiki

Some of us (Fwd,Niz) are annoyed by mediawiki and are looking for alternatives. Here is room for stuff like lists of things we want, descriptions of available alternatives etc. BTW: we are by no means bound to php/MySQL.

Features

Must have

• Api (for instance for irc bot)
• WYSIWYG editor (preferably seamlessly integrated in the front-end for logged-in users)
• Formatting of code (possibly with syntax highlighting)
• Easy upgrading (so no 12446 plugins that needs to be updated by hand)
• LDAP Integration both for authentication/autorization and for listing members
• Good cache control
• Simple method to obtain data from external sources (web services, API's, databases (partkeepr))
• Methods of structuring content via metadata (categories, tags, tree)
• Must not require a shitload of work for initial setup of the software
• Good documentation of the software used
• Templates to use as starting point for design
• Good security track record (no swiss cheese)
• wiki like syntax for linking pages together
• wiki like setup of document locations (like url/projectname/subpart )
• wiki like templates with forms

Would be nice

• Decent media management (centrally keeping track of uploaded files to avoid duplicates)
• Modular page building (start with empty page, insert text block, insert image block, insert query block with dynamic content, insert agenda block)
• Easy installation (webserver, database)
• (Preferably) easy way to code additional functionality where no standard extensions/modules exist.
• Blog functionality (but not only that, static pages in some sort of structure should be the main focus)
• Clean URLs

Approach

Let's pick a couple of CMS'es with potential (for example from this list) and install them in a VM to try out as many of the must-have-features as possible. If we find a suitable candidate we can look into content migration possibilities and proceed from there.