Tell me more ×
Answers OnStartups is a question and answer site for entrepreneurs looking to start or run a new business. It's 100% free, no registration required.
up vote 1 down vote favorite

My commercial software is using some code source licensed under LGPL or MIT. How and where should I mention this? Is it mandatory?

share|improve this question
Can you be more specific? Perhaps tell us how you use the source or even tell us which open source code it is? – TimJ♦ Nov 4 '10 at 14:06
Thank you Tim. The open source code is sourcegrid.codeplex.com. I am linking to the dll of the library. – Tom Nov 4 '10 at 15:03

3 Answers

up vote 1 down vote accepted

I don't know the terms of the MIT license by heart, so you'll have to read it.

With regard to the LGPL: is the LGPL work you are using (hereafter referred to as "foo") a library or something else? Is the work based on foo (hereafter referred to as "bar") a derivative of foo, a work that uses foo, or are you unsure (in which case provide more info on bar)?

Generally, if foo is a library, and bar uses foo as an external dependency rather than compiling whole chunks of foo into bar, bar is a work that uses foo, and you have no particular responsibilities under the LGPL.

If you foo is a library, and bar is a modification or derivative of foo, or foo (or significant portions of foo) are compiled into bar to make it count as a derivative, the LGPL applies and you must provide the proper notices, access to the source code, etc. In this case you may at your option relicense bar under the GPL instead of the LGPL if doing so makes more sense to you.

There are a bunch of other cases, but those are the two most common.

IANAL*, but I run an open-source based development shop, so I deal with this stuff daily.

--Susan

*I Am Not A Lawyer: in other words, don't take my word for it, that's what lawyers are for.

share|improve this answer
Thank you Susan. You answered my question. My software is linking to the library dll. – Tom Nov 4 '10 at 15:06
This answer is for the LGPL license, not MIT. Not doing anything (the advice above for LGPL when just linking to a DLL) is a violation of the MIT license. – TimJ♦ Nov 4 '10 at 15:23
up vote 2 down vote

Follow the license of use.

share|improve this answer
1  
This is not helpful – Tom Nov 4 '10 at 13:46
1  
@Tom - What John is saying is to read the license, understand it and comply. It is the right advice, but it is not spoonfeeding you the answer. – TimJ♦ Nov 4 '10 at 13:54
@Tom: agreed. If he understood the license, he'd not have asked. – HedgeMage Nov 4 '10 at 13:55
@Tim: When it comes to open source licenses, people from the closed-source world tend to get a bit disoriented at first. A little hand-holding while they get their sea legs isn't out of line. If John isn't in the mood to provide it, he's welcome to skip the question instead of giving a non-answer. – HedgeMage Nov 4 '10 at 13:57
@Hedge - yes, but the OP didn't provide specifics in how he was using the library(ies) so the best answer is "read the license and apply the relevant sections". If Tom had done that we could give him the exact terms to comply with. And I agree - the open source licenses can be daunting when jumping in. It was a huge distraction for me when I had to figure out if we should bother using open source works. – TimJ♦ Nov 4 '10 at 14:02
show 2 more comments
up vote 1 down vote

EDIT

Based on your link to the project it is the MIT license, not LGPL. Here is a wiki page on the MIT license.

So I think you need to have this notice in your software somewhere:

Copyright (c) 2009 Davide Icardi

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

share|improve this answer
Can I simply put it in a txt file with other application files? – Tom Nov 4 '10 at 15:28
If you can't decide then I think it is time you ask the author listed above what he would be happy with. Or you can look at the listed software that uses it and copy what they do. – TimJ♦ Nov 4 '10 at 15:30
What I have done is provide ALL the license information/text in a dlg box during installation. No one really reads them, but they are there, in your face at install time. I also include a license.txt file in the parent folder. I have no idea if this is acceptable to you or the license holders but in my opinion it is in compliance with the licenses I need to work with. – TimJ♦ Nov 4 '10 at 15:35
Thank you Tim for the info – Tom Nov 4 '10 at 15:51

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.