3 <!--#include virtual="/inc/head.shtml" -->
6 <!--#include virtual="/inc/banner.shtml" -->
10 <div class="blog-index">
13 <h2>OpenSSL Bylaws</h2>
15 First issued 13th February 2017<br/>
16 Last modified 10th December 2019
20 <div class="entry-content">
22 <p>This document defines the bylaws under which the OpenSSL Project
23 operates. It defines the different project roles, how they contribute
24 to the project, and how project decisions are made.</p>
26 <h2>Roles and Responsibilities</h2>
30 <p>Users include any individual or organisation that downloads,
31 installs, compiles, or uses the OpenSSL command line applications or
32 the OpenSSL libraries or the OpenSSL documentation. This includes
33 OpenSSL-based derivatives such as patched versions of OpenSSL provided
34 through OS distributions, often known as "downstream" versions.</p>
36 <p>Users may request help and assistance from the project through any
37 appropriate forum as designated by the OpenSSL Management Committee
38 (OMC). Users may also report bugs, issues, or feature requests; or
39 make pull requests through any OMC designated channel.</p>
41 <h3><a name="committers">Committers</a></h3>
43 <p>Committers have the ability to make new commits to the main OpenSSL
44 Project repository. Collectively, they have the responsibility for
45 maintaining the contents of that repository. They must ensure that any
46 committed contributions are consistent with all appropriate OpenSSL
47 policies and procedures as defined by the OMC.</p>
49 <p>Committers also have a responsibility to review code submissions in
50 accordance with OpenSSL project policies and procedures.</p>
52 <p>Commit access is granted as a result of a vote by the OMC. It may
53 be withdrawn at any time by a vote of the OMC.</p>
55 <p>A condition of commit access is that the committer has signed an
56 Individual Contributor Licence Agreement (ICLA). If contributions may
57 also be from the employer of an individual with commit access then a
58 Corporate Contributor Licence Agreement (CCLA) must also be signed and
59 include the name of the committer.</p>
61 <p>In order to retain commit access a committer must have authored or
62 reviewed at least one commit within the previous two calendar
63 quarters. This will be checked at the beginning of each calendar
64 quarter. This rule does not apply if the committer first received
65 their commit access during the previous calendar quarter.</p>
67 <h3><a name="OMC">OpenSSL Management Committee (OMC)</a></h3>
69 <p>The OMC represents the official voice of the project. All official
70 OMC decisions are taken on the basis of a vote.</p>
74 <li>makes all decisions regarding management and strategic direction
75 of the project; including:
77 <li>business requirements;</li>
78 <li>feature requirements;</li>
79 <li>platform requirements;</li>
80 <li>roadmap requirements and priority;</li>
81 <li>end-of-life decisions;</li>
82 <li>release timing and requirement decisions;</li>
85 <li>maintains the project infrastructure;</li>
86 <li>maintains the project website;</li>
87 <li>maintains the project code of conduct;</li>
88 <li>sets and maintains all project Bylaws;</li>
89 <li>sets and maintains all non-technical policies and non-technical procedures;</li>
90 <li>nominates and elects OMC members as required;</li>
91 <li>approves or rejects OTC nominations for committers and OTC members;</li>
92 <li>adds or removes OMC, OTC, or committers as required;</li>
93 <li>adjudicates any objections to OTC decisions;</li>
94 <li>adjudicates any objections to any commits to project repositories;</li>
95 <li>ensures security issues are dealt with in an appropriate
97 <li>schedules releases and determines future release plans and the
98 development roadmap and priorities;</li>
99 <li>maintains all other repositories according to the policies and
100 procedures they define.</li>
103 <p>Membership of the OMC is by invitation only from the existing OMC
104 following a passing vote. OMC members may or may not be committers as
105 well. If an OMC member is also a committer then all rules that apply
106 to committers still apply.</p>
108 <p>The OMC makes decisions on behalf of the project. In order to have
109 a valid voice on the OMC, members must be actively contributing to the
110 project. Note that there are many ways to contribute to the project
111 but the ones that count in order to participate in the OMC
112 decision-making process are the ones listed below.</p>
114 <p>In general, the OMC will leave technical decisions to the OpenSSL
115 Technical Committee (OTC, see below) and not participate in
116 discussions related to development and documention of the OpenSSL
117 Toolkit. In exceptional cases however an OTC vote can be overruled
118 by an OMC vote. Such an exceptional case would be for example if an
119 OTC decision stands contrary to OMC policies or decisions.</p>
121 <p>OMC members may become inactive. In order to remain active a member
122 must, in any calendar quarter, contribute by:</p>
124 <li>a) Having authored, or been recorded as a reviewer of, at least
125 one commit made to any OpenSSL repository (including non-code based
127 <li>b) vote in at least two-thirds of the OMC votes closed in the
128 first two months of the quarter and the last month of the preceding
132 <p>The above rules will be applied at the beginning of each calender
133 quarter. It does not apply if the OMC member was first appointed, or
134 became active again during the previous calendar quarter. The voting
135 requirement only includes those votes after the time the member joined
136 or was made active again.</p>
138 <p>If an OMC member remains inactive for one calendar quarter then
139 they will no longer be considered an OMC member, but will be listed as
140 an OMC Alumni. OMC Alumni have no access to OMC internal resources
141 (including email lists) but may request a vote at any time to
142 reinstate their membership in the OMC.</p>
144 <p>Any OMC member can propose a vote to declare another member
145 inactive or remove them from OMC membership entirely.</p>
147 <p>An OMC member can declare themselves inactive, leave the OMC, or
148 leave the project entirely. This does not require a vote.</p>
150 <p>An inactive OMC member can propose a vote that the OMC declare them
151 active again. Inactive OMC members cannot vote but can propose issues
152 to vote on and participate in discussions. They retain access to OMC
153 internal resources.</p>
155 <h4><a name="omc-voting">OMC Voting Procedures</a></h4>
157 <p>A vote to change these bylaws will pass if it obtains an in favour
158 vote by more than two thirds of the active OMC members and less than
159 one quarter votes against by the active OMC members. A vote that does
160 not change these bylaws will pass if it has had a vote registered from
161 a majority of active OMC members and has had more votes registered in
162 favour than votes registered against.</p>
164 <p>Only active OMC members may vote. A registered vote is a vote in
165 favour, a vote against, or an abstention.</p>
167 <p>Any OMC member (active or inactive) can propose a vote. OMC Alumni
168 may only propose a vote to reinstate themselves to the OMC. Each vote
169 must include a closing date which must be between seven and fourteen
170 calendar days after the start of the vote. Votes to change these
171 bylaws must be fourteen calendar days in duration.</p>
173 <p>In exceptional cases, the closing date for non-bylaw changing votes
174 could be less than seven calendar days; for example, a critical issue
175 that needs rapid action. A critical issue is hard to define precisely
176 but would include cases where a security fix is needed and the details
177 will soon be made public. At least one other active OMC member besides
178 the proposer needs to agree to the shorter timescale.</p>
180 <p>A vote closes on its specified date. In addition, any active OMC
181 member can declare a vote closed once the number of uncast votes could
182 not affect the outcome. Any active OMC member may change their vote up
183 until the vote is closed. No vote already cast can be changed after
184 the vote is closed. Votes may continue to be cast and recorded after a
185 vote is closed up until fourteen days after the start of the vote.
186 These votes will count for the purposes of determining OMC member
187 activity, but will otherwise not affect the outcome of the vote.</p>
189 <p>All votes and their outcomes should be recorded and available to
192 <h3><a name="OTC">OpenSSL Technical Committee (OTC)</a></h3>
194 <p>The OTC represents the official technical voice of the project. All
195 OTC decisions are taken on the basis of a vote.</p>
199 <li>makes all technical decisions of the code and documentation for OpenSSL including:
202 <li>architecture;</li>
203 <li>implementation;</li>
205 <li>documentation;</li>
206 <li>code review;</li>
207 <li>quality assurance;</li>
208 <li>classification of security issues in accordance with the security policy;</li>
212 <li>produces releases according to OMC requirements;</li>
213 <li>establishes and maintains technical policies and technical procedures such as:
215 <li>GitHub labels and milestone usage;</li>
216 <li>coding style;</li>
219 <li>nominates to the OMC, addition or removal of OTC members and committers;</li>
220 <li>ensures technical aspects of security issues are dealt with in an appropriate
224 <p>Membership of the OTC is by invitation only from the OMC.
225 OTC members must be committers and hence all rules that apply to committers also apply.
226 OTC members may be OMC members and in which case all rules that apply to OMC members
229 <p>The OTC makes technical decisions on behalf of the project based on
230 requirements specified by the OMC. In order to have
231 a valid voice on the OTC, members must be actively contributing to the
232 technical aspects of the project. Note that there are many ways to contribute to the project
233 but the ones that count in order to participate in the OTC
234 decision-making process are the ones listed below.</p>
236 <p>OTC members may become inactive. In order to remain active a member
237 must, in any calendar quarter, contribute by:</p>
239 <li>a) Having authored, or been recorded as a reviewer of, at least
240 one commit made to any OpenSSL repository (including non-code based
242 <li>b) vote in at least two-thirds of the OTC votes closed in the
243 first two months of the quarter and the last month of the preceding
245 <li>c) maintain committer status.</li>
248 <p>The above rules will be applied at the beginning of each calender
249 quarter. It does not apply if the OTC member was first appointed, or
250 became active again during the previous calendar quarter. The voting
251 requirement only includes those votes after the time the member joined
252 or was made active again.</p>
254 <p>If an OTC member remains inactive for one calendar quarter then
255 they will no longer be considered an OTC member.</p>
257 <p>An OTC member can declare themselves inactive, leave the OTC, or
258 leave the project entirely. This does not require a vote.</p>
260 <p>An inactive OTC member can propose a vote that the OTC declare them
261 active again. Inactive OTC members cannot vote but can propose issues
262 to vote on and participate in discussions. They retain access to OTC
263 internal resources.</p>
265 <h4><a name="otc-voting">OTC Voting Procedures</a></h4>
267 <p>A vote will pass if it has had a vote registered from
268 a majority of active OTC members and has had more votes registered in
269 favour than votes registered against.</p>
271 <p>Only active OTC members may vote. A registered vote is a vote in
272 favour, a vote against, or an abstention.</p>
274 <p>Any OTC member (active or inactive) can propose a vote.
275 Each vote must include a closing date which must be between seven and fourteen
276 calendar days after the start of the vote. </p>
278 <p>In exceptional cases, the closing date
279 could be less than seven calendar days; for example, a critical issue
280 that needs rapid action. A critical issue is hard to define precisely
281 but would include cases where a security fix is needed and the details
282 will soon be made public. At least one other active OTC member besides
283 the proposer needs to agree to the shorter timescale.</p>
285 <p>A vote closes on its specified date. In addition, any active OTC
286 member can declare a vote closed once the number of uncast votes could
287 not affect the outcome. Any active OTC member may change their vote up
288 until the vote is closed. No vote already cast can be changed after
289 the vote is closed. Votes may continue to be cast and recorded after a
290 vote is closed up until fourteen days after the start of the vote.
291 These votes will count for the purposes of determining OTC member
292 activity, but will otherwise not affect the outcome of the vote.</p>
294 <p>All votes and their outcomes should be recorded and available to
295 all OTC and OMC members.</p>
297 <h4><a name="otc-transparency">OTC Transparency</a></h4>
299 The majority of the activity of the OTC will take place in public.
300 Non-public discussions or votes shall only occur for issues such as:
302 <li>pre-disclosure security problems</li>
303 <li>pre-agreement discussions with third parties that require confidentiality</li>
304 <li>nominees for OTC or committer roles</li>
305 <li>personal conflicts among project personnel</li>
309 <p>Full details (topic, dates, voting members, specific votes cast, vote result) of
310 all public votes shall be made available in a public repository.</p>
312 <h3>OpenSSL Software Foundation (OSF)</h3>
314 <p>The OpenSSL Software Foundation represents the OpenSSL project in
315 legal and most official formal capacities in relation to external
316 entities and individuals. This includes, but is not limited to,
317 managing contributor license agreements, managing donations,
318 registering and holding trademarks, registering and holding domain
319 names, obtaining external legal advice, and so on.</p>
321 <p>Any OMC member may serve as a director of OSF if they wish. To do
322 so they should send a request to any existing OSF director.</p>
324 <h3>OpenSSL Software Services (OSS)</h3>
326 <p>OpenSSL Software Services represents the OpenSSL project for most
327 commercial and quasi-commercial contexts, such as providing formal
328 support contracts and brokering consulting contracts for OpenSSL
331 <p>Any OMC member may serve as a director of OSS if they wish, subject
332 to certain contractual requirements. To do so they should send a
333 request to any existing OSS director.</p>
336 <h2><a name="leave">Leave of absence</a></h2>
338 <p>An active OMC member, OTC member, or committer may request a leave of absence
339 from the project. A leave of absence from the OMC, OTC or committer shall
340 suspend inactivity determination for the specified role. All access to
341 OMC, OTC or committer resources shall be suspended (disabled) and the OMC
342 or OTC member shall be excluded from voting and the committer shall be excluded
343 from reviewing or approving source changes. On return from a leave of
344 absence, the OMC or OTC member or committer will be deemed to have become active
345 as of the date of return.</p>
347 <p>All of the following criteria must be met in order to qualify as a
348 leave of absence:</p>
350 <li>a) the member must request via email to the OMC a leave of
351 absence at least one week in advance of the requested
352 period of leave;</li>
353 <li>b) only one leave of absence is permitted per calendar year;</li>
354 <li>c) the leave of absence must specify the date of return from
355 the leave of absence; </li>
356 <li>d) the length of the leave of absence shall be a minimum of one calendar
357 month and shall not exceed three calendar months (one quarter); and </li>
358 <li>e) the leave of absence applies to all the roles within the
359 project (i.e. OMC, OTC and committer if all three roles apply).</li>
362 <h2><a name="update">Bylaws Update History</a></h2>
364 The following changes have been made since the bylaws were first
365 issued 13-February-2017.
368 <li>21-November-2019.
369 Added <i>OTC</i>. and other related changes.</li>
370 <li>20-December-2017.
371 Added <i>Leave of absence</i> section.</li>
376 You are here: <a href="/">Home</a>
377 : <a href="/policies">Policies</a>
378 : <a href="">Bylaws</a>
379 <br/><a href="/sitemap.txt">Sitemap</a>
383 <!--#include virtual="sidebar.shtml" -->
387 <!--#include virtual="/inc/footer.shtml" -->