Meeting minutes 2019 05 09

Attendance: George Bina, Jarno Elovirta, Kerry Langford, Robert Anderson, Lief Erickson, Roger Sheen, Frank Wegmann, John Pashley, Shane Taylor, Kris Eberlein, Radu Coravu

Item 1: Any updates about prior releases?

Plan for hotfix 3.3.2: open pull request needs to be cherry picked. Roger will do that. Robert has a minor fix coming for generated text, and is working on an out-of-memory error that hasn't been diagnosed yet.

Roger asks about the pixellated warning image - maybe we could replace it with the better SVG variant that we already have? Will prep a pull request and discuss there.

Shane has pull request to consider as well: https://github.com/dita-ot/dita-ot/pull/3293 Robert and Jarno will look closer.

Item 2: DITA-OT 3.4 Development status and updates

3.4 project board: https://github.com/orgs/dita-ot/projects/12

Project files: Jarno created a branch with example files that are more-or-less realistic, real-world project files. Would like feedback here: https://github.com/dita-ot/docs/pull/252

Currently project files are intended for use with CLI, but may also want to add support for Eero's Gradle plugin, which might mean adding a Java API (not sure).

Multiple input file support https://github.com/dita-ot/dita-ot/pull/3286

• Have an implementation. It's simple - if you have multiple input files, it builds a map around them.
• Problem: can't really do things like reference multiple bookmaps and get reasonable book output.
• Extended discussion of possibilities...
• What it means to have more than one input, what output should be created?
• If you have 3 input topics and generate 3 output HTML files, great - what about PDF? 3 PDFs, or one? With TOC, or without?
• Given the uncertain answers of "What is the right output?" - not sure how broadly this can or would be used. Maybe ship marked as "experimental", may go away if it doesn't work out?
• Robert can imagine some uses for it (primarily HTML), generally as a way to process several independent collections at once - with all cross-linking - and then split back up into collections.
• Radu also comments that several people continue to request the ability to publish a single topic with the map context - "I want to send out this one topic as a PDF for review but need keys to resolve for that to work"

Item 3: Doc updates and plans, update on documentation call

Lief continues to work on masters thesis idea. Looking at TOC, while also contemplating facets and maybe even subject schemes.

George featured DITA-OT docs in his STC presentation this week about Docs as Code.

Item 4: DITA-OT Day 2019

Comment from last meeting: "Need to come up with a theme for DITA-OT-Day this year". Assignment for everyone to put their ideas into #dita-ot-day slack channel.

Details are coming: https://www.oxygenxml.com/events/2019/dita-ot_day.html

Item 5: Other topics

...

Item 6: Backlog discussion

Project boards: Project boards: https://github.com/orgs/dita-ot/projects/

Time to go through pull requests, issues tracker, determine how to handle open issues.