News for hackers. Stuff that matters.

A comment on Crypto optimizations for Go from CloudFlare/Intel blocked by licensing issues. Parent comment

Re:Crypto optimizations for Go from CloudFlare/Intel blocked... by stock_toaster on Monday May 18, 2015 @07:45PM (#9567463)
There is also a requirement to submit a signed CLA, as seen here[1].

Additionally, on that page there is a requirement for a standard copyright header, specifying "The Go Authors" as the copyright holders.

[1]: https://golang.org/doc/contribute.html#copyright

[ Parent | on HN ]
Re:Crypto optimizations for Go from CloudFlare/Intel blocked... by jerf on Tuesday May 19, 2015 @09:32AM (#9569865)
The CLA is not a term of the license; it's a term of Google's stewardship of the code. If you fork Go and keep the BSD license, you can do as you like. Many projects of many varying license types use CLAs. The Linux kernel deliberately uses the fact it doesn't have one to ensure that nobody could ever un-GPL2 it because there's no possibility that you could ever reach every contributor for a license change.
[ Parent | on HN ]