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] 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" <gback@mitre.org>
Date: Wednesday, May 23, 2018 at 2:58 PM
To: Bret Jordan <Bret_Jordan@symantec.com>, Allan Thomson <athomson@lookingglasscyber.com>, "cti@lists.oasis-open.org" <cti@lists.oasis-open.org>
Cc: Interoperability Subcommittee <cti-interoperability@lists.oasis-open.org>
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.





[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, "cti@lists.oasis-open.org on behalf of Bret Jordan" <cti@lists.oasis-open.org on behalf of Bret_Jordan@symantec.com> 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.



From: cti-interoperability@lists.oasis-open.org <cti-interoperability@lists.oasis-open.org> on behalf of Allan Thomson <athomson@lookingglasscyber.com>
Sent: Tuesday, May 22, 2018 4:45:42 PM
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



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