Hi folks, there is some “multiple instance support” which can also work around the “no department support” - I’m running for years 10 wikis on a single Tomcat instance :-)
On my wish list * Markdown support * Ease of embedding images * Mobile friendliness Cheers, Siegfried Goeschl PS: Maybe there is a JSPWiki presentation at ApacheCon North America 2016 :-) > On 06 Feb 2016, at 14:06, Jim Willeke <j...@willeke.com> wrote: > > I have been using JSPWiki for more than 10 years and I too think it has a > lot going for it. > > I agree with Dave. We need to answer "who is JSPWiki for?" > And what does Features does JSPWiki have that is not already present within > the market? > > These need to be one answered in one paragraph. > > I not see JSPWiki competing in a corporate environment: > > - Little (if any) support - SHOW STOPPER > - No Department Support (cannot be separated into different namespaces) > - SHOW STOPPER > - NOT mobile friendly > - Limited "pre-built" plugins to integrate with other Applications > (think source control or issue tracking) > - Limited Administration tools > - Need more GUI interfaces (like adding a photo or Excel embedded into > page) > > Personal Gripes > > - No markdown support > - No multiple instance support (Well at least poor) > > It is listed on some comparison sites > <http://www.wikimatrix.org/show/JSPWiki>, but not sure how current things > are. > > From a technical standpoint, of course, almost anything is possible. > From a market penetration standpoint, it is a different story. > > -jim > > > > > > > -- > -jim > Jim Willeke > > On Sat, Feb 6, 2016 at 1:13 AM, Dave Koelmeyer < > dave.koelme...@davekoelmeyer.co.nz> wrote: > >> On 30/11/15 11:21, Paul Uszak wrote: >>> I think that one of the initial points people should address, prior to >>> launching a publicity campaign, is: who is JSPWiki for? It's pretty >>> important to identify the market segment that efforts will then be made >>> towards. We could all just talk about it a lot, but it's more efficient >> if >>> someone actually has an idea as to what is to be achieved, for whom. >> >> Fair point, but some of this is already covered right on >> http://jspwiki.apache.org/ and >> http://www.ecyrd.com/JSPWiki/wiki/JSPWikiFeatures. Any organisation >> looking for the particular features listed there would be in the target >> market for JSPWiki, for instance. >> >>> From a personal perspective as a user, it appears that JSPWiki is only >>> suitable for a highly technical computer user. I use it because it meets >>> certain nerdy requirements. Most casual users don't know what a server >> is. >> >> I don't follow your logic at all. I don't think any organisation >> interested in choosing JSPWiki to host instead of say Confluence or >> MediaWiki expects their end users to install and run the product >> themselves (comparisons to a desktop app such as Thunderbird are >> completely apples to oranges). >> >>> Dave, you can get an impression of what I'm talking about by comparing >> the >>> ease of installation of Thunderbird to that of JSPWiki. Therefore, if >> you >>> think that we should be targeting developers /programmers, I would >> suggest >>> that perhaps those who want JSPWiki, know or can readily find out about >>> JSPWiki. There might be an inherent danger of diminishing returns by >>> publicising a highly technical product into the mainstream segment. >>> Marketing 101 tells us not to advertise AR15s during the Super Bowl half >>> time slot. >> >> I'm referring to volunteering free time and effort with a fair amount of >> existing expertise to a small project which suffers from a lack of >> visibility (the JSPWiki page even got yanked from Wikipedia due to a >> lack of notability) – not the Super Bowl. >> >> I use JSPWiki for a variety of product and project documentation tasks, >> and it largely excels at both. However, the legacy UI is getting long in >> the tooth in terms of ease-of-use, and the problem with HADDOCK as far >> as I am concerned is there are just not enough folks using it and >> providing feedback. It's a great start but is not there yet for >> full-time use (and I feel like a lone voice on JIRA). Hence why I'm in >> strong agreement with the original author of this post, and why I'd >> really like someone from the project to jump in here with some points of >> view. >> >> Cheers, >> Dave >> >> >>> On 29 November 2015 at 10:55, Dave Koelmeyer < >>> dave.koelme...@davekoelmeyer.co.nz> wrote: >>> >>>> Hi All, >>>> >>>> Sorry to bump an ancient thread (which I bumped previously with no >>>> response). There is still only a JSPWiki Facebook group with the same >>>> whopping four members. Janne enabled admin access for me a long while >>>> back, but what should happen ideally is to create a Facebook Page, and >>>> perhaps an associated Twitter channel, and start spreading the word a >> bit. >>>> >>>> I'm super-happy to take the lead on this, but I imagine it would need to >>>> be approved by Apache. >>>> >>>> I currently handle social networks publicity for Mozilla Thunderbird, so >>>> I've got a fair bit of experience on this one. >>>> >>>> How can we get this progressed, and does anyone have any other points of >>>> view? >>>> >>>> Cheers, >>>> Dave >>>> >>>> -- >>>> Dave Koelmeyer >>>> http://blog.davekoelmeyer.co.nz >>>> GPG Key ID: 0x238BFF87 >>>> >>>> >>>> >>>> On 13/04/14 15:31, Dave Koelmeyer wrote: >>>>> On 4/10/2014 8:54 PM, Siegfried Goeschl wrote: Hi folks, >>>>>> the question at hand is to increase JSPWiki’s publicity - how can we >> do >>>>>> that? Unfortunately Open Source also consists of lot of advertising >>>>>> otherwise no user will ever use it :-) >>>>> Really ramping up activity on social networks would be a good idea, >>>>> Facebook and Twitter specifically. There is a Facebook page with a >>>>> whopping four members, and activity on there is all but dead. Happy to >>>>> make a time commitment here to start posting fresh content. >>>>> >>>>> Cheers, >>>>> Dave >> >>
