Lots of people have been receiving emails like the one below.

They have never asked the community of authors what they want.

I think OpenSSL are using a github "garbage-in / garbage-out" style of
process.  Feel free to dig into what they think I am author of, and

The start suggests they want to privately collect sufficient consensus
to pass their agenda.  They appear to be considering all actions in
the tree (including mine) on equal grounds.

The last sentence suggests they don't care at all about the rights of
the authors.


Date: Wed, 22 Mar 2017 16:48:10 -0400
From: lice...@openssl.org
To: dera...@cvs.openbsd.org
Subject: OpenSSL License change
Message-ID: <20170322204810.ra49wtmwn%lice...@openssl.org>
User-Agent: s-nail v14.8.6
Status: O


This mail is coming from the OpenSSL development team.

This is a pre-release email before we "go public."  In particular,
the most recent blog entry, listed below, is not yet available.  But we
thought, as an important downstream fork, that we'd give you the courtesy
of participating early.

We are working to change the license for OpenSSL. We want to move from
the current license (which is custom-written and has some uncommon
requirements on end-users), to the widely-accepted and common 
Apache License (version 2).  You can find some explanation in
our blog entries:


We wrote some tools to look through every version of our files, and
our scripts found your email address.  You can see what we found:


We are asking for your permission to change the licence for your
contribution. Please visit this link to respond; you will have a chance
to accept or decline, and enter a brief comment (you can use the comment
to give the names of other people we should contact, for example):


If you have any questions or concerns, send email to lice...@openssl.org;
please be patient for a response. You can also post to the public mailing
list, openssl-...@openssl.org; details about that list can be found at this


If we do not hear from you, we will assume that you have no objection.

Thank you!

-The OpenSSL Development Team

Reply via email to