|
The chartered work repos have one primary purpose for us, and that is issue tracking against the published specifications. We may use them for wikis or other things over time, but for the foreseeable future they will be used for issue tracking.
Bret
Sent from my Commodore 64
PGP
Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050
On 10/10/2016 3:08 PM, Bret Jordan (CS) wrote:
I disagree. It would make things a lot easier if the Chartered work
repos were done as TC level projects instead of individual repos.
What specifically would be easier?
What specifically are we trying to do with Chartered Work repos? I would not recommend using them for prose specifications, unless we're planning to develop the specifications as Markdown, HTML, or some other plain text format. I've been given the impression
that we don't want to include JSON schemas as chartered work products, hence why cti-stix2-json-schemas and cti-cybox3-json-schemas [sic] are open repositories.
Further, I think this TC should create an open source project on github
that is outside of OASIS for all of our opensource projects and
contributions that come from MITRE or others.
The MITRE members of the TC have made an explicit decision to contribute our code to OASIS Open repos, rather than (for instance) continuing to use STIXProject.
What does being "outside of OASIS" gain us? What does it even mean for "the TC" to create something outside of OASIS (and therefore outside the TC)? As I've said before, anyone (including a TC member) is of course free to create whatever repositories
they'd like.
----------
I'd still appreciate hearing from Mark, John, and/or Trey.
Greg
|