-
Notifications
You must be signed in to change notification settings - Fork 96
Meeting minutes 2017 04 06
- Attendance
- OT project status updates
- New issues since last call
- Fixed issues since last call
- Project planning board review
- Discussion
- Kris
- Peter
- Roger
- Shane
The DITA-OT contributor call was held immediately prior to the docs call. Meeting minutes are available at https://github.com/dita-ot/dita-ot/wiki/Meeting-minutes-2017-04-06.
- DITA-OT 2.4.5 was released on March 27. See http://www.dita-ot.org/2.4/release-notes/.
- 2.4.6 scheduled for April 18, currently 3 fixes.
8 new issues & pull requests were created since the last call, only 1 of which is still open:
The remaining new issues have already been fixed:
A total of 7 issues & pull requests were closed.
- #133 – Update docs to mention the current way of referring keys
- #134 – Missing 'dita:' prefix in 'new extension point' example
- #137 – plugin-addgeneratedtext references deprecated getString
Of those, 4 were pull requests (one each by Robert & Shane, plus 2 new contributors who sent PRs via the oXygen Web Author).
- #135 – Add missing 'dita:' prefix in extension point example #134
- #138 – Quick fix for #133
- #139 – Tweaking technically innacurate (obsolete) info
- #140 – Fixed typo in doc. There was no closing target tag.
The docs issue tracker at https://github.com/dita-ot/docs/issues currently lists 19 open issues, 78 closed.
Our GitHub Projects boards show the status of issues currently associated with each release milestone and serve as the primary planning overview for upcoming releases:
- Roger returns to the idea of indexing input from IA students, using Shane's spreadsheet in Google Docs: https://docs.google.com/spreadsheets/d/1SyvjMTIIOu7ICoA16FwX758QnvmWF3nN2K0XP5VNvaw/
- Shane suggests the original spreadsheet can be copied & shared as necessary
- Peter found the resources he lost with his old laptop, hopes to share soon
- Peter to share his indexing resources
Peter asks what implications preprocessing changes will have for docs, discussion on how best to document those. Roger mentions that Robert & Jarno will provide input, Peter might be able to review.
Shane mentions we might want to be more explicit about best practices for extending. This is what you should use the extension points for and this is what you should NOT do with them.
Shane has been using the DITA-OT docs build to test a new DITASearch plugin for DITA-OT HTML5 transformations: https://github.com/shaneataylor/ditasearch.
A sample build is available at http://www.taylortext.com/dita-ot-docs/. Shane would appreciate the team's feedback, suggestions during the next docs call.
- Team to review DITASearch plugin, prepare feedback for next meeting
Revise top-level documentation structure #121
Shane would like to take a stab at reorganizing the docs to suggest a possible new top-level organization. He views finding the information as the most difficult task users face.
Roger cautions this could require more effort than we may have time for between now and the 2.5 release deadline (May 31). General concern that reorg may expose holes we don't have time to fill. Shane thinks it's still best to start.
Brief discussion on how best to flag any topics that are incomplete. Since dev docs are frequently viewed, Roger would prefer to avoid any "under construction" signs, make sure whatever's there makes sense as is, then extend later as time allows.
Shane suggests adding a more visible call to action banner for WIP topics to encourage people to contribute.
- Roger to explore options for more visible Edit this page links/banners.
https://github.com/dita-ot/docs/wiki/Meeting-minutes-2017-04-06
Created 2017-04-06 16:14
View the latest DITA Open Toolkit docs at www.dita-ot.org/dev.