>>So, full circle: why is this an issue now at all?
I guess because I asked “who is JSPWiki for ?” I believe this is the most important challenge facing JSPWiki. Not having a clear understanding of this question poses the greatest risk to it. I see this as a strategic marketing issue, not one simply of publicity. It would be interesting to know what the person managing the development of JSPWiki thinks is the answer to this. Where is it heading? Is there a vision? “2.10.2” is not the answer I'm looking for. It is difficult to steer development towards an uncertain goal. There is tough competition all around, so is there some unique selling point that we can exploit? I think that there is. Several actually. There are niche market segments that JSPWiki could move into very successfully. Although without a clear focus, I fear that this project might stall somewhat. I certainly don't expect it to compete effectively in the mainstream market for reasons already highlighted. If consensus is that this is a hobby, then fine. Have at it. But I'm reminded of Thackeray's *“Whatever you are, try to be a good one.”* If there is a desire to see this product become a larger player, there are clear strategic marketing techniques that can be applied. Should we be having this discussion on the dev list instead, as that is where the decision makers are? Is there an appetite for debating JSPWiki's future? On 8 February 2016 at 01:55, Jason Morris <jason.mor...@sydney.edu.au> wrote: > Hi Robert, > > > > Dave [Koelmeyer] and I have been attempting to address this issue from the > Glassfish side of things. We are drafting a brief but comprehensive set of > installation instructions for JSPWiki on Glasfish 4.x. So far, I've tested > them on Glassfish 4.0, and they work just fine. > > > > Some ideas: > > > > · What about a JSPWiki Admin page/console not unlike the managers > page in Tomcat? > At least some rudimentary permissions/roles could be managed there. > > > > · What about providing some kind of installation shell script that > put everything where it needs to go? > > > > 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? > > > > Cheers, > > Jason > > > > -----Original Message----- > From: Robert Spiske [mailto:ep...@spiske.name] > Sent: Monday, 8 February 2016 3:46 AM > To: user@jspwiki.apache.org > Subject: Re: Open Discussion - How to increasing JSPWiki publicity ... > > > > Hello! > > > > about 2 years ago i gave JSPWiki a try. > > Most of my problems were related with to little documentation. Partly > because the apache site was not up yet. > > > > First i had a few installation problems. > > Using Debians tomcat installation i had problems with the filesystrem > access control and finding the right locations of wiki ini files to edit. > > > > Trying to fit the wiki to the corporate design, had no obvious howto. > > > > Writing a portal of my own, i wanted to use the same logins and groups, > found out, that this was not as simple as i hoped. > > > > Thought that it would be nice to use the wiki hidden behind the portal i > was writing, searched for API function to add and update pages and some > function to render the content to fit into my pages. > > > > It would have been great to import a lot of pages from a mediawiki, turned > out not to be easy because of plugins on the mediawiki side. > > > > After learning this and because of other design issues, I have put the > JSPWiki integration to a hold, some day i will probably take it up again. > > > > Perhaps this can help to come up with a way to make JSPWiki more popular. > > > > Robert > > > > > > >
