cti-interoperability — archive

Re: [cti] Re: [EXT] [cti-interoperability] Motion for Open Repository for CTI Interop Issue Tracking

From: Jason Keirstead <[email protected]>
To: [email protected]
Date: Thu, 24 May 2018 13:37:00 -0000

I am with Allan on this. If we can't accept bug reports from non-TC members, this entire STIX Preferred effort is doomed to failure. I fail to see how reporting a bug or change request on something like a test case is an IPR issue. There is no IP here. - Jason Keirstead STSM, Product Architect, Security Intelligence, IBM Security Systems www.ibm.com/security "Things may come to those who wait, but only the things left by those who hustle." - Unknown From: Bret Jordan <[email protected]> To: Allan Thomson <[email protected]>, "Back, Greg" <[email protected]>, OASIS CTI TC list <[email protected]> Cc: Interoperability Subcommittee <[email protected]> Date: 05/24/2018 02:30 AM Subject: Re: [cti] Re: [EXT] [cti-interoperability] Motion for Open Repository for CTI Interop Issue Tracking Sent by: <[email protected]> The reason I think it needs to be a TC Repo, is the issue tracker will track changes. Due to IPR rules, I do not think we could take suggestions from non-TC members, aka, no bugs, issues. Bret From: Allan Thomson <[email protected]> Sent: Wednesday, May 23, 2018 4:05:12 PM To: Back, Greg; Bret Jordan; OASIS CTI TC list Cc: Interoperability Subcommittee Subject: Re: [cti] Re: [EXT] [cti-interoperability] Motion for Open Repository for CTI Interop Issue Tracking Our intention is interoperability (i.e. STIXPreferred) is available to non-TC members to participate in. I can imagine that non-TC specific information be available on the repo. So I think it is appropriate in this case that the repo is open rather than restricted to the TC. Allan Thomson CTO (+1-408-331-6646) LookingGlass Cyber Solutions From: "Back, Greg" <[email protected]> Date: Wednesday, May 23, 2018 at 2:58 PM To: Bret Jordan <[email protected]>, Allan Thomson <[email protected]>, "[email protected]" <[email protected]> Cc: Interoperability Subcommittee <[email protected]> Subject: Re: [cti] Re: [EXT] [cti-interoperability] Motion for Open Repository for CTI Interop Issue Tracking I’m fine with either, but I’ll point out that a motion to create an open repo is very different from a motion to create a TC repo. Based on what Allan is saying in the purpose statement, it’s probably more suitable as a TC repo [1], using this form [2]. Again, I would be in support of either one, though. Thanks, Greg [1] https://www.oasis-open.org/resources/tcadmin/github-repositories-for-oasis-tc-members-chartered-work [2] https://www.oasis-open.org/resources/tc-admin-requests/request-a-tc-github-version-control-instance-be-created On 2018-05-22, 20:07, " [email protected] on behalf of Bret Jordan" < [email protected] on behalf of [email protected] > wrote: I second this, however, I would suggest the name just be cti-interop this way as an official work product repo, we could use it for other interop related things. Yes, obviously, it will have an issue tracker, but we could do other things with it as well. Bret From: [email protected] <[email protected]> on behalf of Allan Thomson <[email protected]> Sent: Tuesday, May 22, 2018 4:45:42 PM To: OASIS CTI TC list Cc: Interoperability Subcommittee Subject: [EXT] [cti-interoperability] Motion for Open Repository for CTI Interop Issue Tracking I move that the TC approve by unanimous consent requesting OASIS to set up an OASIS Open Repository named cti-interop-issues using the following pieces of information: * Purpose Statement: A CTI-Interoperability issue tracking repository * Initial Maintainers: Allan Thomson, Jason Keirstead * Open Source License: BSD-3-Clause License * GitHub Name: cti-interop-issues * Short Description: OASIS Open Repository: CTI-Interop Issue Tracking If there have been no objections by Friday, 25th May, 8am PST, I will submit the form [1] to request OASIS staff to create the repository. [1]: https://clicktime.symantec.com/a/1/O_ihu1E08Xl2-dCkw-ASiK6V6aRPMzaHPgA8JWCVguA=?d=uExWX7fZn2Kl6plF49kKe_LZP8lrMkLtXgjcy41DR0Fu0FSDcexzZAqC2nn1IMYh1vZ5FISBNpMlibp8Q0YGdjpkIAvhfVRjM1dsDF7cV4gT9qa8h0OjnyVkwC9MH38YSKD2lIHqyY8rhnZXjDuzWpBtp-VTHGRkjFV0W281F9vYddlnNEAE25ie-1Nhr0af-1LmnMK3x4VacBd2yc3UUhapIM5Pqqb-yRWtSq1ZVe0EGfmckl5y8-UwGLKOPkChB785CerSuPcODwZCi8FkAo5apC1IyU_dwL9khyfWaWdeH9AkaMHufWKd5VmISpiqqD5sPRcc9KLHxJQ_oIEHIjQQjQRnSPNRM6xRsDeD8nYOLsbdk6iZwtmXnnNOsf4riJlDR8Bh2-ZNEkQF5Kbql5CIO0Bj-vXyUHnKYHCAjWuD7fSaz6YXLfHN71fJx4whN1cAV3AA_F8MAUW8uP9AXd6s3VH576SP6yheifXsvXSPrvmnnX2t1VHrp2KdF36FZzPIqViSYyR4Mk5GEw%3D%3D&u=https%3A%2F%2Fwww.oasis-open.org%2Fresources%2Ftc-admin-requests%2Fopen-repository-request Allan