OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cti message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [cti] Status of CTI OASIS Open Repositories


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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]