This page (revision-19) was last changed on 09-Aug-2016 03:01 by Dave Koelmeyer 

This page was created on 04-Aug-2016 04:53 by Dave Koelmeyer

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Version Date Modified Size Author Changes ... Change note
19 09-Aug-2016 03:01 8 KB Dave Koelmeyer to previous Scratchpad - increasing JSPWiki publicity ==> JSPWiki publicity
18 04-Aug-2016 08:08 8 KB Dave Koelmeyer to previous | to last
17 04-Aug-2016 08:02 7 KB Dave Koelmeyer to previous | to last
16 04-Aug-2016 07:42 6 KB Dave Koelmeyer to previous | to last
15 04-Aug-2016 07:33 6 KB Dave Koelmeyer to previous | to last
14 04-Aug-2016 07:32 6 KB Dave Koelmeyer to previous | to last
13 04-Aug-2016 06:44 6 KB Dave Koelmeyer to previous | to last
12 04-Aug-2016 06:39 5 KB Dave Koelmeyer to previous | to last
11 04-Aug-2016 06:37 5 KB Dave Koelmeyer to previous | to last
10 04-Aug-2016 06:30 4 KB Dave Koelmeyer to previous | to last
9 04-Aug-2016 06:28 4 KB Dave Koelmeyer to previous | to last
8 04-Aug-2016 06:19 4 KB Dave Koelmeyer to previous | to last
7 04-Aug-2016 06:11 3 KB Dave Koelmeyer to previous | to last
6 04-Aug-2016 06:00 3 KB Dave Koelmeyer to previous | to last
5 04-Aug-2016 05:54 2 KB Dave Koelmeyer to previous | to last
4 04-Aug-2016 05:52 2 KB Dave Koelmeyer to previous | to last
3 04-Aug-2016 05:51 2 KB Dave Koelmeyer to previous | to last
2 04-Aug-2016 05:48 1 KB Dave Koelmeyer to previous | to last
1 04-Aug-2016 04:53 346 bytes Dave Koelmeyer to last

Difference between version and

At line 8 changed one line
This page contains a summary of the discussion which occurred under the ''"Open Discussion - How to increasing JSPWiki publicity"'' thread on the JSPWiki mailing lists. This may help to focus our publicity efforts as (temporarily) documented at [Scratchpad - increasing JSPWiki publicity].\\
This page contains a summary of the discussion which occurred under the ''"Open Discussion - How to increasing JSPWiki publicity"'' thread on the JSPWiki mailing lists. This may help to focus our publicity efforts as (temporarily) documented at [Scratchpad - increasing JSPWiki publicity|JSPWiki publicity].\\
At line 74 added 12 lines
Also mentioned on the mailing list:
%%quote
"Re. facebook/twitter page... I'd only ask you to please redirect as much traffic as possible to the MLs, as there is where we usually lurk."
/%
So, this should also be included in our publicity process.\\
\\
%%info
__To do 2016-08-04:__ document a draft social networks process (or "policy") summarising the above steps, as well as guidance on the sort of content which is in-scope for publicising via these channels.
/%
\\
At line 104 added one line
/%
At line 93 removed one line
I not see JSPWiki competing in a corporate environment:\\
At line 95 removed one line
*Little (if any) support - SHOW STOPPER
At line 97 changed one line
*No Department Support (cannot be separated into different namespaces) - SHOW STOPPER
%%quote
"Best way to increase publicity is to release often. After every release
there've been an increase on use/MLs. Problem is, we do this on a free time
basis, so a mantaning an steady effort is complicated. So, the question is,
how do we do to foster collaboration, patches, etc?\\
\\
As for the wikipedia, maybe a wave of blog posts (which could also be sent
to the server side, voxxed, etc.) is enough to convince them to own our
page? But we do need people actually doing this, the time we spend on
JSPWiki is almost spent on coding."\\
\\
/%
\\
At line 99 changed one line
*NOT mobile friendly
%%quote
"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."
/%
\\
At line 101 changed one line
*Limited "pre-built" plugins to integrate with other Applications (think source control or issue tracking)
%%quote
"So, if we want to increase adoption, one plan of attack might be to:
At line 103 changed one line
*Limited Administration tools
* Target the Windows platform first.
At line 105 changed 3 lines
*Need more GUI interfaces (like adding a photo or Excel embedded into
page)
\\
* Make the installation, with all its dependencies (including Tomcat running as a Windows service), as transparent as possible to new users via customizable installation scripts/batch files.
At line 109 changed one line
Personal Gripes
* We can provide different kinds of pre-configured installation templates/options like:\\
**install as public wiki (this would close all the permissions and security that are wide open on the basic install and only allow admins to edit/delete).\\
**install as private, single-user wiki (this would be like my developer's journal installation)\\
**install with the following defined groups and roles (for people who already have a user structure in mind).\\
**custom installation (the traditional installation where the user sets all the properties)\\ \\
At line 111 changed 5 lines
*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.
* Provide some kind of control panel like the Tomcat App Manager so non-techies don't have to fiddle with editing text files. I know that this is an anathema to developers, but non-programmers really hate doing "anything" that resembles programming."
At line 117 removed one line
\\