|
I may be really naive, but I thought that as long as you're not "taking" the code and using the source in your app you're good. If you just import the libraries, you're fine. Like using a NuGet package. I'm not distributing the code, I'm not modifying and I'm not incorporating the lines of code into my project, only a reference. Am I under the wrong impression?
|
|
|
|
|
The assumption is that you take the source and incorporate it into your application. The technological means of doing so (using the source directly or a compiled library) doesn't really matter.
Our lawyer opted for a conservative interpretation of the license, given that you can't depend on having a court that is technically sophisticated enough to understand the differences between source code and a compiled library.
Software Zen: delete this;
|
|
|
|
|
deanofharvard wrote: I may be really naive, but I thought that as long as you're not "taking" the code and using the source in your app you're good. If you just import the libraries, you're fine. Like using a NuGet package. I'm not distributing the code, I'm not modifying and I'm not incorporating the lines of code into my project, only a reference. Am I under the wrong impression?
Yes, if the code in question is GPL, you would be naive and wrong.
Fortunately, virtually nobody in their right mind licenses libraries and Nuget packages as GPL.
There are many different open source licenses (LGPL / Ms-PL, BSD / MIT style) that do not want to force you to open source all your code in exchange for linking against a GPL library.
When I see an article on CodeProject, or some fancy open source project, I often scroll down to the license, check whether if it is GPL. If it is GPL, my response has to be "you're dead to me." And I move on, pretending the software doesn't exist. Maybe it helps some people who live in the hippie communes of the world, or people who write command line utilities for Linux, but unfortunately it's not useful to me.
I am now trying to educate people of the perils of using the LGPL license. I have always thought it was fair enough: if you tweak the library, you have to release your changes. Fine. But there are provisions that basically make it impossible to use LGPL software on mobile app stores or consoles, so I have been prodding library developers about whether they really want to limit their audience this way. One lesser known license that may work better for some people instead of the LGPL is the Mozilla License, which works on a source code file basis, and is missing some of the limiting aspects of the LGPL.
|
|
|
|
|
Gary Wheeler wrote: intellectual property
There is no such thing as "intellectual property".
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
Source code, design drawings, notes, schematics - call it what you will. The GPL requires that you surrender your rights to protect that material.
Software Zen: delete this;
|
|
|
|
|
Which is fine, just don't use it.
Just have you have a right to decide how to license your IP, I don't see why you're intent of denying others the right to exercise theirs. If you're not happy with the terms, just avoid it and there's no problem.
Personally, I'm happy there is a variety of licenses. Without the efforts of the GPL chaps, there would be very little FOSS, as most of it relies on gcc, Linux and other parts of the GNU ecosystem to get built at all.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
My point is that the GPL folks would have you believe that you can use it and maintain the rights to the work you've done. You can't.
Software Zen: delete this;
|
|
|
|
|
I have to agree with you, in my opinion forcing you to open your source code defeats the whole concept of open. How can something be open if its not open to allow you to use it however you want?
I think the magic of OSS is when its bundled with permissive licenses like CPOL here in CP or MIT and licenses alike. We contribute because we like and and we get support of lots of people who like doing the same.
I'm glad when people find my code useful and use in their own projects, the way they like. I find that a lot of people also help make my code become better and it becomes our code and I also benefit because I learn from it. I don't need to force anyone to share their code, specially because in many cases they can't, like when they are working on closed enterprise projects.
I am totally pro OSS, whenever its not tied to GPL.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
----
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
|
If you mean by that - it does what I need, than definitely yes!
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
in my 2 years of software development experience itself, I have seen a number of open source libraries which are much better than their enterprise counterparts.
Whether I think I can, or think I can't, I am always bloody right!
modified 14-Jul-14 5:56am.
|
|
|
|
|
I found the "Whenever it makes sense" option a bit strange.
Being open source was never an issue or a synonym of lower quality.
Actually it's a guarantee that I can put my hands in and fix whatever but it might appear.
Also it's a guarantee that I can look into the source to clearly know what's going on.
As I'm writing this I'm mainly thinking about JavaScript but the same applies, and also applied to me, in other environments.
Mostly we need to be more careful with their updates and look around in the communities if people are using it and if their problems relate to us, other than that, in most cases, open source is as good as any other piece of software.
P.S.: I didn't forget about the support, which some open source projects also have, but I've have issues with or without support that were or weren't solved no matter what...
Cheers!
|
|
|
|
|
AlexCode wrote: found the "Whenever it makes sense" option a bit strange.
Not it's not. Options 1, 3, 4, and 5 are religious choices. 2 and 6 are the only ones that aren't.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
For me it's not a matter as sense to use Open Source or not.
It's a matter of suiting the needs as a tool or not.
I mean, for me using a tool makes sense if it suites my needs, not if it's open source or not.
Now that I'm thinking a bit more about it, maybe it might apply if I'm developing an Opens Source solution.
Then it would in fact make sense to use an Open Source library to make the whole final solution, Open Source.
Ok, so it might make sense after all... :p
|
|
|
|
|
But the license of a piece of software is one of the factors in whether it suits your needs. If it is GPL, and you're writing closed-source, commercial software, it doesn't suit your needs. If it is MIT-licensed, then it may. If you have no budget for purchasing a tool, or if your needs involve being able to see how the tool works, then open source as a whole is going to be likely a good way to meet your needs and worth looking into. "When it makes sense" includes all of the factors-- it makes sense if it matches what you need in functionality, availability, licensing, and cost. So I think "when it make sense" is a perfectly valid option for the question.
|
|
|
|
|
There is a big difference between 'using' software part of an open source project (and maybe without acknowledgement) and linking libraries like boost..
I think that most professional C++ projects use at least a couple of open source libs.
modified 14-Jul-14 7:01am.
|
|
|
|
|
Davide Zaccanti wrote: I think that most professional projects use at least a couple of open source
libs
Only the poor bastards writing asp.net UIs HAVE to use 3rd party libraries (to get any productivity and in some cases to even work). Winforms, WPF and Silverlight are perfectly usable without them.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
We are strongly discouraged from using open source code - management want someone they can beat on if the tool goes wrong, besides us minions that is.
Yes, when there aren't any other sensible options
This does seem to imply that open source is NOT a sensible option, just saying.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Open Source doesn't mean lack of support
There are plenty of open source projects/products that have support plans.
Actually this is a business strategy where these companies create a large user base because their product is free but still manage to pay their bills with the support fees.
So don't mix Open Source with jumping off a cliff without parachute! 
|
|
|
|
|
AlexCode wrote: Open Source doesn't mean lack of support
Sure I know that, you know that, anyone working in the industry knows that, try getting management to understand that and change their policies - I figure a policy change will kick in about 2022!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I don't see that implication. I read that one as saying "Given a choice between good open and closed tools to do something we normally pick the closed one, but will use good OSS in preference to writing our own if nothing else is available".
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Mycroft Holmes wrote: We are strongly discouraged from using open source code - management want someone they can beat on if the tool goes wrong, besides us minions that is.
Wow, do you mind sharing the name of the company so that I can make a mental note never to get a job there?
|
|
|
|
|
When it makes sense.
Unless the people who voted no really wouldn't use open source software even when they know it would make the most sense out of all alternatives.
They probably voted no because so far it hasn't made sense to them yet.
Or because their boss tells them not to use it. In that case the above goes for the boss!
And the people who voted as much as possible would use open source software even when it makes no sense?
I'm having my doubts about that! Open source in general probably just makes sense to them.
And when it makes sense or when there aren't any other sensible options are practically the same, no?
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
"As often as I can" may include situations where the open source version may not be the best option, but it is free. Sometimes you make the free stuff work for your needs just because you cannot justify the benefits to cost ratio.
...of course, you could argue that as "When it makes [financial] sense"
|
|
|
|
|
musefan wrote: ...of course, you could argue that as "When it makes [financial] sense"
You beat me to it 
Sense is sense, whether it's financial, technical, political or what have you
And if indeed the benefits to cost ratio is better for open source it makes sense, especially when you cannot afford the costs (in which case it may be the only sensible thing!).
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
