Chartered Work Repos (was: RE: [cti] Status of CTI OASIS Open Repositories)

["Back, Greg" <gback@mitre.org>]

Thanks for clearing that up, Bret.

I was under the impression, based on the text in the ballot [1] that they would contain more than that. Are you anticipating issues being added by both TC members and non-members?

I've seen GitHub used occasionally for tracking issues other than for the content in the same repository, I worry that a workflow for addressing the issues will be difficult to maintain. 

One big factor in favor of using GitHub at all is that many people outside the TC already have accounts, but I don't see a TC-specific organization vs. an OASIS organization as being a significant factor.

Greg

[1] https://www.oasis-open.org/committees/ballot.php?id=2972 

> -----Original Message-----
> From: Bret Jordan (CS) [mailto:Bret_Jordan@symantec.com]
> Sent: Monday, October 10, 2016 6:38 PM
> To: Back, Greg <gback@mitre.org>
> Cc: cti@lists.oasis-open.org
> Subject: Re: [cti] Status of CTI OASIS Open Repositories
> 
> 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 Oct 10, 2016, at 5:33 PM, Greg Back <gback@mitre.org
> <mailto:gback@mitre.org> > wrote:
> 
> 
> 
> 	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
>