-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathopensource.html
More file actions
196 lines (174 loc) · 6.84 KB
/
opensource.html
File metadata and controls
196 lines (174 loc) · 6.84 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
<!DOCTYPE html>
<!-- format2025 -->
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>OCA Techsite: Open Source Guidelines</title>
<link rel=stylesheet type='text/css' href='css/screen.css' media='screen'/>
<link href="https://fonts.googleapis.com/css2?family=Encode+Sans:wght@100..900&display=swap" rel="stylesheet">
<script src='js/script.js' ></script>
</head>
<body>
<table>
<col width='15%'>
<col>
<tbody>
<tr>
<td>
<a href='index.html'>
<img src='images/OCA-Logo-300.png.webp' width='130px' height='60px' alt='OCA Alliance Logo'/>
</a>
</td>
<td class=topnav>
<ul>
<li><a href='aes70.html'>AES70 Standard</a></li>
<li><a href='repositories.html'>Repositories</a></li>
<li><a href='downloads.html'>Downloads</a></li>
<li><a href='information.html'>Information</a></li>
<li><a href='opensource.html'>Open‑Source Guidelines</a></li>
</ul>
</td>
</tr>
</tbody>
</table>
<div class='banner'>
<div class='title'>
<h1>Open-Source Software Guidelines</h1>
</div>
</div>
<div class=content>
This page is a guide for users of and contributors to OCA Alliance
open-source software.
</p>
<h2>Alliance open-source products </h2>
<p>
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.
</p>
<p>
Going forward, the Alliance will offer a growing number of open-source products to
assist AES70 evaluation, experimentation, education, demonstration, and commercial
implementation.
</p>
<h3> Finding Alliance open-source products</h3>
<p>
Alliance open-source products are listed in various entries of the
<a href="downloads.html" target="_blank"> Downloads</a> section of this website.
</p>
<p> Physically, Alliance open-source products are in GitHub repositories that reside in
subfolders of the OCA Alliance's Github site,
<a href="https://ocaalliance.Github.io/" target="_blank">ocaalliance.Github.io</a>.
</p>
<h3> Using Alliance open-source products </h3>
<p>
Alliance open-source products produced in 2024 or later are normally licensed under the
<a href="http://www.apache.org/licenses/LICENSE-2.0" target="_blank">Apache 2.0 license</a>.
For complete licensing details, please go to
<a href =#Licensing>Licensing Details</a> below.
</p>
<h3> Contributing to Alliance open-source projects </h3>
<p>
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.
</p>
<p>
To fulfill legal requirements, Pull request comments must include specific text.
See <a href="#Licensing">Licensing Details</a> below.
</p>
<h2> Technical Details </h2>
<h3> Open-source repository structure </h3>
<p class='tight'>
All Alliance open-source repositories have the following base folder set:
</p>
<div class="in">
<pre class='code'>
<b>Folder or File Contents </b>
----------------------------------------------
[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
</pre>
</div>
<h3>README file</h3>
<p class="tight">
In addition to product-specific information,
every README file contains the standard Alliance licensing text.
The standard content (Markdown format) is
<a href="licensing/LicenseInfo-Readme.md" target="-blank">here</a>.
</p>
<h3> License declarations </h3>
<p>
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
<a href="licensing/LicenseInfo-Code.txt" target="_blank">
here
</a>.
</p>
<h2 id="Licensing"> Licensing Details </h2>
<p>
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 <b>not</b> have copy-left requirements, and are widely accepted
for commercial use.
</p>
<p>
A copy of this license, including instructions for use, is on the Apache website, here:
</p>
<div class="in">
<a href="http://www.apache.org/licenses/LICENSE-2.0" target="_blank">
http://www.apache.org/licenses/LICENSE-2.0
</a>
</div>
<p>
A clean copy of the license text is here:
</p>
<div class="in">
<a href="licensing/Apache License v2.0.pdf" target="_blank">
https://ocaalliance.Github.io/licensing/Apache License v2.0.pdf
</a>
</div>
<p>
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.
</p>
<h3>Contributing to an open-source project</h3>
<p>
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
<b><a href="https://developercertificate.org/">Developer's Certificate of Origin (DCO)</a></b>,
a simple document written by the Linux Foundation that attests the contributor
has sufficient rights to make the contribution.
</p>
<p>
Pull requests without DCO certifications will not be accepted by the Repository Manager,
and should be resubmitted with certification included.
</p>
<p>
The required text is as follows:
</p>
<div class="in">
<font face="Courier New" color='#000064'><b>
The entire content of this Pull request complies with
the Linux Developer Certificate of Origin, the text of which is at
https://developercertificate.org/. <br />
<Submitter's full name and email>
</font></b>
</div>
<p>
Note that the submitter's name and email must be provided.
This text is also given in the Readme file of every Alliance repository.
</div>
</body>
</html>