Hi all,

  I opened five Jira issues with proposals for where JSPWiki could go next.
None of them is implemented. I would like to hear whether the direction
makes sense before anybody writes code.


   1.   JSPWIKI-1310, a versioned REST API with an OpenAPI description.
   Today /ajax/ serves JSON only for the UI, the XML-RPC endpoints are
   commented out by default in web.xml, and there is an Atom feed. Nothing is
   documented or versioned. The question I most need answered is whether this
   should live in jspwiki-main or in a new module.
   2.   JSPWIKI-1313, a modern editor with Markdown in mind. The plain
   editor already has a live preview. The CKEditor and TinyMCE templates load
   libraries that are not in the repository, and FCK is only in the legacy
   template 210. Open question: do we want a WYSIWYG mode for Markdown at all?
   3.   JSPWIKI-1312, replacing Mootools and the icon font. It overlaps
   with JSPWIKI-1097, which already set the target of native JavaScript. I can
   close 1312 as a duplicate if you prefer. The issue has measurements of how
   much code dependson Mootools.
   4.   JSPWIKI-1311, metrics, a health endpoint and structured logging.
   org.apache.wiki.management only has SimpleMBean, and there is no
   Micrometer, Prometheus or health code.
   5.   JSPWIKI-1314, search relevance and filters (lower priority). No
   Lucene field is boosted, and there are no filters by date, author or
   attachment type.


Separately, there are open pull requests for older issues, among them the
security-manager removal (JSPWIKI-129), the htmlunit-neko migration
(JSPWIKI-1206) and the password hash, expiry and lock work (JSPWIKI-1231
and JSPWIKI-1254).
Reviews are welcome. Some of them are stacked on each other, and the PR
descriptions say which.

Thanks,
Arturo

Reply via email to