Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming > #2848
| From | Daniel Pitts <newsgroup.nospam@virtualinfinity.net> |
|---|---|
| Newsgroups | comp.programming |
| Subject | Re: license learning |
| References | <69fa86b0-1494-48ca-ad82-2a7f51c5fd02@googlegroups.com> |
| Message-ID | <IlZJs.85006$Id.15542@newsfe24.iad> (permalink) |
| Date | 2013-01-17 12:41 -0800 |
On 1/17/13 11:59 AM, bob wrote: > When and how do most programmers learn what the different licenses *really* mean? (like MIT, GPL, Lesser GPL, Apache, etc.) > > I certainly never learned them in college, and I doubt anyone else did either. > > Do most programmers actually know these or do they just try not to get caught with their hand in the cookie jar? (or hope their hand isn't in a cookie jar) > Mostly, it is legalese, so for the finer points, a lawyer is recommended. For the general meaning, just read the licenses. It is pretty close the plain English. Also, I know some of these licenses have "annotated" version which describe the intent behind the wording. The danger there is that interpretation isn't a legally binding one compared to the actual wording.
Back to comp.programming | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
license learning bob <bob@coolfone.comze.com> - 2013-01-17 11:59 -0800 Re: license learning Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2013-01-17 12:41 -0800 Re: license learning Luca Saiu <positron@gnu.org> - 2013-01-22 11:00 +0100
csiph-web