[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-stix] Timestamps - Proposal
That is the approach we outlined and agreed to.
How is that bad form?
We need to be able to track issues from identification through discussion to solution proposal to consensus being reached to actually incorporating the changes within a release. And have a traceable record of all of this.
Github issue trackers are designed for just this sort of process.
I think the point is that the issues should have ideally been created back when the discussion on this started rather than just capturing everything after the fact.
sean
From: "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org> on behalf of "Jordan, Bret" <bret.jordan@bluecoat.com>
Date: Thursday, December 3, 2015 at 2:38 PM To: John Wunder <jwunder@mitre.org> Cc: "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org> Subject: Re: [cti-stix] Timestamps - Proposal
We should NOT use Github Issues for things we have decided on. That is bad form.
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."
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]