Vote: Add Release Requirements Policy

2022-05-25 Thread Tomas Mraz
Topic: Add Release Requirements Policy at commit 1845646
   This will become an official OTC policy.
Proposed by: Tomas
Issue link: https://github.com/openssl/technical-policies/pull/40
Public: yes
Opened: 2022-05-25
Closed: 
Accepted:    (for: , against: , abstained: , not voted: )

   Dmitry [  ]
   Matt   [  ]
   Pauli  [  ]
   Tim    [  ]
   Richard    [  ]
   Shane  [  ]
   Tomas  [+1]
   Kurt   [  ]
   Matthias   [  ]
   Nicola [  ]

OTC members, please vote,

-- 
Tomáš Mráz, OpenSSL




Vote: Add Branch Policy

2022-05-25 Thread Tomas Mraz
I am sorry for sending a duplicate mail - this time with the correct
Subject.

Topic: Add Branch Policy at commit 10bea43
   This will become an official OTC policy.
Proposed by: Tomas
Issue link: https://github.com/openssl/technical-policies/pull/7
Public: yes
Opened: 2022-05-25
Closed: 
Accepted:    (for: , against: , abstained: , not voted: )

   Dmitry [  ]
   Matt   [  ]
   Pauli  [  ]
   Tim    [  ]
   Richard    [  ]
   Shane  [  ]
   Tomas  [+1]
   Kurt   [  ]
   Matthias   [  ]
   Nicola [  ]

OTC members, please vote,

-- 
Tomáš Mráz, OpenSSL




Vote: coding-style.md: add various rules on names

2022-05-25 Thread Tomas Mraz
Topic: Add Branch Policy at commit 10bea43
   This will become an official OTC policy.
Proposed by: Tomas
Issue link: https://github.com/openssl/technical-policies/pull/7
Public: yes
Opened: 2022-05-25
Closed: 
Accepted:    (for: , against: , abstained: , not voted: )

   Dmitry [  ]
   Matt   [  ]
   Pauli  [  ]
   Tim    [  ]
   Richard    [  ]
   Shane  [  ]
   Tomas  [+1]
   Kurt   [  ]
   Matthias   [  ]
   Nicola [  ]

OTC members, please vote,

-- 
Tomáš Mráz, OpenSSL




Vote: coding-style.md: add various rules on names

2022-05-25 Thread Tomas Mraz
Topic: coding-style.md: add various rules on names at commit 5a3b1ac
   This will become an official OTC policy.
Proposed by: Tomas
Issue link: https://github.com/openssl/technical-policies/pull/48
Public: yes
Opened: 2022-05-25
Closed: 
Accepted:    (for: , against: , abstained: , not voted: )

   Dmitry [  ]
   Matt   [  ]
   Pauli  [  ]
   Tim    [  ]
   Richard    [  ]
   Shane  [  ]
   Tomas  [+1]
   Kurt   [  ]
   Matthias   [  ]
   Nicola [  ]

OTC members, please vote,

-- 
Tomáš Mráz, OpenSSL




Re: HPKE PR process question

2022-05-25 Thread Stephen Farrell


Hiya,

On 25/05/2022 12:23, Matt Caswell wrote:

Acknowledging receipt of this. We'll get back to you on it.


Thanks. I'm happy to provide further info or be involved
in the discussion if that's useful. An ETA for a substantive
response would also be welcome (e.g. weeks, a month, ...)

Cheers,
S



Matt

On 23/05/2022 22:41, Stephen Farrell wrote:


Hi,

Back in November 2021 (~6 months ago) I created a PR [1]
suggesting an implementation of RFC 9180. In discussion,
the  "need OMC decision" tag was added to the PR on Dec
14th.

Since then, I have heard nothing at all and so far as I
can see, from bits of the openssl-project list archive
that I've checked, the OMC has had no discussion of this
PR at all.

So, now I'm wondering how to make process-progress with
this PR - can you assist or point me at the correct place
to ask? (I can start a thread on openssl-users I guess if
that's better?)

Please note that this is about trying to unblock the
process - the details of HPKE APIs are separate. (I
remain happy to do work to get my code in a shape that
the project likes, but to be honest, 6 months of seeming
process-blockage with no feedback is a tad de-motivating.)

Thanks,
Stephen.

[1] https://github.com/openssl/openssl/pull/17172


OpenPGP_0x5AB2FAF17B172BEA.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Re: HPKE PR process question

2022-05-25 Thread Matt Caswell

Acknowledging receipt of this. We'll get back to you on it.

Matt

On 23/05/2022 22:41, Stephen Farrell wrote:


Hi,

Back in November 2021 (~6 months ago) I created a PR [1]
suggesting an implementation of RFC 9180. In discussion,
the  "need OMC decision" tag was added to the PR on Dec
14th.

Since then, I have heard nothing at all and so far as I
can see, from bits of the openssl-project list archive
that I've checked, the OMC has had no discussion of this
PR at all.

So, now I'm wondering how to make process-progress with
this PR - can you assist or point me at the correct place
to ask? (I can start a thread on openssl-users I guess if
that's better?)

Please note that this is about trying to unblock the
process - the details of HPKE APIs are separate. (I
remain happy to do work to get my code in a shape that
the project likes, but to be honest, 6 months of seeming
process-blockage with no feedback is a tad de-motivating.)

Thanks,
Stephen.

[1] https://github.com/openssl/openssl/pull/17172


OMC VOTE: Update the security policy to include MODERATE issues in prenotifications.

2022-05-25 Thread Mark J Cox
The vote is as shown below.

OMC members should cast their vote here:

https://github.com/openssl/general-policies/pull/21

Mark


Topic: Accept the security policy as of
314ef25aa50e6f0c6a5b026251a06a1c4941e5a2
Proposed by: Mark Cox
Issue link: https://github.com/openssl/general-policies/pull/21
Public: yes
Opened: 2022-05-25
Closed: -MM-DD
Accepted:  yes/no  (for: X, against: Y, abstained: Z, not voted: W)

   Kurt   [  ]
   Mark   [ +1]
   Matt   [  ]
   Pauli  [ +1]
   Richard[  ]
   Tim[  ]