Skip to content

Meeting minutes 2023 12 07

Robert Anderson edited this page Dec 7, 2023 · 5 revisions

Attendance: Radu Coravu, Jarno Elovirta, John Pashley, Robert Anderson, Chris Papademetrious, Mark Giffin, Roger Sheen, Josh Johnson, John Kirkilis, Brianna Stevens-Russell

Item 1: Any updates about prior releases?

Could do one if needed, likely would only target security patches. Problem was reported in logback library.

Item 2: DITA-OT 4.2 Development status and updates

Can #4330 be merged? (https://github.com/dita-ot/dita-ot/pull/4330) Should be ready to go. Had some questions about whether to continue making updates to XHTML; generally, no issue accepting pull requests like this, although there is no intention that HTML5 / XHTML have to retain parity, so it's also likely going forward that we will get some updates that only go into HTML5.

Discussion of XSLT 3.0 -- should we update to use it? Saxon supports; we could change the version on all of our stylesheets and see if it causes any issues. Should do this on a feature branch and let it sit for a while, allow people to comment / test against it. Chris to open pull request

Project board for next release: https://github.com/orgs/dita-ot/projects/42

Jarno working on pull request to update the "integrate" process, to avoid using Ant. Should log a message that the old method is deprecated, although it will remain available. https://github.com/dita-ot/dita-ot/pull/4329

Also working on larger change to logging in general. How we usually log messages today with Ant logging, with numbers in brackets, etc. Updating to make it more modern:

  • Removing some things that we don't need
  • Use colors
  • Don't base message on the name of the Ant target, use readable value
  • Configurable log style "legacy" or "fancy", legacy uses the current one, fancy is the new one
  • This has, in generally, been a very troublesome project

Continued discussion: refactoring of log messages. Still have a few that we cannot tell if they are used somewhere, or are safe to remove. Should we go ahead and merge the work, or leave it open for a bit? Marking ready for review https://github.com/dita-ot/dita-ot/pull/4287

Discussion of Mark's issue -- https://github.com/dita-ot/dita-ot/pull/4303 -- would it be possible to use a data-compact attribute instead of using a class, for compact lists? LWdita ticket that prompted this -- https://github.com/jelovirt/org.lwdita/issues/178

Ops board: https://github.com/orgs/dita-ot/projects/39

Item 3: Doc updates and plans

  • Got some feedback about build instructions that resulted in updates
  • Contributions from Nokia also merged

Item 4: DITA-OT Day 2024

About 50 people registered. Agenda is almost complete.

Jarno will likely have an overview session of changes from the last few releases (short presentation). Future discussion ideas can be left for the "shop talk" at the end.

Generally - we have a lot of proposals, Robert and Jarno are happy to shorten their pieces / shorten shop talk to let everyone hear more from other people.

Item 5: Other 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.

Clone this wiki locally