1 # A record of formal votes in reverse chronological order.
3 # To vote, add one of the following entries next to your name:
5 # [+1] I vote in favour of the proposal
6 # [ 0] I abstain from the vote
7 # [-1] I vote against the proposal
9 # If you are abstaining, you can indicate a tendency as follows:
11 # [+0] I abstain but with a slight lean towards a vote in favour
12 # [ 0] I abstain with no stated preference
13 # [-0] I abstain but with a slight lean towards a vote against
15 # A template for voting (alphabetical by surname) follows.
23 accepted: yes/no (for: X, against: Y, abstained: Z, not voted: T)
38 topic: Accept the OTC voting policy as defined:
40 The proposer of a vote is ultimately responsible for updating the votes.txt
41 file in the repository. Outside of a face to face meeting, voters MUST reply
42 to the vote email indicating their preference and optionally their reasoning.
43 Voters MAY update the votes.txt file in addition.
45 The proposed vote text SHOULD be raised for discussion before calling the vote.
47 Public votes MUST be called on the project list, not the OTC list and the
48 subject MUST begin with “VOTE:”. Private votes MUST be called on the
49 OTC list with “PRIVATE VOTE:” beginning subject.
51 Proposed by Matthias St. Pierre (on behalf of the OTC)
55 accepted: yes/no (for: X, against: Y, abstained: Z, not voted: T)
70 topic: Adopt the coding style policy on function arguments as shown in chapter
71 6.1 of web PR 194 (commit f37f8a9000)
72 Proposed by Matt Caswell
76 accepted: no (for: 2, against: 5, abstained: 2, not voted: 2)
91 topic: Adopt the coding style policy on extending existing functions as shown
92 in chapter 6.2 of web PR 194 (commit f37f8a9000)
93 Proposed by Matt Caswell
97 accepted: yes (for: 5, against: 3, abstained: 2, not voted: 1)
101 Pauli [+1] # Vote changed 2020-09-21
113 topic: The performance improvements provided in PR11188 should be considered a
114 bug fix and therefore acceptable for backport to 1.1.1
115 Proposed by Matt Caswell
119 accepted: no (for: 0, against: 8, abstained: 3, not voted: 0)
135 topic: Rename OSSL_SERIALIZER / OSSL_DESERIALIZER to OSSL_ENCODER / OSSL_DECODER
137 The rationale is that it makes things easier on programmers
138 (encode / decode is easier to write than serialize / deserialize),
139 and also avoids disputes on what is and isn't serialization.
141 Associated issues and PRs: #12455, #12659 and #12660
146 accepted: yes (for: 5, against: 1, abstained: 4, not voted: 1)
154 Shane [-0] # Shane's vote was actually --0
161 topic: Rename OPENSSL_CTX to OSSL_LIB_CTX (as proposed by pull request #12621)
163 The main rationale behind this change is consistency, because many of the new
164 OpenSSL 3.0 types have an OSSL_ prefix, and OPENSSL_CTX is a notable exception.
165 More details can be found in the description and thread of pull request #12621.
167 There was a discussion on openssl-committers ('Rename OPENSSL_CTX to OSSL_WHAT?')
168 and an initial poll on doodle about the favourite replacements for OPENSSL_CTX
169 (https://doodle.com/poll/drku9ziwvkp6tw25).
171 Proposed by Matthias St. Pierre
175 accepted: yes (for: 5, against: 0, abstained: 4, not voted: 2)
190 topic: For change requests which target both the master and the
191 OpenSSL_1_1_1-stable branch, the following procedure should be followed:
192 - First, a pull request needs to be opened against the master branch for
193 discussion. Only after that pull request has received the necessary
194 amount of approvals, a separate pull request can be opened against the
195 OpenSSL_1_1_1-stable branch.
196 - A separate pull request against the OpenSSL_1_1_1-stable branch is
197 required. This holds - contrary to common practice - even if the change
198 can be cherry-picked without conflicts from the master branch. The only
199 exception from this rule are changes which are considered 'CLA: trivial',
200 like e.g. typographical fixes.
201 Proposed by Matt Caswell
205 accepted: no (for: 4, against: 4, abstained: 3, not voted: 0)
221 topic: Accept and merge #11577.
222 comment: #11577 reduces the maximum length of TLS labels.
223 It also breaks standards compliance.
228 accepted: no (for: 0, against: 9, abstained: 1, not voted: 1)
238 Kurt [-1] # 2020-06-09
243 topic: Keep FIPS_mode() as emulated by EVP_default_properties_is_fips_enabled(NULL)
244 Proposed by Tomas Mraz
248 accepted: no (for: 2, against: 5, abstained: 3, not voted: 1)
263 topic: approve PR#8300 statem: fix the alert sent for too large messages
264 Proposed by Tim Hudson
268 accepted: no (for: 1, against: 4, abstained: 6, not voted: 0)