dblasby@anonymised.com wrote:
TOPP is likely getting a confluence license and setting up a machine to
run it.
Yeah!
I was thinking of moving the Geoserver wiki over to it. The codehaus
confluence (where its hosted currently) is kinda slow and I find it
difficult/frustrating to edit (or read) pages due to the lag. Hosting
it ourselves will speed this up and hopefully encourage people to
document.
We're more than willing to also put Geotools on it and, because
geoserver and geotools share a lot of documentation, it makes sense to
keep them together.
GeoAPI also has a wiki, but it is not seeing much love. However that community is picking up momentum now that it is doing something we care about. Before Martin seemed to do everything, I am very glad to see people pulling together and helping him out.
They may be uncomfortable in moving of the independent body that is codehaus. Or they may want to return to an maven build based website ...
I was think we should continue having JIRA and SVN on codehaus, and only
move the wikis over. The wiki's have an export/import command so this
shouldnt be an issue.
What do you think?
dave
ps. Jody -- you put udig on its own confluence so I'd like to hear your
experience.
It was the best thing ever, the poor sysadmin would not agree. But the other thing we tried (DRUPAL) was horrible, and the performance increase was great.
Asking them was straight forward, exporting the site from confluence as XML, and them importing it to the site was no problem.
Note in recent months the performance gain is minimal due to the number of cruise control builds - however it does indicate the community is active (go extended geotools community!)
There is one downside:
- upgrades are not pain free (of course they caused me pain at codehaus, witness the current geotools layout)
- including jira lists (like the one on the development page) should not be cached (to reflect reality), but that will slow things down alot when jira and confluence are not on the same machine.
Jody