On 08/02/16 14:55, Jason Morris wrote: > I, too, am a long-time user of JSPWiki on Tomcat. When transitioning to > Glassfish, I experienced many of the same problems you did. Other users have > raised the point that JSPWiki, from a corporate standards level, is > unsupported. That is, there is no "number" someone can call to get it fixed > when it breaks. > > > I have to ask: why the sudden concern about making JSPWiki into something > more than a good open-source wiki? Why the interest in pushing it as some > kind of corporate solution? My $0.02 from 20+ years in software is that this > will never happen as long as there is no single-source accountability for the > software. It works with OSS like LINUX because there are vendors like RedHat > that wrap it with a layer of added value in terms of support. It is such > value-add vendors that make OSS a viable option for commercial adoption by > minimizing the risk of adoption. > So, full circle: why is this an issue now at all?
The original question raised (not by me) on this same thread was "Open Discussion - How to [increase] JSPWiki publicity ..." (implying – correctly – there is a lack of publicity), and was asked way back April 2014. There were I think three responses, but no real discussion took place. It's not a new issue, more an actual discussion which didn't happen at the time. If there is less visibility for JSPWiki, there are less folks discovering and actively using it – leading to problems which you've experienced with folks using it on alternate app servers, for instance. If you look at other healthy open source projects, specifically alternative wiki products such as MediaWiki, they have a level of publicity absent in JSPWiki. The target audience isn't folks like you and me who have been using it for years, it's those prospective users who simply don't know about it. Note what's missing from https://en.wikipedia.org/wiki/Comparison_of_wiki_software for example. In terms of "pushing as a corporate solution", I'm not pushing for anything as such, other than greater visibility. Corporate deployment is just one highly-applicable use case in which JSPWiki can (with the right requirements) compete. I run an open source consultancy, and I would just *love* to be able to offer JSPWiki as a commercial hosted service for small-medium-sized businesses, and be able to contribute back to the project with tangible resources. Absent that – due to some lingering problems with HADDOCK and the drawbacks with the legacy interface – contributing some free time to raising publicity is the next best thing I can offer. I really like JSPWiki's strengths (ease of setup, mostly ease of use, streamlined and no bloat, no separate database to manage, open source, and so on), but if a slide into obscurity is on the horizon, I'll switch to another product. Cheers, Dave -- Dave Koelmeyer http://blog.davekoelmeyer.co.nz GPG Key ID: 0x238BFF87
