github / choosealicense.com

A site to provide non-judgmental guidance on choosing a license for your open source project
https://choosealicense.com
MIT License
3.68k stars 1.33k forks source link

Explain common terms like "copyright", "patent" and "license" #238

Open strugee opened 9 years ago

strugee commented 9 years ago

Most people have a basic grasp of licensing-related stuff, but are hazy on the exact details of what the different terms mean. It would be nice if we could have a FAQ or something to explain all of it. I'd send a patch, but I'd like to solicit some feedback on what people think the exact format should be.

Here's a list of things we might want to put on such a page:

bhuga commented 9 years ago

This is a good idea, but I'd like to hear your thoughts on two concerns I have:

strugee commented 9 years ago

These words mean different things in different jurisdictions. Can we make a definition of "public domain" or "patent" that is meaningful for everyone without misrepresenting for at least some readers?

I think so? I'm not enough of an expert on non-US intellectual property law to say definitively, but I think if we make it general enough we can find a balance. E.g. "patent" could be defined as something along the lines of, "Something that places legal protections on ideas such that the law treats the patented idea similar to how it treats property. Patents " That blurb, while getting the main idea across, doesn't really say anything specific about the law.

Alternately, we could add a note stating that the definitions provided are based on U.S. IP law.

JeromSar commented 9 years ago

I think it's also important to clarify several other terms which use the word "patent". For example, the Apache license includes a so called "patent grant", but the term is never further explained. For me, this was confusing and raised several questions:

I think an explanation for some of these could be included in the popovers that appear at the right side of the screen when hovering over the different characteristics.

ionas commented 8 years ago

distribution, installation, service should also be cleared.

waldyrious commented 8 years ago

For future reference, individual entries in this glossary should be linkable, and linked from pages on the site where they are used.

benbalter commented 8 years ago

Just thinking through implementation, we could have a terms.yml file in the _data folder, expose it as JSON, and have a client-side script to make any use of the word on the site a tooltip using the existing tool tip library that's already loaded.

waldyrious commented 8 years ago

Rather than a custom script, why not use the build system to replace all instances of those terms with HTML <abbr> tags?

ionas commented 8 years ago

@waldyrious <arconym>, deprecated and not fitting. <abbr>, abbreviation not deprecated but not really fitting. What abotu <dfn> https://developer.mozilla.org/en/docs/Web/HTML/Element/dfn

tuespetre commented 7 years ago

I agree with @JeromSar; I am pretty ignorant when it comes to licensing and I don't have a clue what 'patent rights' means in this context or how they apply. I was hoping to find an explanation here. 😉

karam72 commented 2 years ago

It could be great if you can include Warranty disclaimers/liability term with one simple sentence.