Next in thread →
Next in month →
RE: [cti] Motion for Open Repository for CTI TC training materials
I second the motion. Sarah Kelley Senior Cyber Threat Analyst Multi-State Information Sharing and Analysis Center (MS-ISAC) Elections Infrastructure Information Sharing and Analysis Center (EI-ISAC) 31 Tech Valley Drive East Greenbush, NY 12061 518-266-3493 24x7 Security Operations Center - 1-866-787-4722 From: [mailto:] On Behalf Of Trey Darley Sent: Monday, April 02, 2018 1:07 PM To: OASIS CTI TC list Subject: [cti] Motion for Open Repository for CTI TC training materials tl;dr: A number of folks are collaborating on a set of CTI training materials. This work needs a home, hence this motion. I move that the TC approve by unanimous consent requesting OASIS to set up an OASIS Open Repository project named cti-training using the following pieces of information: * Purpose Statement: A collection of CTI-related training materials * Initial Maintainers: Trey Darley, John Wunder, Ivan Kirillov * Open Source License: BSD-3-Clause License * GitHub Name: cti-training * Short Description: OASIS Open Repository: CTI-related training materials If there have been no objections by Thursday, 05 April at 21h UTC I will submit the form [1] to request OASIS staff to create the repository. [1]: https://www.oasis-open.org/resources/tc-admin-requests/open-repository-request -- Cheers, Trey ++--------------------------------------------------------------------------++ Director of Standards Development, New Context gpg fingerprint: 3918 9D7E 50F5 088F 823F 018A 831A 270A 6C4F C338 ++--------------------------------------------------------------------------++ -- "No one can terrorize a whole nation, unless we are all his accomplices." --Edward R. Murrow This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments. . . . . .
Next in thread →
Next in month →