[TriLUG] TriLUG wiki and infrastructure hack day.

[Jack Hill]

On Tue, 16 Apr 2013, Alan Porter wrote:

> I think one of our top requirements is that the wiki should have some
> sort of authentication / authorization... some wikis do this, while
> others are anonymous.  I had been looking for one that we could plug
> into our existing LDAP user database.

I agree, I think that restricting editing to TrilLUG members is reasonable 
and would be effective in stopping spam.

http basic auth can use the pam stack, so this is doable. I'm not familiar 
with pam_ldap (and haven't yet had a chance to look. Hey, we should 
document our configurations on the new wiki), in particular, what 
components need access to the hashed or cleartext password.

One of the future infrastructure improvement projects that I would like to 
see is an authentication scheme where any, untrusted, person could 
authenticate TriLUG users. Examples of schemes that could do this include 
Kerberos, OpenID, and BrowserID a.k.a Persona.

On the other hand maybe a centralized identity authority an antiquated 
idea and we should all be using something like monkeysphere.

> Closely related is that we need to be able to clean up graffiti.  Some
> wikis (like MediaWiki) insist on leaving all history intact, but just
> allow you to erase it from current view.  This is so they can claim that
> they are fully transparent.  The downside is that when you look at "all
> pages", you still end up seeing a ton of graffiti remnants.  Basically,
> it just gets cluttered up.
>
> I had been leaning towards Dokuwiki or Twiki (now called "FossWiki").

I haven't had the chance to work with those. I don't think ikiwiki allows 
for removing revisions from the history cleanly.

Best,
Jack