-
Notifications
You must be signed in to change notification settings - Fork 193
Meeting minutes 2023 07 06
Attendance: Radu Coravu, Chris Papademetrious, Frank Wegmann, Roger Sheen, Jarno Elovirta, John Pashley, Julien Lacour, John Kirkilis, Lief Erickson, Josh Johnson
Released in between last meeting and this one.
The beta 2.0 grammar files have an issue which will need to be updated in first patch.
Snakeyaml project has some security issue, may need to bump. To get latest snakeyaml, likely need to update entire jackson set of libraries. Radu notes that the guava library also has a recently reported issue.
4.1.1 project board: https://github.com/orgs/dita-ot/projects/43
Project board for next release: https://github.com/orgs/dita-ot/projects/42
One idea for the release: we have a lot of styles for error messages coming from the CLI. They've grown over years, from different people. Would be nice to go over all of them together and try to standardize.
Looking for general themes for the release. One idea is to focus on usability (similar to previous item). Jarno specifically requesting ideas, as his ideas for improvements probably would not target the primary user community.
Couple ideas from the call:
- One idea related to pdf themes. In Rotterdam, think there was an idea about themes defining both XSL-FO attribute sets, and also CSS, so that the theme could be reused. Could imagine using the CSS for html output. One tricky thing is that while xsl-fo and CSS look similar, they have gone separate ways for a couple decades now, so the reuse is not straightforward; CSS is actively developed with new features that go new directions, FO has been quite stable for a while. Reuse potential is also a bit murky, as HTML and PDF tends to have different requirements (at least in small ways).
- Other idea is to think about more progress on incremental builds.
- One idea - could switch html5 to preprocess2? Good discussion. A few blockers - likely some bugs in there we've never seen; not as many extension points available for developers. Some discussion about hash file names ... if error messages are working properly, you have the original file name in the message.
Ops board: https://github.com/orgs/dita-ot/projects/39
Not yet using markdown map in our 4.1 docs; now that 4.1 is out, we can likely update to use a markdown submap somewhere and build it with 4.1.
PDF theme schema is flagging a bunch of things as invalid, which are actually working in the theme; still investigating the utility of that schema, if it's giving false reports then it's less reliable.
...
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.
View the latest DITA Open Toolkit docs at www.dita-ot.org/dev.