Re: Blog post; changing in email, crypto policy, etc

--===============0027976949311177436==
Content-Type: multipart/alternative; boundary="94eb2c1afccc7ac754056370aa0c"

--94eb2c1afccc7ac754056370aa0c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello,

On Tue, Jan 23, 2018 at 3:00 PM, Hubert Kario <[email protected]> wrote:

> On Friday, 19 January 2018 18:34:57 CET Salz, Rich via openssl-dev wrote:
> > There=E2=80=99s a new blog post at
> >     https://www.openssl.org/blog/blog/2018/01/18/f2f-london/
>
> > We decided to increase our use of GitHub. In addition to asking that al=
l
> bug
> > reports and enhancement requests be reported as issues, we now want all
> > major code proposals to be discussed as issues before a large pull
> request
> > shows up. This will let the community discuss the feature, offer input =
on
> > design and such, before having code to look at. We hope this will let u=
s
> > all first look at the bigger picture, before getting bogged down in the
> > weeds of line-by-line code reviews.
>
> does that mean I have to subscribe to all notifications from the openssl
> github project to notice them? that's really suboptimal
>

Totally agree.


--=20
SY, Dmitry Belyavsky

--94eb2c1afccc7ac754056370aa0c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,=C2=A0<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Jan 23, 2018 at 3:00 PM, Hubert Kario <span dir=3D=
"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">hkario@red=
hat.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D"">On Friday, 19 January 2018 18:34:57 CET Salz, Rich via openssl-dev wr=
ote:<br>
&gt; There=E2=80=99s a new blog post at<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.openssl.org/blog/blog/2018/0=
1/18/f2f-london/" rel=3D"noreferrer" target=3D"_blank">https://www.openssl.=
org/blog/<wbr>blog/2018/01/18/f2f-london/</a><br>
<br>
</span>&gt; We decided to increase our use of GitHub. In addition to asking=
 that all bug<br>
&gt; reports and enhancement requests be reported as issues, we now want al=
l<br>
&gt; major code proposals to be discussed as issues before a large pull req=
uest<br>
&gt; shows up. This will let the community discuss the feature, offer input=
 on<br>
&gt; design and such, before having code to look at. We hope this will let =
us<br>
&gt; all first look at the bigger picture, before getting bogged down in th=
e<br>
&gt; weeds of line-by-line code reviews.<br>
<br>
does that mean I have to subscribe to all notifications from the openssl<br=
>
github project to notice them? that&#39;s really suboptimal<br></blockquote=
><div><br></div><div>Totally agree.=C2=A0</div></div><br clear=3D"all"><div=
><br></div>-- <br><div class=3D"gmail_signature" data-smartmail=3D"gmail_si=
gnature">SY, Dmitry Belyavsky</div>
</div></div>

--94eb2c1afccc7ac754056370aa0c--

--===============0027976949311177436==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

--===============0027976949311177436==--