This GitHub public repository openc2-oif-obo was created at the request of the OASIS Open Command and Control (OpenC2) TC as an OASIS TC Open Repository to support development of open source resources related to Technical Committee work.
While this TC Open Repository remains associated with the sponsor TC, its development priorities, leadership, intellectual property terms, participation rules, and other matters of governance are separate and distinct from the OASIS TC Process and related policies.
All contributions made to this TC Open Repository are subject to open source license terms expressed in Apache-2.0 license. That license was selected as the declared Applicable License when the TC voted to create this Open Repository.
As documented in Public Participation Invited, contributions to this TC Open Repository are invited from all parties, whether affiliated with OASIS or not. Participants must have a GitHub account, but no fees or OASIS membership obligations are required. Participation is expected to be consistent with the OASIS TC Open Repository Guidelines and Procedures, the open source LICENSE.md designated for this particular repository, and the requirement for an Individual Contributor License Agreement that governs intellectual property.
This repository supports implementation of an OpenC2 Integration Framework (OIF) family product that can be configured as an intermediate producer-consumer; this product will be called the OIF Bridge Orchestrator (OBO).
Many OpenC2 use cases involve a Producer interacting with a Consumer that in turn manages subordinate devices. While such a Consumer can be achieved with an amalgamation of an OIF-Device and an OIF-Orchestrator, having a tool designed to utilize OIF for this purpose will allow this tool to receive individual focus and updates tailored for its specific role. Current OIF-Orchestrator implementations require user-facing features such as a GUI that are unnecessary in many intermediate implementations and require using tools from a variety of repositories to create one effective intermediate device. This open repository serves to focus that work.
TC Open Repository maintainers are responsible for oversight of this project's community development activities, including evaluation of GitHub pull requests and preserving open source principles of openness and fairness. Maintainers are recognized and trusted experts who serve to implement community goals and consensus design preferences.
Initially, the associated TC members have designated one or more persons to serve as Maintainer(s); subsequently, participating community members may select additional or substitute Maintainers, per consensus agreements.
Current Maintainers of this TC Open Repository
-
David Lemire, [email protected], dlemire60, National Security Agency
-
David Kemp, [email protected], davaya, National Security Agency
- TC Open Repositories: Overview and Resources
- TC Open Repositories: Overview and Resources
- Open Source Licenses
- Contributor License Agreements (CLAs)
- Maintainers Guidelines and Agreement
Questions or comments about this TC Open Repository's activities should be composed as GitHub issues or comments. If use of an issue/comment is not possible or appropriate, questions may be directed by email to the Maintainer(s) listed above. Please send general questions about TC Open Repository participation to OASIS Staff at [email protected] and any specific CLA-related questions to [email protected].