Re: [Jamwiki-devel] Thinking about continuing JAMWiki development

[Ryan H. <rya...@gm...>]

Hi Audrius,

It's been more than two years since the last JAMWiki release and I've 
been debating what to do with the project, so it's great that you're 
interested in it.

One thing I've been thinking about is that, rather than continuing on 
with the project under the same name, it might make the most sense to 
continue the project by creating a fork of the existing code & 
documentation under a new name - call it JAMWiki2, JAMWikiNext, or start 
fresh with a name that doesn't include "JAMWiki" at all.  That would 
allow you to push forward with whatever vision you have for the project 
and allow some freedom from supporting old code and requirements, and 
would also make it clear that the project is moving in a new direction. 
  Would that make sense to you?  I can make it clear on jamwiki.org and 
the JAMWiki Sourceforge page that your project is an "approved" and 
active fork, and eventually just redirect JAMWiki traffic to your 
project.  I could also provide some assistance in the initial setup if 
desired.

While I would love to personally continue developing JAMWiki, the 
balance between the amount of time required to produce a quality product 
and the benefit provided vs. other available solutions is something I 
can no longer justify, so if the project can continue in some way under 
another person or group's leadership I am excited to support that endeavor.

Please let me know your thoughts.

Ryan


On 7/12/2015 10:00 AM, Audrius Meskauskas wrote:
> Hello, Ryan, hello, list,
>
> You have asked, if anybody would like to take over JAMWiki development
> and maintenance. Ok, me the great ...
>
> I am the initiator of Ultrastudio.org project which used a fork 0.8.4. I
> have made many various changes in the code, including some security
> hardening, but did not contribute back upstream at that time as most of
> changes required were way too specific of my focused goals and I was not
> paying attention to be generic enough (PostgreSQL only and so on).
> Ultrastudio.org, if somebody is interested in, was a project to build a
> Wikipedia-like encyclopedia with Java applets easily enabled, addressing
> security through server side applet compilation after public code review
> and automated security scan. We operated for a few years with some
> limited success but have no technical possibility to continue after
> Oracle just disabled unsigned applets. The server is still running in a
> read only mode now.
>
> Successful or not, this project gave me significant experience with
> JamWiki code, I am fully comfortable with the build system and project
> layout, so probably could take over development and maintenance. My
> primary focus would be keeping up with the newer technologies where
> available (Java 8, Google Guava, we may later try something more
> sophisticated like Cassandra for the storage) and further hardening
> security, and also maybe some Selenium tests. Also, if it would be
> enough interest from the side, in the future may be good to migrate the
> code into GitHub, doing further development through pull requests and
> code review.
>
> I will discuss my changes with you, as long a you may have time for
> this, and will listen carefully if you oppose on serious grounds, but I
> also would like to have certain freedoms as well. You have asked
> somebody for taking over and I mean exactly this. To indicate the
> possible major alterations, we may increment the major version number.
>
> I am Java developer with researcher background. I started to program in
> this language when it first came long time ago, use Java heavily at work
> and at some time have contributed over 100 000 LOC to GNU Classpath.  I
> plan to work on JAMWiki as on the hobby project without ambitions to
> make business or fame out of it. I think it should be an "ecologic
> niche" for a good and simple Java Wiki on the world as MediaWiki
> basically dictates all your server architecture (must be LAMP) and
> Confluence is horribly expensive to try anything more serious with it,
> leave alone it is closed source. Also, I do not take removing from
> Wikipedia into serious consideration as this was part of the some
> strongly pushed process that also removed high quality commercial tools
> like Magnolia or Jahia, probably just to show there is no any notable
> Java wiki engine remaining.
>
>
> With respect
> Audrius
>
>
> _______________________________________________
> Jamwiki-devel mailing list
> Jam...@li...
> https://lists.sourceforge.net/lists/listinfo/jamwiki-devel
>