level 1·4d·edited 4dFYI: This is not a licensing change. It is about whether you need to submit paperwork to transfer the copyright ownership to the FSF before contributing code - you no longer need to do so. Several contributors had problems with this and have started working on a fork. It's also very unusual for an open source project to require this (usually only done by companies that want to relicense the code in the future, e.g. to a proprietary license).
I think it is a good idea regardless, it added difficulty to the first contribution of a new developer, which is already difficult and it's more likely they will make further contributions after a first one.
24level 2Keep in mind that not assigning copyright is why openssl has the annoying license that requires the exception, and it's taking them several years to fix this issue.
5https://www.reddit.com/r/linux/comments/npzqbq/update_to_gcc_copyright_assignment_policy/
OpenSSLのライセンスは2種類のライセンスが連結されたものです。一つは“OpenSSL License”と呼ばれ、もう一つはSSLeayのライセンスです。あなたは両方に従わなければなりません。この二者の結合は、コピーレフトの自由ソフトウェアライセンスとなっており、これはGNU GPLと両立しません。また、このライセンスは オリジナルBSDライセンスやApache 1ライセンスのような宣伝条項を有しています。
わたしたちは、皆さんがお書きになるソフトウェアではOpenSSLの代わりにGNUTLSを使うことをお勧めします。しかしながら、OpenSSLやOpenSSLと共に動作するアプリケーションを使わないという理由は何もありません。
https://www.gnu.org/licenses/license-list.html
GPLとOpenSSLが両立できない不満
