He states that clause 3 is "hereby deleted in its entirety. The license below does not contain the advertising clause. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:.
Use to manage open source licenses, from the creators of tl;dr Legal. One thing about both the GPL and the BSD-style licenses for which there is widespread agreement is that both have problems.
Neither is perfect, and perhaps no license can be perfect. There is also considerable agreement that there are benefits both to software developers and to society as a whole from the choice provided by the existence of a variety of types of free software licenses, including the GPL and BSD-style licenses. The original version of the BSD license contained the so called advertising clause , which stated that all advertising materials that mention features of or use of the software must display the acknowledgment: "This product includes software developed by the University of California, Berkeley and its contributors.
One of the problems with this clause arose from the fact that people who made changes to the source code often wanted to have their names added to the acknowledgment. This could easily result in large and cumbersome acknowledgments for products with numerous contributors and for software distributions consisting of multiple individual projects.
A second problem was legal incompatibility with the terms of the GPL. This is because the GPL prohibits the addition of restrictions beyond those that it already imposes. That did not cause any major problems because it was only necessary to include a single sentence of acknowledgment in any advertisement. However, the fact that other software developers did not copy the clause verbatim, but replaced the phrase "University of California" with the name of their own organization or persons involved in it, resulted in a proliferation of slightly different licenses and a consequently serious problem when many such programs were assembled to form a larger work or an operating system.
For example, if an operating system or other program required fifty slightly different acknowledgment sentences, each naming a different developer or group of developers, such advertising alone might require a full page. Not only would this be very tedious reading, but it could also be costly. In June , after two years of discussion, the Office of Technology Licensing at UCB finally proclaimed: "Effective immediately, licensees and distributors are no longer required to include the acknowledgment within advertising materials.
Accordingly, the foregoing paragraph of those BSD Unix files containing it is hereby deleted in its entirety. This was clearly very useful. However, it could not eliminate the legacy of the advertising clause, as similar clauses still exist in the licenses of many programs that followed the old BSD license; only the developers of such packages can change them.
In the BSD licenses, they talk about "source code and binary form", no mention of documentation. In fact, FreeBSD uses a complete different license for its documentation. The MIT license is short, clear, and easy to understand. The disadvantage is that anyone can take software licensed under MIT, change the branding, and sell it as proprietary software. MIT commercial use: users do not have to provide any other source code when releasing new software.
MIT licenses allow commercial use. As the MIT license falls in the BSD-style class of licenses, users do not have to provide any other source code when releasing new software. Including the attributions and original MIT license in the reused code will suffice, making MIT licenses suitable for commercial use.
Applying a license to your open source projectsOpen your GitHub repository in a browser. In the root directory, click on Create new file. Click on Choose a license template. Pick one of the licenses all the ones mentioned in this article are there.
Once chosen, click on Review and submit. Meer items This is the original BSD license, modified by removal of the advertising clause. Since the license covers distribution the terms you agreed to when they distributed it to you still apply, they can't suddenly revoke an MIT library that has been in use for years.
Read the license. You can see for yourself that there's no provision for revoking that permission as long as you comply with the license.
How to comply with it? You can use BSD-licensed projects in closed-source, commercial projects. You must include the original copyright and license. The BSD License allows proprietary use and allows the software released under the license to be incorporated into proprietary products. Works based on the material may be released under a proprietary license as closed source software, allowing usual commercial usages under.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Ask Question. Asked 9 years, 3 months ago. Active 10 days ago. Viewed 59k times.
0コメント