[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] RE: [Non-DoD Source] [cti] RE: New Mini-Working Groups (UNCLASSIFIED)
This could be one potential approach to the question of historical transparency but we should note that it does not address the issue of collaborative participation.
If you can’t use Slack you still cannot participate directly.
I think there are several questions involved here:
I would say finding answers to #1 and #2 above are absolutely required for us to use this technology within OASIS.
I also think that #3 is very important though maybe not a hard OASIS requirement. I’m not sure there is a way to solve #3 for Slack as it is integral to its design. To solve #3 I think would require a different collaboration platform.
sean
From: <cti@lists.oasis-open.org> on behalf of Jason Keirstead <Jason.Keirstead@ca.ibm.com>
Date: Friday, March 11, 2016 at 10:37 AM To: "Bohling, James T CIV JS J6 (US)" <james.t.bohling.civ@mail.mil> Cc: "Casey, Eoghan CIV DC3/DCCI" <Eoghan.Casey@dc3.mil>, "'Jordan, Bret'" <bret.jordan@bluecoat.com>, "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> Subject: Re: [cti] RE: [Non-DoD Source] [cti] RE: New Mini-Working Groups (UNCLASSIFIED) I just want to raise that we have a pseudo-technical solution previously proposed to the Slack "problem". I wrote proof of concept code that took every slack chat and logged it for posterity as plain text (for example see
http://ctilogger.mybluemix.net/logs/stix).
CLASSIFICATION: UNCLASSIFIED +1 Slack and quick (hasty) changes. - James -----Original Message----- From: cti@lists.oasis-open.org [mailto:cti@lists.oasis-open.org] On Behalf Of Casey, Eoghan CIV DC3/DCCI Sent: Friday, March 11, 2016 9:22 AM To: 'Jordan, Bret' <bret.jordan@bluecoat.com>; cti@lists.oasis-open.org Subject: [Non-DoD Source] [cti] RE: New Mini-Working Groups All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ---- Bret, I believe that these efforts to make quick changes risks making hasty changes that are not adequately considered and that we will later regret. Furthermore, these mini-working groups break the transparency that was expected when moving to OASIS. Frankly, I am surprised that OASIS is permitting the use of Slack - how do those discussion get tracked within OASIS systems? Currently, my organization does not permit access to Slack so we do not have a way to see those discussion, never mind contribute. Until these questions are resolved, I recommend against these mini-working groups or further breakout discussions on Slack. Eoghan -----Original Message----- From: cti@lists.oasis-open.org [Caution-mailto:cti@lists.oasis-open.org] On Behalf Of Jordan, Bret Sent: Thursday, March 10, 2016 11:14 PM To: cti@lists.oasis-open.org Subject: [Non-DoD Source] [cti] New Mini-Working Groups All, We have kicked off a few mini-working groups to address some key issues, they are as follows: 1) Patterning: Allan, John-Mark, Jason, and Ivan are heading up this discussion. Anyone can join in on Slack at #patterning or on email. The due date for this proposal is Tuesday March 22nd. 2) Versioning: Looking for 3-4 people to lead this work. Anyone can join in on Slack at #versioning or on email. The due date for this proposal is Tuesday March 22nd 3) Sightings: Looking for 3-4 people to lead this work. Anyone can join on Slack at #sightings or on email. This due date for this proposal is Tuesday March 22nd. In general we will try and run 3-4 mini-working groups at a time, each with a 2 week delivery window. You can think of it as a sprint in development terms. If you want to be involved early on in the proposal phase, PLEASE make it known. Further, we hope to get leadership setup for Versioning and Sightings tomorrow. If any of you are interested in helping to lead either one of these, please let us know. (btw, we are looking for 3-4 leaders for each topic). They will be responsible for driving the discussion, gathering feedback from everyone, writing up proposed normative text, and then presenting their proposal on a CTI wide working call. Thanks, Bret Bret Jordan CISSP Director of Security Architecture and Standards | Office of the CTO Blue Coat Systems PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050 "Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg." --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: Caution-https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php CLASSIFICATION: UNCLASSIFIED --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]