Hello. Please let me know if I'm using the wrong mailing list.
I am currently evaluating XWiki (along with several other wikis) for use within our small
development team. We will be sharing the wiki with clients as well, so we have several
criteria that MUST be met:
1. WYSIWYG editing
2. Clean interface, small learning curve
3. Fine-grained user access to pages
4. Security (the wiki will be on a server exposed to the internet, but will be private)
5. Good support base
In trying out XWiki Enterprise and looking through the documentation I think it meets
these requirements (definitely 1-3).
My questions are:
1. We will want to segregate the clients from each other (ie. they won't be aware of
each other), but our development team would need one-login access to all content, across
clients. ie. if a developer logs in, they would have access to all content; if client A
logs in, they would only see client A's content, etc. Am I understanding correctly
that with User Groups and proper ACL we could achieve this?
2. I'm trying to get an idea of the support base behind XWiki: does the support and
development rely on a small number of developers (or only one), or on a true community of
developers? I noticed the "XWiki Project Health" page is quite out of date
(only going up to Nov/07).
3. We do not currently have Java server experience; will XWiki be easy to
install/run/manage securely without exposing ourselves and our clients to risks out of
ignorance of the underlying technology? Is it inherently more secure than using PHP on an
Apache webserver (as I have read), or does it just come down to security awareness?
Any comments or additional information would be welcome. Excuse me if I have asked
questions that are readily available on the website -- I have looked through the online
documentation but have also evaluated many wikis and my eyes are starting to blur.
Thanks very much,
Trevor