Alliance open-source products
An Alliance open-source product is a software component or system the Alliance publishes to help companies use AES70, the Audio Engineering Society's OCA standard for audio device control and monitoring over networks.
Going forward, the Alliance will offer a growing number of open-source products to assist AES70 evaluation, experimentation, education, demonstration, and commercial implementation.
Finding Alliance open-source products
Alliance open-source products are listed in various entries of the Downloads section of this website.
Physically, Alliance open-source products are in GitHub repositories that reside in subfolders of the OCA Alliance's Github site, ocaalliance.Github.io.
Using Alliance open-source products
Alliance open-source products produced in 2024 or later are normally licensed under the Apache 2.0 license. For complete licensing details, please go to Licensing Details below.
Contributing to Alliance open-source projects
Contributions to Alliance open-source projects are welcome. To make a contribution, the contributor posts a Git Pull request to the product's GitHub repository. Once the repository manager approves it, the Pull request's content will be merged into the project.
To fulfill legal requirements, Pull request comments must include specific text. See Licensing Details below.
Technical Details
Open-source repository structure
All Alliance open-source repositories have the following base folder set:
Folder or File Contents ---------------------------------------------- [component 1]/ component (1) code ... [component n]/ component (n) code License/ copy of Apache 2.0 license Documents/ product documentation README.md readme file - see next
README file
In addition to product-specific information, every README file contains the standard Alliance licensing text. The standard content (Markdown format) is here.
License declarations
Every source file in an Alliance open-source product must include the standard boilerplate license declaration, entered in the appropriate comment syntax for the file's format. The required text (plain text format) is here .
Licensing Details
The Alliance uses the Apache Foundation license, Version 2.0, which covers a wide range of intellectual-property issues, including patent rights. Apache licenses do not have copy-left requirements, and are widely accepted for commercial use.
A copy of this license, including instructions for use, is on the Apache website, here:
A clean copy of the license text is here:
This license does not require signatures. Any OCA open-source product may be used without executing an agreement. However, by using such a product, the user implicitly accepts the terms of this license.
Contributing to an open-source project
Anyone may contribute to an Alliance open source project by submitting a Git Pull request to the project's repository. No prior authorization is required. However, to fulfill legal requirements, the comments field of every submitted Pull request must contain a brief text that certifies the contributed content complies with the terms of the Developer's Certificate of Origin (DCO), a simple document written by the Linux Foundation that attests the contributor has sufficient rights to make the contribution.
Pull requests without DCO certifications will not be accepted by the Repository Manager, and should be resubmitted with certification included.
The required text is as follows:
<Submitter's full name and email>
Note that the submitter's name and email must be provided. This text is also given in the Readme file of every Alliance repository.