Neil Pate Posted September 26, 2016 Report Share Posted September 26, 2016 Just for anybody interested. Courtesy of our friends at GPower (4th link on google, impressive!) http://www.gpower.as/downloads/bsd-license-explained Quote Link to comment
ShaunR Posted September 26, 2016 Report Share Posted September 26, 2016 (edited) Note: That is the BSD-2 Clause licence. There is also the BSD-3 Clause liicence which adds a clause disavowing the use of the providers' name for promotional and/or endorsement of derivative works. Edited September 26, 2016 by ShaunR Quote Link to comment
JKSH Posted September 27, 2016 Report Share Posted September 27, 2016 (edited) 18 hours ago, ShaunR said: Note: That is the BSD-2 Clause licence. There is also the BSD-3 Clause liicence which adds a clause disavowing the use of the providers' name for promotional and/or endorsement of derivative works. And for those who like compact lists: https://www.tldrlegal.com/l/freebsd (2-clause, GPower's article) https://www.tldrlegal.com/l/bsd3 (3-clause, Shaun's highlight) https://tldrlegal.com/license/4-clause-bsd (4-clause, the original BSD license) Edited September 27, 2016 by JKSH 2 Quote Link to comment
infinitenothing Posted October 7, 2016 Report Share Posted October 7, 2016 IMHO, we've talked about it before and this is the annoying part of the license: Quote If you deliver binaries exclusively you can for instance save the license text file together with your other material rights documents, or you could paste the license text into the small-print section of your user guide. We talked about making a tool that would collect all the providers but it seems unnecessary for compiled code. In some cases, maybe its undesirable to let others know what your tool chain is. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.