Meeting minutes 2016 10 06

Meeting facilitated by Kris Eberlein.

Attendees:

• George Bina and Radu Coravu (SyncroSoft)
• Jarno Elovirta
• Kristen James Eberlein (Eberlein Consulting)
• Leigh White (IXIASOFT)
• Bill Burns (Vasont)
• Roger Sheen (infotexture)
• Lief Erickson (Viavi Solutions)
• Bob Johnson (EBSCO)

1. Any updates about prior releases?

Release 2.3.3 released on 25 September; it fixes many bugs related to @copy-to. Jarno has not heard any feedback about this release. Roger commented that there was no public release announcement.

Action items:

• Robert: Announce the release on dita-users list
• Jarno: Will tweet. (Also has asked owner of ditaot handle if she would release the handle to the dita-ot project.)

2. DITA-OT 2.3 status and updates

Jarno: A few pull requests that Robert has reviewed and closed. There are a few others that Robert should review and merge. One (https://github.com/dita-ot/dita-ot/pull/2462) touches just about every module in pre-processing so might be too large for a proper code review. The tests pass, so it should be OK. It handles how pre-processing retains temp file names and desired files names. When these are merged, Jarno can do proper work on map-first processing. If Robert cannot review it, Eero could do so.

General agreement that map-first processing can be introduced in 2.4 but should not be the default. Several IXIASOFT clients (and WebWorks) have built plug-ins that modify pre-processing.

Discussion of moving to ship FOP 2.1. Radu has tested this the most; he reports that there are some issues with SVG. Jarno thinks we should use the new version, as a nod to the FOP team. Radu reports that it will be easy for someone to downgrade to an earlier version of FOP. General consensus to move to shipping FOP 2.1.

3. Doc updates and plans, update on documentation call

Roger: Work on contribution process information is on-going. There is a new requirement for contributors to sign-off their commit. Roger working on this for the documentation and Web site. Changes to CLI documentation to show usage of double hypens instead of single hyphens. (Single hyphens are deprecated but will still work.) Discussion of the fact that now that we are pointing people to the Dev version of the documentation (in order to use the "Edit this topic" functionality), we need a way to let people know that they are viewing the dev version of the documentation. General consensus that a banner would be best solution.

The focus for the 2.4 documentation is info on migrating plug-ins to latest versions of the DITA-OT

Action items:

• Robert and Roger will review contribution info currently present on site.
• Roger will post new contribution content on staging server for team review before going live with it.
• Roger: Implement banner for dev version of docs (done with site repo issue #24)

4: DITA-OT Day 2016

George reported that 50 people are registered. Sponsors are Comtech, Gnostyx, IXIASOFT, and Icarus Enterprise Solutions Ltd. George will promote at Lavacon.

Action items

• oXygen will promote on Linked; Twitter, and dita-users
• Speakers should tweet and otherwise publicize their sessions.
• Leigh will ask IXIASOFT Marketing to up their promotion.

5. Other topics

Roger is working on revising the landing page for the 2.4 release. He has a mockup that he is testing; it needs to work better with mobile devices.

Kris is working on developing a list of products (editors, content management systems, etc.) that use the DITA-OT. General agreement on the following:

• Should not use the term "ship", since that does not work for SaS products. No agreement about what verb to use; "use" is very vague, but "incorporate" or "integrate" is too precise. Discussion tabled for now. General agreement on the following:
• First priority is to list the companies that clearly "use" the DITA-OT;
• The topic can have a link for people who want to have their products listed (or removed) to open a pull request.