Re your message on GitHub ("... The DITA TC has been looking at the GitHub Issue Tracking technology... ")
I thought I might remind you that indeed, several OASIS TCs are now using GitHub [1] for version control, issues tracking, threaded comments (conversations), Wiki pages, collecting input from outsiders, etc
Two or three of the repos were launched specifically because the TC participants like GitHub issues tracking, with the ability to use labels and to associate comment threads with particular issues. On Issue labels, I don't know about formal mechanisms for faceted classification, but see some examples here:
Requesting creation of the OASIS repo is simple: just have Chair or Secretary fill out the form:
Documentation:
GitHub Repositories for OASIS TC Members' Chartered Work
I'll be happy to answer any questions you might have.
- Robin Cover
[1] TC GitHub Repository examples
Current OASIS TCs that use GitHub repos for TC work
"The purpose of this repository is to support version control for Work Product artifacts developed by members of the OASIS Common Security Advisory Framework (CSAF) TC, including prose specification editing and secondary artifacts like meeting minutes, productivity code, etc. "
"The purpose of this repository is to provide version control support for development of source files for the written DITA specification."
"The purpose of this repository is to provide issue tracking and wiki pages for the STIX 2.x Work Products, including: Part 1: STIX Core, Part 2: STIX Objects, Part 3: Cyber Observable Core, Part 4: Cyber Observable Objects, and Part 5: Patterning"
"The purpose of this repository is to support development of a JSON serialization of the XLIFF Abstract Object Model, as managed by members of the OASIS XLIFF OMOS TC."
"The purpose of this repository is to support development on an Object Model for XLIFF Versions 2.0 and higher, under management of the OASIS XLIFF OMOS TC."
"The purpose of this repository is to support development of standard vocabularies for annotating OData services. It contains the most recent copies of the OData vocabularies authored by members of the OASIS OData Technical Committee."
"The purpose of this repository is to support development of tools for producing OpenAPI descriptions for OData services."
"The purpose of this repository is to provide version control and issues tracking to support development of resources related to the OASIS OSLC Domains Technical Committee."
[Pending] An official OASIS repository for the LWDITA SC (Lightweight DITA Subcommittee)
On Tue, Jan 31, 2017 at 10:34 AM, Dr. Stanley Doherty <stan@modularwriting.com> wrote:
Hi all --
At our ATC meeting yesterday, we discussed developing some more formal listening session tracking process. The DITA TC has been looking at the GitHub Issue Tracking technology.
I forward for your review two links:
1. Feature overview
> See "Integrated issue tracking" at:
https://github.com/features
2. Sample Issue Tracker sheet (dita-migrations)
> https://github.com/StanDoherty/dita-migrations/ issues
FYI . . .
Stan
Robin Cover
OASIS, Director of Information Services
OASIS, Director of Information Services