The OCA PGB welcomes suggestions for new subprojects. To submit your idea, please complete the template below and email it as an attachment to the OCA PGB mailing list.
There are no formal guidelines for project names in the OCA, we suggest a name that is either memorable and/or evokes the project goals
Please descripe the project's value in one sentence. "The FooBar project is an open-source python library that helps connect Foo to Bar in order to detect threats"
Give a more detailed description. "The FooBar project connects Foo to Bar using magic beans. These magic beans allow threat information to be shared in a high-fidelity way, and can be used in a Kestrel analytic. By doing this, FooBar lets users save the day.
Project contribution to OCA goals and mission
See also: OCA Charter
Why the OCA vs. the OpenSSF, IETF, CSA, etc?
Are you hoping to attract more developers? End users? Architecture collaboration?
More than one link is OK if the project has multiple homes
STIX, OpenC2, CACAO, SARIF, CSAF, Kestrel, STIX-Shifter...
Please see list of applicable licenses
Python, Go, Rust, JSON, YAML....
Links to any significant dependancy technologies. You do not have to link to every library a project depends on, only major ones.
Dependancy technologies should normally be available under an open-source license that is compatible with the proposed license of the project. If you need help in validating this compatibility, we are happy to assist you. If a dependancy technology is not open-source, please explain in detail how this will be mitigated for project consumers and collaborators.
The project should have at least one sponsor that is either be an OCA sponsor and PGB member, or a prospective sponsor/member.
To avoid "zombie" projects, new projects must have a viable plan on how they will be resourced - either from a combination of the sponsors, or some other external contribution plan.