[Kolab-devel] wiki as part of kolab

Markus Heller markus at relix.de
Tue Sep 6 15:04:22 CEST 2005


Hi Hamish,

> We use dokuwiki here, although I would not call it "integrated" we do use
> kolab for authentication, details here:
> http://wiki.kolab.org/index.php/Dokuwiki
> I agree that it will be nice to have this feature of a wiki integrated, and
> make some kind of kolab "portal". Ideally it would be a portal ala
> openXchange, with plugins for different things like wiki, forum, email etc.

I had a look at it and it looks nice to me. Concerning the strategy in this 
issue, at least with a little glimpse over the fence to Redmond Gardens, I 
see that they try to place Sharepoint Portal next to Exchange in order to 
offer integrated Portal / Groupware solutions to their customers. 

Perhaps we should think again a little, how we could integrate the various 
issues. To me it seems, that the web frontend topic is quite "hot". 

So the strategy might be to design the web services (I don't mean the computer 
sciences  Webservices trail) in a manner that they can 

a) be arranged neatly on a single Apache or

b) be separated out in the sense that they could be exported to and reused in 
a different portal solution. 

Very concisely I speak about features as offered by TWIKI modules:
- calendar (hey, we've got a really cool calendar in Kolab)
- filtered access to a wiki net (I don't think we should speak of a tree)


Imagine the sports or any other kind of club that has a kolab server for the 
internal communication. Let's say there is a unspecified "external/public" 
account that accepts assignments. The assignments are the events which the 
club organizes. And the manager-user can define who (individual board members 
etc) may register assignments/events for the public. 

But imagine, the club already has a website (which is the case very often). 
Then it is imaginable that the club would simply want to integrate the club 
calendar on its web site. 

There I would also see a requirement to create an automatic link between the 
assignment description and certain wiki pages. And I see a necessity to 
restrict the write access to certain kolab users, as there might be the rule 
that the company or club board would not want ordinary members to edit all 
the public information. 

Well so far about my ideas...Maybe you'll make use of them :-)

Best wishes,

Markus




More information about the devel mailing list