Re: [openssl-project] Alpha release coverage on The Register

2018-02-14 Thread Dr. Matthias St. Pierre
Am 14.02.2018 um 23:28 schrieb Tim Hudson:
> http://www.theregister.co.uk/2018/02/14/openssl_1_1_1_alpha_adds_tls_1_3_support/
>
>
> Note that the headline "Shambling corpse of ancient, shoddy, buggy,
> crypto shoved towards the grave" is referring to TLS protocol versions
> not to OpenSSL (at least that is my reading of the article) but as
> always The Register does like snappy headlines. 
>
> It could do with a pointing out the timeline on TLSv1.3 support in
> OpenSSL ... 
>
> Tim.
>

Thanks for the Link! After all, the article is much more positive than
the subtitle suggests. Personally, I very much enjoyed seeing the "grand
redesign" in double quotes ;-)

Matthias


___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project


Re: [openssl-project] VOTE on travel reimbursement policy

2018-02-14 Thread Tim Hudson
[kurt]
> So I think we should either all vote in public, or nobody should vote in
public.

You make a good point there - I agree.

Tim.
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project

Re: [openssl-project] VOTE on travel reimbursement policy

2018-02-14 Thread Kurt Roeckx
On Wed, Feb 14, 2018 at 10:40:29PM +0100, Richard Levitte wrote:
> In message <20180214212414.ga13...@roeckx.be> on Wed, 14 Feb 2018 22:24:14 
> +0100, Kurt Roeckx  said:
> 
> kurt> The call for votes should probably also not go to the project list
> kurt> based on that current rules say that we vote on the omc list
> kurt> afaik.
> 
> This is exactly contrary to what we agreed on at the last f2f, apart
> from *certain* votes (such as invitation of new people).

I think that what we agreed to is that the text to vote on should
be discussed on the project list before the vote, and that the
vote should happen on the omc list. Since the vote happens on the
omc list, I see no reason to send the call for votes to the
project list, I only see it as confusing.

Note that I have no problem with voting in public, but then
everybody should vote in public. If some people vote in public and
others don't, the summary might give enough information about what
the others voted. So I think we should either all vote in public,
or nobody should vote in public.


Kurt

___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project


Re: [openssl-project] VOTE on travel reimbursement policy

2018-02-14 Thread Tim Hudson
> Now, the initial posting went to both the OMC and the project list,
> and some chose to vote with a simple "Reply All" without editing the
> recipients.  If that was on purpose or because attention wasn't payed
> to that detail, I cannot say.

For my part, it was just a reply-all - but if I had stopped to look at the
details I still would have done a reply-all - as there is nothing in this
vote that needs to be kept private in my view.
I guess it is a choice for each OMC member as to whether or not they make
their actual votes public - the summary results will be - but the actual
votes were indeed meant to be on openssl-omc only.

It would also have been good for the text to be attached - especially when
we are sending vote details to openssl-project.

Tim.
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project

Re: [openssl-project] VOTE on travel reimbursement policy

2018-02-14 Thread Richard Levitte
In message <20180214212414.ga13...@roeckx.be> on Wed, 14 Feb 2018 22:24:14 
+0100, Kurt Roeckx  said:

kurt> The call for votes should probably also not go to the project list
kurt> based on that current rules say that we vote on the omc list
kurt> afaik.

This is exactly contrary to what we agreed on at the last f2f, apart
from *certain* votes (such as invitation of new people).

Note that there's a difference between the thing we vote on and our
votes.  That latter is supposed to happen within the confines of the
OMC, but the final tally (numbers only) would be presented on the
project list.

Now, the initial posting went to both the OMC and the project list,
and some chose to vote with a simple "Reply All" without editing the
recipients.  If that was on purpose or because attention wasn't payed
to that detail, I cannot say.

Cheers,
Richard

-- 
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project


Re: [openssl-project] VOTE on travel reimbursement policy

2018-02-14 Thread Kurt Roeckx
On Wed, Feb 14, 2018 at 04:06:44PM +, Salz, Rich wrote:
> The policy is in the bureau  (not a public repo) so that we have something 
> concrete to vote on.  It is exactly the same as I posted to the project list 
> before.

I would like to see all votes contain the full text and not
a reference to some commit id.

The call for votes should probably also not go to the project list
based on that current rules say that we vote on the omc list
afaik.


Kurt

___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project