-
Notifications
You must be signed in to change notification settings - Fork 95
Meeting minutes 2016 02 04
- Juliane
- Magda
- Nick
- Roger
- Sebastien
- Shane
As of this call, we have 9 contributors.
Welcome aboard and many thanks to Shane Taylor, who submitted 3 pull requests since the last call.
-
DITA-OT 2.2.2 was released, with 2 main fixes:
http://www.dita-ot.org/2.2/release-notes- Shortdescs from bookmaps w/ BASIC chapter layout #2023
- Windows Ant bug #2172
-
DITA-OT 2.2.3 maintenance release planned with further 2.2 bugfixes
-
Development docs at http://www.dita-ot.org/dev/ have new features,
serve as a prototype for new WebHelp output:- Bootstrap Sass for additional styling options (see note styles, etc.)
- Dynamic ToC can be expanded & collapsed independent of current topic
- Topic finder: press
tto filter the list of topic titles - Keyboard shortcuts help: press
?
- Info for the dita command, properties files, migrating ant builds #62 by Shane
- Generate annotated samples/template.properties file #60 by Shane
- Add samples files from the OT repo refactoring #58 by Shane
- Mention plugin.rnc in the docs #61 by Stefan
- Update “Tested platforms and tools” #59 by Roger
- The docs should link to the DITA generator #57 by Stefan
- Troubleshooting builds #56 by Shane
- Expand extension point descriptions #55 by Roger
- Generate annotated samples/template.properties file #60 by Shane
- Add samples files from the OT repo refactoring #58 by Shane
- Update references to DITA 1.3 spec #48 by Roger
- Certain extension points are not explained anywhere by Radu
Currently 20 Open Issues, 30 Closed:
https://github.com/dita-ot/docs/issues
Shane's latest pull request 62 currently in review, minor issues to address, should be merged soon.
-
Add info on migrating to v2.x #29
Shane is preparing input, not ready to merge yet. Proposes tracking this in a public feature branch rather than develop. Sebastien's team @ HERE is gathering migration best practices internally in their wiki, may be able to contribute portions of that as input soon.
Shane asks what markup to use in code examples to highlight inserted/deleted code? Currently using elements from the highlighting domain: <b> for insertions and <line-through> for deletions, as no more semantically appropriate alternatives seem to be available.
Shane wonders whether we want to highlight known DITA-OT issues in the docs?
Clearly there are some cases in which project owners may be reluctant to call attention to defects in software, but there are cases where the toolkit may behave differently than users expect, and it might be good to say:
This doesn't work the way you think it does, it works another way.
Roger suggests this content could be seen as related to troubleshooting information and included somewhere nearby.
Shane creates a new issue to track this task: https://github.com/dita-ot/docs/issues/63
Proposal from Shane for discussion:
Many of the issues are quite large in scope. Would more granular issues be easier to work with? I think they would encourage participation and make it easier to track progress. But then, I've grown to like working in Agile with frequent iterations, so maybe it's just me 😃
View the latest DITA Open Toolkit docs at www.dita-ot.org/dev.