The SCAPv2 working group has made some minor revisions and clarifications to the project proposal, the latest version is attached. We will be going over this on the call today along with the working g

At the PGB meeting next week, we are happy to invite members from the SCAPv2 community to discuss their proposal for a new OCA project. They will have a short overview of SCAPv2 and we will be able to

Please accept this recurring monthly meeting, and decline only individual months after. Agenda will be sent prior to the call.

Hello everyone. I have a conflict and will be unable to host the PGB call next week. As well, Darren is on paternity leave. I have posted a poll in the PGB slack channel and request people respond to

Dear PGB Members As discussed on the previous call we are looking at ways to drive forward the goals of the OCA and have created workstreams with the expressed purpose of accelerating the OpenDXL Onto

Thanks Duncan, you have some good ones here. License definitely needs to be here in the template. I am not sure we need to ask them if it is open source software, since it's a base requirement, but ma

Basically - I am trying to make a template that a new project can fill out, to submit to the PGB, so the PGB can take on a decision on onboarding a project. Recognizing that it can't boil the ocean an

TSC & PGB members; To date we have not received any comments at all on the below onboarding template. I want to remind the group that we have *two potential new projects* waiting in the queue to move

I think once we as a group decide this is the template, then we would post public. - Jason Keirstead Chief Architect - IBM Security Threat Management www.ibm.com/security Co-Chair - Open Cybersecurity

Below is the template onboardinng proposal document filled for ArkAngel. As a reminder the idea is to try to create a template document that captures the evaluation criterion that we want to capture f

Hello folks; we have a solid agenda for the meeting tomorrow, with a bunch of key items to cover. Here are the planned topics. If anyone has other items to discuss please raise them to the group so we

I see no reason it has to be private. - 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, r

It was meant to to be the "we" of OCA - as in, if we do not have our own, we should be using the standard templates, until such a time where if and when we decide to embark on creating our own Code of

I can attest that when contributing an IBM OSS project to the Linux Foundation, we specify that the code is Apache 2.0, but the documentation is Creative Commons Attribution 4.0 International License

Agree Adam - if this folder only contains documentation we should be using a CC license. - Jason Keirstead Chief Architect - IBM Security Threat Management www.ibm.com/security "Would you like me to g

It's the former. The Apache 2 license contains an explicit patent grant which means that if you contribute code to the project you are granting rights to any patents you have on that code. It is why m

Let's stick with Apache 2, it protects from patents better. sfractal --- [EXTERNAL] [oca-pgb] Architecture Working Group License -

FYI there are standard OASIS templates for these, and we are using them in the projects Code of conduct (this is linked from ours) https://github.com/oasis-open-projects/documentation/blob/master/CODE

Hello fellow OCA members; As you may have heard if you have been attending the marketing subcommittee calls, the response to our RSA outreach event to the public next week has been spectacular, with u