Collective Code Construction Contract (C4) & Code of Conduct


duncan@sfractal
 

On PGB call, we discussed having contributor guidelines (ie getting TSC to make them) on all OCA projects and https://rfc.zeromq.org/spec/42/ is another common one it seems projects use.

I think the better open source projects also include a code of conduct. A good one that is reusable is at https://www.contributor-covenant.org

 

Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

I welcome VSRE emails. Learn more at http://vsre.info/

 

._,_._,_


Darren Thomas <Darren_Thomas@...>
 

Thank you Duncan - very useful. 

Darren 


On Mar 26, 2020, at 10:20 AM, sfractal via Lists.Oasis-Open-Projects.Org <duncan=sfractal.com@...> wrote:



CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.



On PGB call, we discussed having contributor guidelines (ie getting TSC to make them) on all OCA projects and https://rfc.zeromq.org/spec/42/ is another common one it seems projects use.

I think the better open source projects also include a code of conduct. A good one that is reusable is at https://www.contributor-covenant.org

 

Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

I welcome VSRE emails. Learn more at http://vsre.info/

 

._,_._,_


Jason Keirstead
 

FYI there are standard OASIS templates for these, and we are using them in the projects

Code of conduct (this is linked from ours)
 
 
 
 
Contributing guidelines - these assume you already know how contributions on Github work. We could flesh out more in case you don't.
 
 
-
Jason Keirstead
Chief Architect - IBM Security Threat Management
www.ibm.com/security

"Would you like me to give you a formula for success? It's quite simple, really. Double your rate of failure."

- Thomas J. Watson
 
 

----- Original message -----
From: "sfractal" <duncan@...>
Sent by: oca-pgb@...
To: "oca-pgb@..." <oca-pgb@...>, oca-tsc <oca-tsc@...>
Cc:
Subject: [EXTERNAL] [oca-pgb] Collective Code Construction Contract (C4) & Code of Conduct
Date: Thu, Mar 26, 2020 2:19 PM
 

On PGB call, we discussed having contributor guidelines (ie getting TSC to make them) on all OCA projects and https://rfc.zeromq.org/spec/42/ is another common one it seems projects use.

I think the better open source projects also include a code of conduct. A good one that is reusable is at https://www.contributor-covenant.org

 

Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

I welcome VSRE emails. Learn more at http://vsre.info/

 

._,_._,_

 


duncan@sfractal
 

Jason,

Is your ‘we’ the royal ‘we’ (ie all of OCA) or just the IBM piece?

Admittedly I only had been looking on https://github.com/opencybersecurityalliance/opendxl-ontology and I’ve now found them on https://github.com/opencybersecurityalliance/stix-shifter/blob/master/CONTRIBUTING.md but not obvious to me where they are on opendl-ontology.

I do think we need to think of OCA as a whole not just an IBM repo and a McAfee repo, and the chairs both need to chair the whole org, not just their company’s part – otherwise we’ll always have ‘company parts’.

Sorry to be harsh but it’s been a very long day. Take it in the spirit of ‘in the future you might consider’.

And huge apology if you were speaking for both and I’m just braindead and can’t find on opendxl-ontology.

 

Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

I welcome VSRE emails. Learn more at http://vsre.info/

 

 

From: <oca-pgb@...> on behalf of "Jason Keirstead via Lists.Oasis-Open-Projects.Org" <Jason.Keirstead=ca.ibm.com@...>
Reply-To: "oca-pgb@..." <oca-pgb@...>
Date: Thursday, March 26, 2020 at 1:31 PM
To: "oca-pgb@..." <oca-pgb@...>
Cc: "oca-pgb@..." <oca-pgb@...>, oca-tsc <oca-tsc@...>
Subject: Re: [oca-pgb] Collective Code Construction Contract (C4) & Code of Conduct

 

FYI there are standard OASIS templates for these, and we are using them in the projects


Code of conduct (this is linked from ours)

 

 

 

 

Contributing guidelines - these assume you already know how contributions on Github work. We could flesh out more in case you don't.

 

 

-
Jason Keirstead
Chief Architect - IBM Security Threat Management
www.ibm.com/security

"Would you like me to give you a formula for success? It's quite simple, really. Double your rate of failure."

- Thomas J. Watson

 

 

----- Original message -----
From: "sfractal" <duncan@...>
Sent by: oca-pgb@...
To: "oca-pgb@..." <oca-pgb@...>, oca-tsc <oca-tsc@...>
Cc:
Subject: [EXTERNAL] [oca-pgb] Collective Code Construction Contract (C4) & Code of Conduct
Date: Thu, Mar 26, 2020 2:19 PM
 

On PGB call, we discussed having contributor guidelines (ie getting TSC to make them) on all OCA projects and https://rfc.zeromq.org/spec/42/ is another common one it seems projects use.

I think the better open source projects also include a code of conduct. A good one that is reusable is at https://www.contributor-covenant.org

 

Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

I welcome VSRE emails. Learn more at http://vsre.info/

 

._,_._,_