Chris Holmes ha scritto: >> Ho hum, >> I don't know what the others think, I can give you just my motivations >> on why I provided my +1. >> >> First off, I keep on loosing my edits when I work with wiki. Edit, >> preview, >> back, forward, boom! And my edit is lost (ok, that's my fault, I'm too >> in a hurry when I write docs...). > Have you tried to 'resume editing'? Confluence actually asynchronously > saves, and if you edit something that you've edited before and lost it > will often have it there.
Hum... no. I just got so upset with confluence that I use it only when I'm forced to :-) I can try a little harder thought. >> Second, I usually can't find anything on the confluence site. Even with >> Hibernate, that has a easier to work with documentation, I usually get >> the "one html page" documentation and then use a lot Firefox search >> capabilities. > I agree a one html page could be nice. I'll try to look in to doing > that with confluence. I know you could do it in a way that would be > annoying to maintain, just write out includes for all pages. It'd be > nice if one could fully automate. Confluence allows for plugins, but having them installed on codehaus is a little hard I guess... >> >> Thrid, wiki is not versioned along with the code, and I'd like it to be >> so. Go to: http://docs.codehaus.org/display/GEOSDOC/Documentation >> Where's the documentation for Geoserver 1.0? > Each version is exported at the release and available for download. So if someone improves the docs online you'll have to wait the next major release to see them? You can't have a "stable branch" for docs as with the code, can you? I'm wondering if it would be possible to perform a "deep" copy of the docs... but then again without a version control applying changes to both branch and trunk would be tedious. > I'm actually ok with it, I don't personally have strong feelings, except > to point at the history, which says that we got much more documentation > when we switched to wiki. I slightly fear us just going around in > circles, when in another couple years someone goes from docbook back to > wiki... Hmm... I have a feeling the wiki worked where people contributed only fixes/improvements inside the pages, but not when full new content was provided. The developers guide is an example that worked, because not many people worked on it, the tutorial section is confusing on the contrary. > I would fight more for GeoServer, as I really like that people > can edit the wiki, but for geotools one could argue programmers know how > to work subversion (though I know I personally added more docs when I > could just write wysiwyg to the wiki). There's another point I forgot to state: for long days confluence on codehaus has been totally unusable due to slow (very slow) response and various problems with my ISP proxies (I remember I asked Jody to perform a few edits because I could not, AJAX used in the confluence pages was not working at all). Cheers Andrea ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
