Blog post; changing in email, crypto policy, etc
Locked
12
12
Blog post; changing in email, crypto policy, etc
 
|
Re: Blog post; changing in email, crypto policy, etc
|
|
It appears to me that you could use openssl-dev instead of openssl-project, saving cycles on killing one and creating the other.
-- Regards, Uri Blumenthal On 1/19/18, 12:35, "openssl-dev on behalf of Salz, Rich via openssl-dev" <[hidden email] on behalf of [hidden email]> wrote: There’s a new blog post at https://www.openssl.org/blog/blog/2018/01/18/f2f-london/ It contains some important policy changes we decided at our meeting last month. This includes: - Closing the openssl-dev mailing list; use GitHub for issues - New mailing list openssl-project for project discussions - New policy for accepting crypto algorithms, formats, and protocols. - .. several others Please read the posting; the changes described in it affect everyone who uses OpenSSL. Thanks for your interest, and all your efforts to help improve the project! -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev |
smime.p7s (6K)
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
On 1/19/18, 12:52, "Salz, Rich" <[hidden email]> wrote:
>> It appears to me that you could use openssl-dev instead of openssl-project, saving cycles on killing >> one and creating the other. > > We discussed that, but it would be harder to “undo” if things don’t work out, we wanted > to make it very clear that this is a new way of operating, and openssl-project is a > moderated list. Make sense? I don’t know. I’d still do as I said. But since you guys discussed it (i.e., debated this option), I’ll defer to your judgment. -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev |
Re: Blog post; changing in email, crypto policy, etc
|
|
In reply to this post by OpenSSL - Dev mailing list
On Friday, 19 January 2018 18:34:57 CET Salz, Rich via openssl-dev wrote:
> There’s 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 all 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 us > 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 -- Regards, Hubert Kario Senior Quality Engineer, QE BaseOS Security team Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 115, 612 00 Brno, Czech Republic -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev |
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
In reply to this post by OpenSSL - Dev mailing list
On Tuesday, 23 January 2018 15:22:13 CET Salz, Rich wrote:
> You should be able to just watch the openssl repo (the eyeball/watch notice > in the upper-right side) that's what I was talking about this feature sends notifications about _all_ conversations happening. > On 1/23/18, 7:00 AM, "Hubert Kario" <[hidden email]> wrote: > > On Friday, 19 January 2018 18:34:57 CET Salz, Rich via openssl-dev > wrote: > > There’s 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 > > all 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 us 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 > > -- > Regards, > Hubert Kario > Senior Quality Engineer, QE BaseOS Security team > Web: www.cz.redhat.com > Red Hat Czech s.r.o., Purkyňova 115, 612 00 Brno, Czech Republic > -- Regards, Hubert Kario Senior Quality Engineer, QE BaseOS Security team Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 115, 612 00 Brno, Czech Republic -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev |
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
In reply to this post by Hubert Kario
On Tuesday, 23 January 2018 15:36:26 CET Salz, Rich wrote:
> ➢ this feature sends notifications about _all_ conversations happening. > > For me, I get the actual comments that are posted. Don’t you? when I comment in an issue/PR or mark it as followed I'm getting only messages from that issue/PR when I mark project as followed I'm getting messages from all issues and all PRs - likely dozens if not hundred messages a day > On the > mailing list, you have to explicitly mark/junk conversation threads in your > mail program. You would still have to do that here. > I don’t understand what you see as different? that marking a conversation as ignored and going to next one is two key combinations and less than a second, github ones require me to go to the web UI which is slow, and if I have to view the issue because subject is ambiguous it takes ten times as long as it does when using email email clients are designed to handle hundreds to thousands of messages a day, Github UI isn't or to put it other way: github notifications are perfect if you are directly involved in the project, they suck if you just want to keep tabs on an active project -- Regards, Hubert Kario Senior Quality Engineer, QE BaseOS Security team Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 115, 612 00 Brno, Czech Republic -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev |
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
On Tuesday, 23 January 2018 16:13:30 CET Salz, Rich wrote:
> ➢ github ones require me to go to the web > UI which is slow > > I am confused by that. When someone posts an issue or comment, I get the > text emailed to me. Not just openssl, but all projects I watch. ah, true, I have those disabled because I use the same account for both my personal and my work projects so no single email address is correct for them -- Regards, Hubert Kario Senior Quality Engineer, QE BaseOS Security team Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 115, 612 00 Brno, Czech Republic -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev |
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
In reply to this post by Hubert Kario
Hubert Kario <[hidden email]> wrote: > that marking a conversation as ignored and going to next one is two key > combinations and less than a second, github ones require me to go to > the web UI which is slow, and if I have to view the issue because > subject is ambiguous it takes ten times as long as it does when using +1 > email clients are designed to handle hundreds to thousands of messages > a day, Github UI isn't -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev |
Re: Blog post; changing in email, crypto policy, etc
|
|
Re: Blog post; changing in email, crypto policy, etc
|
|
| Free forum by Nabble | Edit this page |