Re: Architecture Working Group License
Jason Keirstead
Let's stick with Apache 2, it protects from patents better.
toggle quoted messageShow quoted text
sfractal --- [EXTERNAL] [oca-pgb] Architecture Working Group License ---
The documentation repo was set up entirely empty. What license should be used, especially for the architecture work? Is the documentation repo just for documentation? If so, I propose CC0 (https://creativecommons.org/share-your-work/public-domain/cc0/). If we think it might contain more than just documentation (ie software), I propose MIT license (https://opensource.org/licenses/MIT). I propose both of these in the spirit of ‘integrate once, reuse everywhere’, ‘open cybersecurity ecosystem where products can freely exchange information, insights, analytics, and orchestrated response’, ‘open source code freely available to the security community’, etc. I recognize others might have started at the other end of the licensing spectrum but I thought I’d start at the ‘most open’ and let everyone else justify adding restrictions.
Duncan Sparrell sFractal Consulting LLC iPhone, iTypo, iApologize I welcome VSRE emails. Learn more at http://vsre.info/
From: <oca-pgb@...> on behalf of "sfractal via Lists.Oasis-Open-Projects.Org" <duncan=sfractal.com@...>
Assuming the “Architecture Working Group” is a team (per previous email), shouldn’t it have it’s own mailing list so I won’t be spamming all of you that don’t care about making the sausage?
Duncan Sparrell sFractal Consulting LLC iPhone, iTypo, iApologize I welcome VSRE emails. Learn more at http://vsre.info/
From: <oca-pgb@...> on behalf of "sfractal via Lists.Oasis-Open-Projects.Org" <duncan=sfractal.com@...>
Thank you. Should the “Architecture Working Group” (I think that was what we got called) also be a ‘team’ and would you please add me (and whoever else volunteered to be a member) to that as well.
Duncan Sparrell sFractal Consulting LLC iPhone, iTypo, iApologize I welcome VSRE emails. Learn more at http://vsre.info/
From: <oca-pgb@...> on behalf of "Jory Burson via Lists.Oasis-Open-Projects.Org" <jory.burson=oasis-open.org@...>
Duncan, I've invited you to the PGB team on GitHub.
We're still missing GitHub usernames for most of our PGB and TSC reps. I would like to populate the TSC and PGB teams on github as that makes permission and member management a lot easier.
The documentation repo doesn't have any content in it so far as I can tell, so that's why you can't fork it. When you join the PGB team you will have write access (as will all other PGB reps) and then you can add a readme and make edits.
Please send along your GitHub Usernames at your convenience. Jory
On Thu, Mar 26, 2020 at 1:26 PM sfractal <duncan@...> wrote:
|
||||||||
|