> On Jan 1, 2020, at 15:49, @lbutlr <krem...@kreme.com> wrote: > >>>> You are right that there wasn't a warning, and that was a major >>>> mistake that should not have happened. security/openssl and >>>> security/openssl111 should have contained messages about this switch. >>> >>> Since openssl updated about a week ago, this oversight falls into the class >>> that I would call ???inexcusable???. If I did this on a job I would >>> (rightly) be immediately fired. >>> >>> I would fire me if I did something like this. > >> If we fired every volunteer when some mishap has happened, we >> would run of of volunteers very fast. > > This was the responsibility of a single volunteer? Removing openssl without > warning wasn’t something that was discussed over the last six months?
Ok, let’s stop there. Nobody is going to get fired, and insulting our team of volunteers who worked incredibly hard to bring the openssl switch to fruition is unproductive and uncalled-for. I already acknowledged that we need to do it better next time, so let’s focus instead on solving problems rather than lashing out to people who are here simply to help. # Adam — Adam Weinberger ad...@adamw.org https://www.adamw.org _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
