: Looks like http://cwiki.apache.org/CWIKI/ answers all our
licensing questions.
: Notable:
See also this previous discussion in Lucene-Java, notably this
clarification from Doug...
http://www.nabble.com/Created%3A-%28LUCENE-805%29-New-Lucene-Demo-tf3234570.html#a9242876
If someone wants to investigate what it would take to switch to use
Confluence for the main site and/or the wiki i say great ... but it's
important to keep in mind that:
a) we need to be able to include "official" docs in releases
b) wiki pages editable by "anyone" can't be included in releases
...which means either we need two seperete wikis, or an easy way to
categorize pages as "official" vs "unofficial", let anyone edit/create
unofficial pages, let only commiteres edit/create official pages, allow
exporting of official pages. Depending on how it works, the interlinking
of official/unofficial pages could get somewhat confusing if they were all
powered by one system (having forrest vs moinmoin right now makes a really
clear line that would start getting blurred otherwise)
FWIW, at Krugle we started off using MoinMoin and switched to
Confluence. In general it's been a good change for us, especially as
the scale and scope of our wiki activity increased. And the
integration with Jira can be very handy.
As far as different classes of pages, the easiest way to do that
would be to create spaces (I assume that's possible w/the Confluence
config that Apache would set up), where each space can have different
access rights based on groups of users.
I had a quickly hacked app that I used to convert some of our
MoinMoin pages from their markup syntax to Confluence. If the switch
to Confluence happens, I can look around for it.
-- Ken
--
Ken Krugler
Krugle, Inc.
+1 530-210-6378
"If you can't find it, you can't fix it"
