Licenses: Difference between revisions
No edit summary |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
If you are writing closed-source software, only use other software which are MIT, Apache, or BSD licensed. | If you are writing closed-source software, only use other software which are MIT, Apache, or BSD licensed. | ||
Do not use or link to any AGPL software such as MongoDB, especially if you want your startup to get bought out. | |||
Interacting with GPL programs such as MariaDB through an interface layer is fine though. | |||
Licensing your own software as AGPL will prevent it from ever being bought out or used at many tech companies. | |||
This is because tech companies, in particular Google, have an AGPL ban<ref name="googleagpl">Google AGPL Policy: https://opensource.google/docs/using/agpl-policy/</ref>. | |||
==MIT License== | ==MIT License== | ||
| Line 81: | Line 86: | ||
The GNU Affero General Public License is basically GPL but where interaction over the network counts as distribution. | The GNU Affero General Public License is basically GPL but where interaction over the network counts as distribution. | ||
So if people can interact with your AGPL program over the internet, then you must open-source it. | So if people can interact with your AGPL program over the internet, then you must open-source it. | ||
==Creative Commons Licenses== | |||
==Resources== | ==Resources== | ||
* [https://opensource.stackexchange.com/questions/217/what-are-the-essential-differences-between-the-bsd-and-mit-licences BSD vs MIT License stackexchange] | * [https://opensource.stackexchange.com/questions/217/what-are-the-essential-differences-between-the-bsd-and-mit-licences BSD vs MIT License stackexchange] | ||
==References== | |||