|By Jeremy Geelan||
|September 20, 2003 12:00 AM EDT||
Dear Mr. McBride,
Recently you wrote an "open letter to the open source community" published September 9, 2003 by LinuxWorld. This reply is from a group within the open source / free software community. Because you addressed your letter to our community-at-large, we thought we should answer you ourselves.
Our community isn't organized hierarchically like a corporation, so it has no CEO or overall leader in that sense, except that Linus Torvalds leads Linux kernel development and Richard Stallman leads the GNU Project and the Free Software Foundation (FSF). We have written this letter together on the website Groklaw, which is a research and news site currently dedicated to covering developments in the news about your company.
Quite a number in the group are software engineers, including contributors to the Linux kernel. Others are proprietors of Linux-based businesses or executives or employees of Linux-related businesses. A few of us are lawyers, one is a paralegal, one a stockbroker, at least one is a physicist, a couple are journalists, one is a retired policeman, another a retired truck driver, others are in or have been in the military, and some work or have worked in government. We also have experienced UNIX programmers among us who personally witnessed the history of UNIX since its inception, participated in its development, and know the software well. One of us is a non-technical grandmother who installed GNU/Linux herself recently and fell in love with the software. We are a large, international and varied group of people, which is appropriate because GNU/Linux is developed and used worldwide and the open source community to which you directed your letter is both global and diverse.
VIOLATIONS OF THE GPL AND COPYRIGHT LAW
Our first purpose in writing to you is to draw to your attention that there are consequences to violating the GNU General Public License, the GPL.
You have continued to distribute the Linux kernel, despite alleging that it contains infringing source code. Simultaneously, you are attempting to compel purchase of "Linux Intellectual Property" licenses for binary-only use, the terms of which are incompatible with freedoms granted under the GPL.
According to the GPL, any violation of its license terms automatically and immediately terminates your permission to modify or distribute the software or derivative works. Note the wording of the GPL:
"4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
"5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it."
Releasing software under the GPL is not the same as releasing it into the public domain. Authors retain their copyrights to software licensed under the GPL. Even when authors assign their copyrights to someone else, such as to the Free Software Foundation, the copyrights remain valid, but with the new owner. Therefore, subsequent to termination of your permissions under the GPL, you are in the unhappy position of violating the copyrights of the software authors, if you continue to distribute their software. Under copyright law, you are not allowed to distribute at all without their permission -- and they have chosen to grant that permission only by means of the GPL.
YOUR INVOICES WILL PROVOKE LEGAL ACTIONS
With regard to the invoices you have said you will mail out by October 15, we caution you that we believe that any such action will expose you to civil lawsuits under both federal and state consumer protection laws, as well as to possible criminal prosecution and penalties should state and federal agencies, attorneys general, and district attorneys decide to get involved, which we fully intend to ask them to do upon receipt of any invoice from you.
For just one example of state consumer protection laws, we suggest that you read Article 22-A of New York's General Business Law, Sections 349 and 350. Similar laws are on the books in other states. The Linux kernel developers also have copyright law to rely upon to protect their rights. Linux-based businesses may also avail themselves of other commercial laws, such as trade libel law.
Should we receive invoices from you, we will initiate civil actions under the anti-fraud and consumer protection statutes wherever we live, according to our respective circumstances. We also intend to contact our state attorneys general to request that they seek criminal as well as civil penalties against you, in addition to injunctive relief. In addition, we will file complaints with the FTC and other federal and state agencies, as appropriate. Some individuals have already sent letters to legislators in their respective states and in Washington, DC.
We purchased GNU/Linux software in good faith, and we chose it precisely because it is released under the GPL. We will not accept your attempt to charge us a second time for a product that we have already bought and paid for, most of us from vendors other than yourself. Furthermore, we accept no license other than the GPL for GNU/Linux software. For one reason, it is the permission to modify our software that we treasure. Here is how the GPL FAQ explains the value of being able to modify software:
"A crucial aspect of free software is that users are free to cooperate. It is absolutely essential to permit users who wish to help each other to share their bug fixes and improvements with other users."
This is one key to the justly renowned stability and security of GNU/Linux software, and we have no intention of reverting back to the Dark Ages of binary-only software permissions, having already made the conscious and informed decision to escape from and avoid such like the plague.
WE DO BELIEVE IN COPYRIGHT LAW
Despite the false impression you attempt to paint in your letter -- that we are a lawless community that doesn't respect copyright law -- we wish to inform you that we do believe in copyright law. It is the legal foundation upon which the GPL is built, and we rely upon it to protect our rights. If the Linux kernel developers didn't believe in copyright, they would have released their software into the public domain instead of choosing to license it under the GPL.
You are required by law to respect the Linux kernel authors' copyrights, as well as the license they chose to use, the GPL. It is hypocritical to complain of alleged violations of your copyrights and licenses while at the same time disregarding the equivalent legal rights of others.
YOU HAVE SHOWN US NO INFRINGING SOURCE CODE
You have refused to show us, much less prove, any infringing source code. If you showed source code that proved to be infringing, it would be immediately removed. Linus Torvalds, Richard Stallman, and the FSF's attorney, Eben Moglen, have each told you so repeatedly as men of honor. You refuse to let that happen. Why? It appears to us it is because you have no infringing source code to show.
Your most recently filed 10Q shows your UNIX business declining, even as Linux continues to grow in market acceptance. If you are refusing to show the source code to prevent its removal because you wish to charge a perpetual toll, in effect riding on the coattails of the more successful GNU/Linux software, that is a shameful tactic. You cannot compel Linux developers to retain your source code, even if any infringing code existed. An alleged infringement is curable by removing the infringing source code. If you can identify any infringing source code, please do so, prove it is infringing, and let us remove it, because we surely do not want it.
Even more shameful would be to try to destroy, co-opt, or make proprietary, the labor of thousands of good-hearted volunteers who did not volunteer to work for you, do not wish to be exploited by you for your monetary gain, and have already chosen to release their creative work under the GPL.
If your concern is that evidence will be removed before your claims against IBM and its counterclaims against you can be heard in court, that is a baseless concern, because the Linux source code is and always will be publicly available for review by any court. Secrecy is not an option under copyright law. If you make allegations of copyright infringement, you must offer proof.
We do not need or want your legacy UNIX source code. It would be a violation of the GPL to accept proprietary source code into the Linux kernel. If there is proprietary source code in the kernel, we want it removed just as badly as you do, perhaps more so, because we believe in the GPL. Just because people will not walk through your front door to buy your software, you have no right to compel them to pay you through the back door for what they did not voluntarily choose to buy. You must, therefore, try to find a viable business model without our compelled participation.
Any claims you may have against IBM are between you and IBM. It is a contractual dispute to which we are not parties. If you have any valid contractual claims, they will be settled in a court of law, but your remedies in that dispute lie with IBM and IBM alone, not with Linux users. Even if some misappropriation were to be established, you cannot collect twice for the same transgression. Further, we note that to date you have filed no copyright claims against either IBM or Red Hat.
SOURCE CODE CAN BE BOTH IDENTICAL AND LEGAL -- THE BSD CONNECTION
Since the beginning of this year, you have claimed that there is infringing source code taken from your version of UNIX and illegally donated to Linux. But when two examples were shown at SCOForum, neither supported your allegations. For six months, we have listened to analysts say that some source code appeared similar, if not identical. Yet what both they and you failed to investigate and determine is where that source code originated, how and by whom it was added to the software at issue, to whom it now belongs, and who is allowed to use it.
There is BSD source code in Linux which is legally there, and it will, of course, be identical to or similar to BSD source code in your software. The BSDi lawsuit revealed that the AT&T source codebase includes a great deal of BSD source code. Caldera itself also later released "Ancient UNIX" source code under a BSD-like license. Consequently SysV contains substantial amounts of source code that SCO and others have already licensed for use and that the open source / free software community may legally use.
WE POLICE SOURCE CODE EFFECTIVELY -- DO YOU?
It took only a day or so for the source code shown at SCOForum to begin to be identified by members of the open source community. If we do not police source code effectively, as you claim, why were they able to so quickly identify the code? You, in contrast, had no idea where that source code came from, or to whom it belonged, or you surely would not have used it to attempt to prove "infringement" of "your" source code. The evidence indicates it is your due diligence system that is broken, not ours.
If the legal departments of corporations represent to Linus Torvalds that they have ownership rights to source code they donate, what more can reasonably be expected? Do you have methods in place to prevent GPL source code from being improperly inserted into your proprietary software? Would you be willing to allow us to check for such violations? We particularly wish to check your Linux Kernel Personality (LKP) source code. We suspect that there may be GPL source code taken from the Linux kernel and used in LKP without authorization, and we challenge you to prove this has not happened by showing us your LKP source code, throughout its complete development history to date.
Any proprietary software company can police its own source code in Linux by checking the Linux source code. The Linux kernel is open to the public. If you see any source code that you believe is yours, you have only to speak up, and it will be immediately removed, upon confirmation that it is infringing. That is what you should have done. It's a superior feature in the open source method that all you need to do is your own due diligence. Any interested party can verify that no copyright infringements are taking place, simply by looking at the published source code. This creates strong incentives for honesty and provides far greater protection for copyright holders than your proprietary system, where source code can be misappropriated and hidden and no one can check for it, short of a lawsuit. Perhaps that is why proprietary software companies are so often locked in legal battles, something you rarely see in the open source / free software community.
With regard to broken systems, how could it happen that while working with the Linux kernel source code for years -- and your company did -- you never noticed any infringing source code? And how do you explain that you released the allegedly infringing source code in your own distributions of Linux for years without noticing it was in there?
If Linux did contain infringing UNIX source code that you failed to notice for years, or noticed but did nothing to prevent, despite the fact that the Linux source code was freely available at any time for your review, it raises questions about your internal processes and procedures for protecting your copyrights rather than demonstrating any purported "breakdown" in the open source methodology.
INDEMNIFICATION IS A RED HERRING
Anyone considering surreptitiously inserting proprietary software source code into Linux knows they would be quickly discovered and identified by name. That is your indemnification and your protection. We believe our system for policing source code is far more exacting and successful than your own.
On the subject of indemnification, we note that the software license which you propose to sell does not offer indemnification from lawsuits brought by other companies. And we think we should inform you that warranties are permitted under the GPL:
"1. . . .You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee."
We do not feel we need it; the open source method protects us sufficiently, but it is certainly negotiable if we wish to pay for it.
Proprietary software companies regularly file lawsuits against each other for copyright infringement, patent and trademark violations. Microsoft has been found guilty recently in several cases, but despite the fact that the GNU Project was begun in 1984 and Linus Torvalds began the Linux kernel in 1991, there has never been a claim of copyright infringement that we know of in all those years, let alone a finding of guilt. The record shows which method has done a better job of policing source code, which reveals that your call for indemnification is, to put it bluntly, FUD.
WE RESPECT THE LAW
With regard to your talk of having experienced a DDoS attack and your request that we aggessively police the community, your request is like us asking you to police Microsoft to ensure it never again breaks antitrust law or never again violates anyone's patents, trademarks, or copyrights.
Just because you are both proprietary software companies, it doesn't follow that you can control what Microsoft does or should be criticized as if you condoned their actions just because you are in the same proprietary camp. Whether it is individuals or companies that break a law, it is wrong, but it reflects only on the individual perpetrator. We expect you to make that distinction for us, as we do for you.
There is a legal process for such matters. Not everyone accepts as established fact that there was an attack. The doubt is based on the fact that your employees were quoted as saying that reports of an attack were untrue and that you took your servers down for maintenance yourself and then had trouble getting them back up again. We observed that the "attack" kept business hours, Utah time, for much of that week. If the information your employees provided was false and there was in fact a network denial of service attack on your servers, we naturally abhor such behavior. Your implication that we would feel otherwise is deeply insulting and offensive.
We would think, however, that a capable information technology company that sells web services software would have the technical know-how to handle a DDoS attack, if that is really what happened. Most such companies do handle them without being brought to their knees for a week. We are glad that you say you have since learned technical steps you can take to protect yourself in the future.
WHO MAKES UP THE OPEN SOURCE COMMUNITY TODAY?
Kindly bring up-to-date your concept of the people and organizations that make up the open source community. Your letter attempted to portray us as a counter-cultural fringe element. On the contrary, the truth is that our community is very much in the mainstream already and includes many of the largest and most successful businesses today, including IBM, Red Hat, Merrill Lynch, Lucent Technologies, Unilever, Verisign, Dell, Amazon, Google, Dreamworks, Los Alamos National Laboratory, Oak Ridge National Laboratory, the US Department of Defense, the US military, and many other federal, state, and local governments and governmental agencies, including, by the way, the town of St. George, Utah.
You can read a list of companies and governmental agencies that use GNU/Linux at Linux International's "Linux Success Stories" webpage. The Linux Documentation Project also has such a webpage, called "Powered by Linux!", as does the Linux in Business website. The Linux Counter calculates there are currently 18 million users of GNU/Linux software.
With so many businesses, educational institutions, governmental organizations, and individual users switching to our software, we must be doing something right.
LINUX ALREADY HAS A BUSINESS MODEL
Your inability to make your Linux business a success, while unfortunate for you, parallels your company's failure to make your UNIX business a success. Perhaps the problem isn't Linux, the GPL, or the open source business model.
Economist Amy Wohl is of the opinion that "The Open Source Community Has a Business Model" and one that is successful. Ms. Wohl is an analyst who has been covering IT for nearly 30 years and who currently comments on the commercialization of new and emerging technology. Here are her comments, which we include with her kind permission:
"As an economist, let me assure you that Open Source has a business model. It simply isn't one that a traditional company like SCO, which expects to be paid for source code, can figure out. There are still lots of companies that can charge for source code, but only when the source code they are offering is valued by customers because it is unique or convenient or offers other recognized value. Other companies (IBM is a good example) charge for their Linux-compatible middleware source code, but honor the Open Source community by supporting it with technical and financial assistance and by strongly supporting the open standards that permit customers to choose to use Open Source code when they prefer it and purchased source code when they find it, for whatever reason, more valuable. Then, as many posters have noted, IBM extends its business model into the future by providing services to help customers plan, design, implement, and customize whatever combinations of hardware, open source, and proprietary code the customer prefers.
"That is the new business model and it seems to be a very successful one."
DUAL LICENSING IS AN OPTION
We suggest that you ask your attorneys to explain the Lesser General Public License (LGPL) to you. If they are not familiar with the LGPL, contact the Free Software Foundation, and they can help you to resolve your misunderstanding and confusion about the GPL and how it works and can explain to you how the LGPL can help your business to thrive, should you insist on continuing with the old proprietary software business model. Companies such as MySQL distribute software simultaneously under both open source and proprietary licenses, a practice that is acceptable, if not ideal, under the GPL.
It is not a violation of the GPL to sell software released under that license. As the GPL FAQ points out, "The right to sell copies is part of the definition of free software." The "free" in free software refers to freedom, not that you can get it gratis. Many of us have paid for our free software, simply because it's more convenient than downloading it or as a way to thank the wonderful folks who developed and shared it with the world. If you're looking for a successful business model, you might consider the tried and true model of satisfied customers.
We have prepared a research document with links to evidence supporting our position and other resources that you may find helpful, including information about the GPL and the LGPL and how they work. The Inquirer is making our research document available online. We hope it will help you understand our position better and prove a useful resource to you and others interested in this controversy. We also believe it demonstrates that we have right on our side and that we will win.
Thank you for writing to us. We appreciate the opportunity to answer your letter. We trust you will give our response due consideration. Thank you for your time.
Members of The Open Source / Free Software Community at Groklaw
Copyright © Groklaw, 2003 Verbatim copying of this letter is permitted in any medium, provided this notice is preserved.
|wpsmoke 09/23/03 03:30:13 AM EDT|
Thank you LinuxWorld for printing the letter in full.
It very comfortable to read on your site with the black text on white with no flashing distractions and adjustable text size and, of course, the content is a comfort to read as well.
I hope you will be able to leave it up and accessible because I feel it's importance and relevance will increase as the open source movement swing from reactive to more proactive responses to The SCO Group.
I came in via Google but have added you to my Favourites list.
|Kevin Michel 09/22/03 04:41:09 PM EDT|
It is sad to watch SCO slowly destroy itself, and do so much damage to the software community and to development in general. They used to be a proud member of a larger culture, they have now marginalized themselves and are going to spend their last days, and dollars, settling lawsuits from the people they have harmed.
|A Concerned Mormon 09/22/03 11:11:59 AM EDT|
All of which does not consider the religious dimension to the situation.
SCO/Caldera is headquartered in the state of Utah. A majority of the people who live in Utah are Mormons.
Why is this important?
If you are not familiar with the tenents of the faith, Mormons are supposed to be a "peculiar" people. In simple terms through faith and actions they are to act as living examples for everyone else. (see http://www.lds.org for details).
One of the things that Mormons have, which other christian denominations do not have are temples. In the temple is it possible to baptise those who've already died and perform other ordinances for them that had not been done during their lives.
The temple is very important to Mormons. To gain entry to the temple you must hold a temple recommend, and to gain a temple recommend you have to truthfully answer 10 questions that your bishop will ask you. The questions are about moral probity, and are such that all christians would agree with them - much like all christians agree with the 10 Commandments. While it is possible to lie to the bishop most Mormons I know (myself included) would find it impossible to do so.
Many of us joke about using our temple recommends as ID when obtaining a loan - in Utah at least a temple recommend is taken very seriously indeed.
So where does this put Darl? He's supposed to be a devote Mormon. Does he hold a current temple recommend? Could he answer yes to the question "Are you honest in your dealings with your fellow man (and woman)?"
Consider Non-Disclosure Agreements. A temple recommend would overide a non-disclosure agreement by it's very nature. Where does this leave the staff of SCO/Caldera?
Possibly Darl truly believes that SCO source code has made it's way into Linux, and that IBM is guilty of putting it there. In that case he would be clear to answer yes to his Bishop.
However considering the various half truths, lies, prevarcations, etc. that have emmanated from SCO/Caldera I'd say that any Mormon who is working there are present should not hold a temple recommend, and should in fact be seeking new employment.
To work for a firm that operates in such a manner would not be spiritually healthy.
|Shaun 09/21/03 01:08:26 PM EDT|
I helped write the letter at Groklaw.
First we only identified ourselves as a small part of the community. We did not claim to represent the whole OSS community. Second we stated that the contractual dispute was between SCO and IBM, which is true.
What we did state was that the OSS community does have legal means against SCO should they follow through on their threats. Again this is true.
The letter was based on facts and placed notice to SCO that we at Groklaw are aware of the law enough to persue legal action. It also placed that same information into the hands of the entire OSS community.
The letter itself went through 6 drafts and several corrections were made to it over the week it was worked on. Many people added statements and I helped specifically in the making the point of correcting the timeline of the GNU project and the beginning of Linux development, as well as stating that it must be based on facts only and not add to the FUD.
PJ wrote the letter effectively, honorably and with proper intent. She has been an outstanding leader because she payed attention to each comment posted and followed through on them wisely.
|Rod 09/21/03 10:00:03 AM EDT|
I find it logical, yet less than honorable that the authors would take a position that "the dispute is between IBM and SCO...".
I understand the concept behind it, but I just think it less than honorable for the folks here (who offer themselves up as "the Linux community") would "cut IBM loose" so readily....
|Thomas Frayne 09/20/03 11:43:56 PM EDT|
LinuxWorld makes many of the same points that I made in my analysis, but I think you pulled your punches.
I have been following developments in the legal battle between SCO and IBM, which has escalated to a battle between SCO and the entire Open Source Community. Here is my analysis of the open letter from Darl McBride, CEO of SCO, to the Open Source Community. The letter is on the web at
The referenced article and an earlier interview with Mark Heise are full of lies and misrepresentations. I'll go through them, and discuss lies I saw by referencing and quoting from the web pages that contain the truth.
McBride: "There is no question about the affiliation of the attacker – Open Source leader Eric Raymond was quoted as saying that he was contacted by the perpetrator and that “he’s one of us.” To Mr Raymond’s partial credit, he asked the attacker to stop. However, he has yet to disclose the identity of the perpetrator so that justice can be done. "
What Raymond said in http://linuxtoday.com/infrastructure/2003082400126NWCYLL
"I don't actually know who the attacker is, and don't want to; the person who phoned me was not him, but an associate -- what spies call a cut-out. It is clear that the attacker was no script kiddie; he was able to come up with a subtle, selective attack that only took out a subset of sites on the subnet that hosts SCO and looked like a site outage from the outside."
McBride: "The second development was an admission by Open Source leader Bruce Perens that UNIX System V code (owned by SCO) is, in fact, in Linux, and it shouldn’t be there. Mr Perens stated that there is “an error in the Linux developer’s process” which allowed Unix System V code that “didn’t belong in Linux” to end up in the Linux kernel (source: ComputerWire, August 25, 2003). Mr Perens continued with a string of arguments to justify the “error in the Linux developer’s process.” However, nothing can change the fact that a Linux developer on the payroll of Silicon Graphics stripped copyright attributions from copyrighted System V code that was licensed to Silicon Graphics under strict conditions of use, and then contributed that source code to Linux as though it was clean code owned and controlled by SGI. This is a clear violation of SGI’s contract and copyright obligations to SCO. We are currently working to try and resolve these issues with SGI."
Perens was misquoted. What he said was:
"Slides 10 through 14 show memory allocation functions from Unix System V, and their correspondence to very similar material in Linux. Some of this material was deliberately obfuscated by SCO, by the use of a Greek font. I've switched that text back to a normal font.
In this case, there was an error in the Linux developer's process (at SGI), and we lucked out that it wasn't worse. It turns out that we have a legal right to use the code in question, but it doesn't belong in Linux and has been removed.
These slides have several C syntax errors and would never compile. So, they don't quite represent any source code in Linux. But we've found the code they refer to. It is included in code copyrighed by AT&T and released as Open Source under the BSD license by Caldera, the company that now calls itself SCO. The Linux developers have a legal right to make use of the code under that license. No violation of SCO's copyright or trade secrets is taking place. "
McBride: "In copyright law, ownership cannot be transferred without express, written authority of a copyright holder. Some have claimed that, because SCO software code was present in software distributed under the GPL, SCO has forfeited its rights to this code. Not so – SCO never gave permission, or granted rights, for this to happen.
Transfer of copyright ownership without express written authority of all proper parties is null and void."
Here he quotes something true, in order to make a point which is a lie. He implies that licensing under the GPL is a void attempt to transfer copyright ownership, when the copyright law gives the copyright owner the right to license his or her work, and does not require any special form for the license. The GPL is such a license. More about this later.
McBride: "Use of derivative rights in copyrighted material is defined by the scope of a license grant. An authorized derivative work may not be used beyond the scope of a license grant. License grants regarding derivative works vary from license to license – some are broad and some are narrow. In other words, the license itself defines the scope of permissive use, and licensees agree to be bound by that definition. One reason SCO sued IBM is due to our assertions that IBM has violated the terms of the specific IBM/SCO license agreement through its handling of derivative works. We believe our evidence is compelling on this issue."
Ah. Nothing wrong here, you say? Well, is a magician lying when he misdirects your attention? Not exactly. However, if you think someone is trying to misdirect your attention, it might pay to consider what he might want to direct your attention away from. Here's a quote from earlier in the article:
McBride: "This means that Linux end users must take a hard look at the intellectual property underpinnings of Open Source products and at the GPL (GNU General Public License) licensing model itself."
This is the only mention of the GPL in the article, so perhaps he does not really want us to take a hard look. However, let's take him at his word, and take a hard look.
A few days earlier we find an interview with Mark Heise at:
This article contains another set of lies and misrepresentations
SCO has misquoted Sec 301 by claiming that Section 301 preempts the GPL, when, in fact Sec 301 reinforces the GPL by stating that no other laws can govern the rights given to copyright owners by Sec 106. Copyright owners typically exercize these rights by licensing their products.
"CNET News.com sat down at SCO Forum earlier this week with attorney Mark Heise, a partner with Boies Schiller & Flexner, which is representing SCO, to talk about how the case is affecting the company, the open-source community, and public licenses that require sharing such as the General Public License, or GPL."
"If you look at the terms of the GPL and the terms of copyright law, copyright law governs. It is the exclusive authority regarding the use, distribution, etc., of copyrighted material. In the GPL, (there is a section that) specifically says it applies only to the use and distribution. In other words, the exact same topics that are covered exclusively by the Copyright Act are covered by the GPL. Section 301 of the Copyright Act says the Copyright Act pre-empts any claims that are governed regarding use, distribution and copying. We believe that although the GPL is being tossed into the fray, it is pre-empted by federal copyright law."
The GPL does not say "use" in that section. See http://www.gnu.org/licenses/gpl.html
It says :
"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.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. 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:
* a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
* b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
* c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)"
Here is the quote from the copyright law:
"Sec. 301. - Preemption with respect to other laws
On and after January 1, 1978, all legal or equitable rights that are equivalent to any of the exclusive rights within the general scope of copyright as specified by section 106 in works of authorship that are fixed in a tangible medium of expression and come within the subject matter of copyright as specified by sections 102 and 103, whether created before or after that date and whether published or unpublished, are governed exclusively by this title. Thereafter, no person is entitled to any such right or equivalent right in any such work under the common law or statutes of any State."
This is why SCO can't ask that IBM's counterclaim be tried in a state court in Utah, with a favorable judge. This section says nothing about preempting licenses like the GPL.
SCO has no chance to invalidate the GPL. The law explicitly provides in
"Subject to sections 107 through 121, the owner of copyright under this title has the exclusive rights to do and to authorize any of the following:
(1) to reproduce the copyrighted work in copies or phonorecords;
(2) to prepare derivative works based upon the copyrighted work;
(3) to distribute copies or phonorecords of the copyrighted work to the public by sale or other transfer of ownership, or by rental, lease, or lending; ..."
The GPL, far from being pre-empted by the copyright law, is relying on rights explicitly given to copyright owners by the copyright law.
Now why would SCO make such a fuss over the validity of the GPL, and then just drop the subject? For that, you only have to look as far as IBM's counterclaim to SCO's suit. IBM's counter claim can be downloaded from
Go to the section: Update 10 Aug 03: The full 45-page IBM Answer and Counterclaim text, a 22-KB download, is
In its counterclaims to SCO's claims, IBM outlined a proof that SCO violated the copyrights of thousands of Linux developers. Here is a summary, indicating the paragraph numbers: The claim basically states that SCO accepted the GPL by distributing significant portions of code covered by the GPL (76); that the GPL prohibits SCO from certain actions (77); that SCO breached the GPL by its
All the countlesss Linux contributors are eligible to sue SCO for copyright infringement. Even better, they can file criminal complaints for copyright infringement against the officers and directors of SCO.
Ah. There's the reason: they're trying every trick they can to stay out of jail. But it's too late. They're already too deep in the pit, and they won't stop digging.
"We've discovered that after shows 80% if leads that people get, 80% of the conversations end up on the show floor, meaning people forget about it, people forget who they talk to, people forget that there are actual business opportunities to be had here so we try to help out and keep the conversations going," explained Jeff Mesnik, Founder and President of ContentMX, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
Jul. 27, 2016 10:30 PM EDT Reads: 1,397
Internet of @ThingsExpo, taking place November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with the 19th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world and ThingsExpo Silicon Valley Call for Papers is now open.
Jul. 27, 2016 10:00 PM EDT Reads: 2,648
The IoT is changing the way enterprises conduct business. In his session at @ThingsExpo, Eric Hoffman, Vice President at EastBanc Technologies, discussed how businesses can gain an edge over competitors by empowering consumers to take control through IoT. He cited examples such as a Washington, D.C.-based sports club that leveraged IoT and the cloud to develop a comprehensive booking system. He also highlighted how IoT can revitalize and restore outdated business models, making them profitable ...
Jul. 27, 2016 09:45 PM EDT Reads: 1,992
"delaPlex is a software development company. We do team-based outsourcing development," explained Mark Rivers, COO and Co-founder of delaPlex Software, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
Jul. 27, 2016 08:00 PM EDT Reads: 2,027
We all know the latest numbers: Gartner, Inc. forecasts that 6.4 billion connected things will be in use worldwide in 2016, up 30 percent from last year, and will reach 20.8 billion by 2020. We're rapidly approaching a data production of 40 zettabytes a day – more than we can every physically store, and exabytes and yottabytes are just around the corner. For many that’s a good sign, as data has been proven to equal money – IF it’s ingested, integrated, and analyzed fast enough. Without real-ti...
Jul. 27, 2016 07:30 PM EDT Reads: 1,084
"There's a growing demand from users for things to be faster. When you think about all the transactions or interactions users will have with your product and everything that is between those transactions and interactions - what drives us at Catchpoint Systems is the idea to measure that and to analyze it," explained Leo Vasiliou, Director of Web Performance Engineering at Catchpoint Systems, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York Ci...
Jul. 27, 2016 06:45 PM EDT Reads: 2,058
I wanted to gather all of my Internet of Things (IOT) blogs into a single blog (that I could later use with my University of San Francisco (USF) Big Data “MBA” course). However as I started to pull these blogs together, I realized that my IOT discussion lacked a vision; it lacked an end point towards which an organization could drive their IOT envisioning, proof of value, app dev, data engineering and data science efforts. And I think that the IOT end point is really quite simple…
Jul. 27, 2016 06:45 PM EDT Reads: 1,161
A critical component of any IoT project is what to do with all the data being generated. This data needs to be captured, processed, structured, and stored in a way to facilitate different kinds of queries. Traditional data warehouse and analytical systems are mature technologies that can be used to handle certain kinds of queries, but they are not always well suited to many problems, particularly when there is a need for real-time insights.
Jul. 27, 2016 04:30 PM EDT Reads: 1,864
Big Data, cloud, analytics, contextual information, wearable tech, sensors, mobility, and WebRTC: together, these advances have created a perfect storm of technologies that are disrupting and transforming classic communications models and ecosystems. In his session at @ThingsExpo, Erik Perotti, Senior Manager of New Ventures on Plantronics’ Innovation team, provided an overview of this technological shift, including associated business and consumer communications impacts, and opportunities it ...
Jul. 27, 2016 04:30 PM EDT Reads: 198
You think you know what’s in your data. But do you? Most organizations are now aware of the business intelligence represented by their data. Data science stands to take this to a level you never thought of – literally. The techniques of data science, when used with the capabilities of Big Data technologies, can make connections you had not yet imagined, helping you discover new insights and ask new questions of your data. In his session at @ThingsExpo, Sarbjit Sarkaria, data science team lead ...
Jul. 27, 2016 04:15 PM EDT Reads: 1,134
Extracting business value from Internet of Things (IoT) data doesn’t happen overnight. There are several requirements that must be satisfied, including IoT device enablement, data analysis, real-time detection of complex events and automated orchestration of actions. Unfortunately, too many companies fall short in achieving their business goals by implementing incomplete solutions or not focusing on tangible use cases. In his general session at @ThingsExpo, Dave McCarthy, Director of Products...
Jul. 27, 2016 04:00 PM EDT Reads: 1,741
Is your aging software platform suffering from technical debt while the market changes and demands new solutions at a faster clip? It’s a bold move, but you might consider walking away from your core platform and starting fresh. ReadyTalk did exactly that. In his General Session at 19th Cloud Expo, Michael Chambliss, Head of Engineering at ReadyTalk, will discuss why and how ReadyTalk diverted from healthy revenue and over a decade of audio conferencing product development to start an innovati...
Jul. 27, 2016 04:00 PM EDT Reads: 1,059
WebRTC is bringing significant change to the communications landscape that will bridge the worlds of web and telephony, making the Internet the new standard for communications. Cloud9 took the road less traveled and used WebRTC to create a downloadable enterprise-grade communications platform that is changing the communication dynamic in the financial sector. In his session at @ThingsExpo, Leo Papadopoulos, CTO of Cloud9, discussed the importance of WebRTC and how it enables companies to focus...
Jul. 27, 2016 03:30 PM EDT Reads: 975
SYS-CON Events announced today that 910Telecom will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Housed in the classic Denver Gas & Electric Building, 910 15th St., 910Telecom is a carrier-neutral telecom hotel located in the heart of Denver. Adjacent to CenturyLink, AT&T, and Denver Main, 910Telecom offers connectivity to all major carriers, Internet service providers, Internet backbones and ...
Jul. 27, 2016 11:00 AM EDT Reads: 729
SYS-CON Events announced today that LeaseWeb USA, a cloud Infrastructure-as-a-Service (IaaS) provider, will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. LeaseWeb is one of the world's largest hosting brands. The company helps customers define, develop and deploy IT infrastructure tailored to their exact business needs, by combining various kinds cloud solutions.
Jul. 27, 2016 10:30 AM EDT Reads: 1,233
Manufacturers are embracing the Industrial Internet the same way consumers are leveraging Fitbits – to improve overall health and wellness. Both can provide consistent measurement, visibility, and suggest performance improvements customized to help reach goals. Fitbit users can view real-time data and make adjustments to increase their activity. In his session at @ThingsExpo, Mark Bernardo Professional Services Leader, Americas, at GE Digital, discussed how leveraging the Industrial Internet a...
Jul. 27, 2016 09:45 AM EDT Reads: 485
The cloud market growth today is largely in public clouds. While there is a lot of spend in IT departments in virtualization, these aren’t yet translating into a true “cloud” experience within the enterprise. What is stopping the growth of the “private cloud” market? In his general session at 18th Cloud Expo, Nara Rajagopalan, CEO of Accelerite, explored the challenges in deploying, managing, and getting adoption for a private cloud within an enterprise. What are the key differences between wh...
Jul. 27, 2016 09:30 AM EDT Reads: 2,084
SYS-CON Events announced today that Venafi, the Immune System for the Internet™ and the leading provider of Next Generation Trust Protection, will exhibit at @DevOpsSummit at 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Venafi is the Immune System for the Internet™ that protects the foundation of all cybersecurity – cryptographic keys and digital certificates – so they can’t be misused by bad guys in attacks...
Jul. 27, 2016 09:15 AM EDT Reads: 1,378
The best-practices for building IoT applications with Go Code that attendees can use to build their own IoT applications. In his session at @ThingsExpo, Indraneel Mitra, Senior Solutions Architect & Technology Evangelist at Cognizant, provided valuable information and resources for both novice and experienced developers on how to get started with IoT and Golang in a day. He also provided information on how to use Intel Arduino Kit, Go Robotics API and AWS IoT stack to build an application tha...
Jul. 27, 2016 09:15 AM EDT Reads: 1,181
Amazon has gradually rolled out parts of its IoT offerings in the last year, but these are just the tip of the iceberg. In addition to optimizing their back-end AWS offerings, Amazon is laying the ground work to be a major force in IoT – especially in the connected home and office. Amazon is extending its reach by building on its dominant Cloud IoT platform, its Dash Button strategy, recently announced Replenishment Services, the Echo/Alexa voice recognition control platform, the 6-7 strategic...
Jul. 27, 2016 09:00 AM EDT Reads: 483