Rumours 116
Anonymous Coward writes "I must remain anonymous for fear of job security, however... Sprint is a client of ours and we have been given a contract to sign that includes (among other things) a bit that goes like this: Supplier warrants that no GNU, FSF, or copylefted software shall be used in the production of services for Sprint. I'm still trying to figure out if this means that I have to uninstall gawk, apache, sendmail, BIND, etc., from my (non-linux) UNIX systems.... Afraid I can't include a link to the exact contract verbage, but it's 100% factual, I just read the contract myself. "
I also received an email from an EE claiming that Synopsys had informed him that they would be porting their tools to Linux. This would be an important step since Linux is ideal for large simulation/synthesis farms: cheap hardware and stable OS that can be left in a computer room. In related news, Green Mountain Computing Systems has released their VHDL compiler for Linux, with a demo available for download. It is slightly faster than the NT version, with better memory performance.
Contract issues: (Score:1)
If this is true, sprint would have no email, dns, routing, etc, etc, etc, etc. Who comes up with this stuff?
And more importantly, could I had you a binary sendmail, say "Uh... it's commercial..." and make money off their stupidity
--
Correct me if I'm wrong... (Score:1)
uhm, I read the article differently (Score:1)
Thats an entirely different thing as saying you may not re-use GPL code. That indeed would be rational but its not what it says. According to this wording the programmers wouldn't be allowed to use Emacs to write the code
It's just a thing that a lawyer figured out without really understanding what he's talking about.
A possible reason? (Score:1)
The idea being that there needs to be *no* possibility that any of the work done for them could be considered derivatives of GPL'ed software - and therefore, Sprints license for the delivered works is safe from, intellectual-property wise.
Sprint is a big corp. Big corps have lawyers. Lawyers are essentially useless members of society, and they know it - they're scared of people waking up and realizing this. So they do things to make themselves seem important - such as add clauses 'that will protect the future investments and assets of this company'.
Oh well. I guess this Sprint contractor will just have to re-invent the wheel(s). Again.
Sprint is not totally off base... (Score:1)
I guess some suits have not read their EULAs. If you read any license agreement, you will see that the author of the software limits his liabilty to replacement of the product. There is no liabilty stated for damages caused by said software. That is the case for both commercial and GNU/FSF software. The only diffference betweent he two types of software is the cost. The liability to the author is the same.
Its clear what the deal is (Score:1)
You have some suits who make an engineering decision. The kind that wonder if their water cooler is y2k compliant. What they are afraid of is some highschooler's ten cent hack code being used, something going wrong shutting down the nationwide network, and their satellites falling out of the sky.
Really though open source code will prove to be more robust in the long run. AT&T learned this the hard way when a single line of bad proprietary C code crashed their eastern seaboard network - how soon do people forget? Quite frankly with the way NT is going, when it crashes somebody's mission crtical app, suing the company won't bring them back online. Nor will they get legal redress with most if not all software packages I know about come with a "AS IS" warranty that absolves the software company of any legal liability whatsoever.
When the get tired of bloated, buggy, crashy code like I am, I have a feeling that they will forget about this contract and let the engineers make the decision and dump the suits.
Not all free software, just GNU (Score:1)
It might have something to do with the fact that the GNU license is incompatible with everything else. You use some GNU software in your code, guess what? You're screwed, you must convert everything to GNU! This may not even be possible because of NDA's, patents, etc.
I won't be surprised if there is a greater backlash against GPL in the future.
I know GPL advocates will be seething at this message, but they need to understand how the world in general works, and it's not GNU.
Sprint is my local pots (Score:1)
Mistakenly, of course (Score:1)
--
hmmm... (Score:1)
Geee, I wonder if it's vulnerable.
Fear, Uncertainty, and Doubt. (Score:1)
please now, no GPL is not the end of the world (Score:1)
By this reasoning, writing this line of shell script wouldn't be allowed (if I wrote and executed it, say, on a linux box)
grep -v ^# stupid.file > stupid.uncommented.file
However, writing this line of code on this NT machine and running it would be fine:
find
However, find and grep are not the same. Specifically, find is a proprietary cheap ripoff of grep. This is why find has no equivalent to ^# (matching strings starting with #) and therefore I would have to write a proprietary replacement to find, or find a grep that isn't GPL'ed.
How does using a GPL'ed utility hurt Sprint? It doesn't. There are no licensing issues for using GPL'ed software for the production of anything. There *are* licensing issues for modifying GPL'ed software, and recompiling it. (or, for that matter, stealing code, which you can't really do in the proprietary programs anyhow.)
Solution? Treat a GPL'ed binary like a proprietary binary. Don't read source unless you're going to use the GPL.
Basically, this contract needs to be more specific, and you need to figure out what a derivative work means. (I read the GPL, and it's not as broad or as boneheaded as that snippet from the Sprint license. (Specifically, if you need *more* explanation, the Sprint license is talking about use of programs, the GPL is talking about source code. Got it?) )
Sprint rumor (Score:1)
If it is real and I think it's possible, I'd want to know what the exact reasons were and not the supposed reasons. That sounds like an explicit clause excluding a specific group of software. I would think that if they were out to insure themselves and have the lawsuit option as well as the 24-7 quick support that they could word it in a manner that wouldn't prevent GPLed software explicitly.
Now at IBM (standard disclaimer) I've heard the (L)GPL issure rehashed a number of times and it hinges on what the meaning of use is. GPL doesn't outline what it means to use a GPLed product. It sounds stupid but lawyers take that kind of stuff seriously (ie: Clinton and what sex means) I've been told by some people that I should remove emacs, cygwin32, linux, info-zip, etc.. from my computer until an IPL comes and gives the ok sign. I've also been told that as long as the GPLed software doesn't produce something that we ship or get shipped with a product then I'm cool so I can use emacs but not bison or gcc. I've also been told to do what it takes to get the job done by a few people which I'll take to mean what I need it to mean.. When your pockets are deep enough the tight rope you walk on becomes very narrow and you take careful steps because you fall a lot further. In the warped minds of those who practice law, RMS or Linus or somebody is totally likely to ignore the use of GCC or linux by small software house but when Microsoft or IBM uses it the lure of billions of dollars cause them to fabricate a law suit.
It's also possible that this could be a new wave of anti-free software activity by companies that stand to lose a lot of money. The OSF kind of did this a few years ago. (You'll probably have to see the world through my twisted mind to fully agree with me on this one..) Some (BIG) companies got together and they produced a brand name and got more big powerful companies to buy into it, then they went out with the non-OSF excluding contracts so that some projects were exclusively 'Open' even though 'Open' was mostly a sham. There are still products and companies that brag about 'Open' products even though the OSF is hardly open, it's a codeword used to make a sale. It was a big market protection gimmick (not exactly, but that's pretty much what a lot of it was) the OSF wasn't the cheapest or easiest organization to get involved with and a lot of their technology wasn't so hot but they could force you into using it because you needed the brand to sell your product.
It's probably just the stupidity of some suit wearing chump who doesn't understand technology who thinks that having the source code makes it wildly easier to break through security or something.
First shot fired! The Great Battle has begun! (Score:1)
Silly Suits (Score:1)
derived products is the right thing for anyone selling proprietary software to do. However, banning its use in services is downright silly and sounds ideologically motivated (that is, if the original source wasn't garbling this.)
Linux and >2GB memory (Score:1)
axolotl
"production of services"--is that software? (Score:1)
Can't use GPLed software since output is GPLed,na (Score:1)
One cannot use the GIMP because images edited with the GIMP are GPLed.
One cannot use a GPLed circuit design program because the chips so designed are GPLed.
One cannot use GPLed CAD program to design a car because such a car is GPLed.
That's what Sprint is thinking, I guess...
Doh! If it's internal, you don't have to! (Score:1)
-russ
This is bullshit. (Score:1)
Go read the GPL before you opine on it.
-russ
Kudos for Sprint (Score:1)
If we're going to slam Sprint based on an anonymous rumor, then shouldn't we be just as quick to praise them for a non-anonymous one?
Cygnus *does* provide immediate support (Score:1)
Um, Cygnus [cygnus.com] does exactly that - it guarantees immediate support for GNU development tools if you have a support contract with us. We've got some pretty major companies as customers, too.
Time to squash the "GPL is a Virus" meme (Score:1)
The GPL is all about choice. It is a little bit uncompromising for some people's tastes. But, like its creator, there is absolutely nothing underhanded or secretive about it. It says what it means and it does what it says.
Also, your interpretation of the clause in Sprint's license is rather too forgiving. Taking literally, as quoted, it does indeed imply that you couldn't at any time use GPL-licensed software while doing their work. That means no compiling with gcc, no scripting with Perl, and no Linux anywhere in the same room. If the contract is as quoted, compliance would be almost impossible in most UNIX shops.
Re: Sprint is not totally off base... (Score:1)
Give me one example of a company suing a software manufacturer and I'll accept that line of reasoning.
Much of what we do is time-critical, and with all forms of free software, immediate support cannot be guaranteed.
Give me one example of anything in a distributed environment (ie, not mainframe) where immediate support is guaranteed and I'll accept that line of reasoning.
Thirdly, if we had a linux expert who set up a bunch of systems, and got his by a truck tomorrow, we'd be screwed. With SGI, Sun, HP, etc, we could bring in an expert immediately.
Prove to me that a Linux expert is harder to find than an SGI, Sun, or HP expert and I'll accept that line of reasoning. Also prove to me that an OS expert would be of any help in this situation. Technical expertise is more a function of how expert a person is in your systems, not the OS.
Your arguments are paranoid and dillusional. There are many institutions that can deal with problems such as you are experiancing. If that fails, there are several fine chemicals that can in fact help.
please now, no GPL is not the end of the world (Score:1)
If you're going to write something that's a modification of GPLed software, why bother not using it? Certainly you aren't the only people that thought of it! Why not let the other people who did all the original work get to see the changes?
As a software author, why would *I* ever release software under a BSD style license? If I'm going to pour hours and hours of work into software, why would I want to let someone else take MY work and change it and make money off it and not let me see what they did with it? Or even publicly credit me with doing the work that is making them money?
If your software is soooo great that it is not something that can be released, ok, then don't use GPL. But, why should we programmers be forced to continually reinvent the wheel just cuz someone else thinks their wheel is too good for us to see?
You don't like GPL, that's you're perogative, but from a programmer who's spent too damn much time rewriting code that's already been written, I think it's the only thing that will keep software moving forward at the rate it should.
** Martin
bad taste (Score:1)
FUCK! with a upper case "F" (Score:1)
How many fucking times must some cunt hole say this:
"Secondly, there's no one to sue if something goes wrong."
When last did you see a company get sued for selling bad software?!? Almost every so called "commercial" grade software package comes with a EULA that makes them NOT responsible for anything that the software may do to your computer, your life, your kids, your dog, or your god damn pet monkey named bob!
Get a fucking grip you stupid morons!!!!
i cannot take it anymore.................
give me a call (Score:1)
hey mook (Score:1)
am i being forced to give the original programmer my code changes? no! exactly... if i am wrong, someone please stop me, but since i know that the code is not leaving my computer, the source does not need to leave too... so there...
Apple, meet Orange... (Score:1)
I do work for sprint (Score:1)
I work in a software engineering group deep within sprint, and I am part of a team that's currently getting MAJOR corporate kudo's from the big-wigs for opening up their eyes to OSS...
We just saved them 3,000,000 smackeroos by coding an app in PHP. The original outsourced bid still canna figure out how we did it...
sprint DOES realize the power of OSS, and Linux. Myself and the 6 others i work with are living proof of it.
Viva Hawaii, boys. Viva hawaii.
They only need release if they sell the product (Score:1)
--
Sprint sucks. (Score:1)
-N.
Gandhi, not Ghandi (Score:1)
Reliability of rumours... (Score:1)
but the people at slashdot really should know better than pass on clearly wrong rumours that BIND, sendmail, etc. are covered by GPL, Copyleft or some "FSF" licence.
Contract issues: (Score:1)
All these programs are covered by BSD and not GPL licences.
There isn't much useable GPL-ed network software at all.
Stallman's folly? You must be jealous (Score:1)
As if they cared if some user or other "boycotted them.
>more development and debugging time, bug ridden >products, and so on. Sprint hasn't got anything I >need.
If they have got nothing you need, then you aren't their customer (or wouldn't be) anyways so they have no reason to give a rat's ass about you.
Oh and you claims about more bugs, more time, etc. are just that - just silly claims.
Don't buy an Intel (Score:1)
a) all intel processors since 386DX have been able to address 4GB of memory
b) PPros and Xeons have 36bit address bus
and can thus address 64GB of memory.
please now, no GPL is not the end of the world (Score:1)
You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions...
If you don't distribute your copies, (ie keep them for internal use only) then the you don't have to make your changes availble.
If you distributed your stuff, then it's a totally different ball game...
-Erik
Sprint is not totally off base... (Score:1)
mmmm.... vhdl (Score:1)
then again...
investorrelation.sprintcom@mail.sprint.com (Score:1)
investorrelation.sprintcom@mail.sprint.com
Would seem to be one such place to query.
nice.. (Score:1)
Finding someone to sue (Score:1)
If something goes wrong with Microsoft(tm) or Oracle(tm) or any other commercial software, do you actually have a realistic chance of prevailing in a lawsuit claiming the products are shoddy?
If so, I would think Microsoft would be filing for bankruptcy any day now.
I mean, it's a nice theory and all, but I think all you could ever get back is the price of the software, and that's not going to help if your whole business went south.
True, you can talk to a Support Robot, but I haven't found support robots of any stripe to be particularly helpful.
D
ASIC Design and Synopsys. (Score:1)
Ouch.. (Score:1)
too many acronymx... (Score:1)
Linux a distraction... (Score:1)
from their main business (the one we pay for)
of delivering _reliable_ tools. Instead they're
off chasing yet another cheap platform.
I'll call Synopsys Today!
I guess they can't read very well, then... (Score:1)
"Activities other than copying, distribution and modification are not covered by this
License; they are outside its scope. The act of running the Program is not
restricted, and the output from the Program is covered only if its contents
constitute a work based on the Program (independent of having been made by running
the Program). Whether that is true depends on what the Program does."
So, what's your company's ticker symbol? (Score:1)
With losing FUD-attitudes like that, they're going
to wonder where all their revenue went and why their
software support costs are so high.
Sprint is swimming upstream (Score:1)
First they ignore you, then they laugh at you... (Score:1)
-Ghandi
Only one step left, fellows.
Some more legal jumbo (Score:1)
Good 'free' Layout program for Linux! (Score:1)
Check out the link below for more info...
Magic for Linux, BSD, etc. [digital.com]
Twinkie