Hacker News new | past | comments | ask | show | jobs | submit login

Your confusion is understandable, and, regrettably, quite common.

Many license documents you are likely to encounter are written as if they were a list of things you can not do; as if they were some sort of contract which you agree to (somehow without signing it). This is very misleading, since a license is a list of permissions, not prohibitions. However, is in the interest of most license writers to mislead you in this way, so that they can keep the maximum rights for themselves and scare you into thinking you have as few rights as possible. The frequently-used term “license agreement” is a symptom of this; it is misleading because a license is not an agreement. It is also often the case that such documents prohibit many things which you have the right to do, but which a license (being a list of permissions and not a contract) can not deprive you of.

Finally, some licenses, such as the GPL, may seem to follow this pattern superficially, but what they list are instead conditions which you must uphold if you are to recieve the permissions granted by the license. Crucially, the document does not try to prohibit you from doing anything which is your right even if you do not comply with the conditions set by the license.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: