German Court Convicts Skype For Breaching GPL 309
terber writes "A German court has once again upheld the GPLv2 and convicted Skype (based in Luxembourg) of violating the GPL by selling the Linux-based VoIP phone 'SMCWSKP 100' without proper source code access. (Original is in German, link is a Google translation.) Skype later added a flyer to the phones' packaging giving a URL where the sources could be obtained; but the court found this insufficient and in breach of GPL section 3. The plaintiff was once again Netfilter developer Harald Welte, who runs gpl-violations.org. The decision is available in German at www.ifross.de (Google translation here)."
Damn (Score:4, Funny)
Re: (Score:2, Funny)
Sorry, I laughed.
Server Error? (Score:4, Funny)
Re: (Score:2)
Hopefully there's some monetary reward in this and that it will teach Skype and others a big lesson.
Re: (Score:3)
Re:Damn (Score:5, Interesting)
Re: (Score:3, Informative)
"You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange."
The thing is that Skype sold a physical produt (a phone), and
Re:Does GPL copyright expires? (Score:4, Insightful)
I take that partly back. It more completely passes into the public domain that a vast majority of software, because the source is easily available (copyright expiration wont make companies release the source).
It will (of course) be many years before any software copyrights expire (here in the States at least).
Correct terminology (Score:5, Informative)
Re:Correct terminology (Score:4, Insightful)
Re:Correct terminology (Score:5, Insightful)
Just out of curiosity (Score:4, Insightful)
Re: (Score:2)
Re: (Score:2)
This may be true (under paragraph 4 of the GPLv2), though its questionable what legal effect it has (since the GPLv2 is an open offer that you receive anew every time you receive software distributed under the license, and which you may accept, under its express terms, simply by redistributing the software.)
Re:Only if copying is not fair use (Score:4, Informative)
Re:Only if copying is not fair use (Score:5, Informative)
It's not fair use, because copies of software that are made for the purpose of using it are not covered by copyright in the first place. The law is explicit about this [cornell.edu]:
In short: It's not fair use (that's a different set of exemptions), but it is legal.
Re: (Score:3, Informative)
Re: (Score:3)
It's not that complicated.
Normally, Copyrigth law says that you aren't allowed redistributing or copying creative works that someone else created.
The GPL says, in effect: "We give you permission to do those things anyway, if you follow these rules
So, if you break those rules, you *don't* have permission, which means if you still copy, you're in violation of copyrigth law.
This is why the GP
Re:Correct terminology (Score:5, Funny)
Noone would be convicted of "breaching the GPL". The GPL is not an EULA. If you violate the terms of the GPL, you are (re)distributing without a license permitting you to do so (since the GPL, which you violated, is the only thing that gives you permission to do so), which is a copyright violation, not a GPL violation. I wish articles would get the specifics right.
You win today's "Pedant of the day award." Look for your certificate in the mail.
Re:Correct terminology (Score:4, Funny)
but you don't get a certificate. We're kindof assholes like that.
Re:Correct terminology (Score:5, Insightful)
On the contrary, a standard legal action against someone not in compliance with the terms of the GPL would be a simple copyright infringement case; the onus is on the defendant to show that they had a valid license (and met its terms).
Re: (Score:2)
Re: (Score:2)
Now that is stupid. The GPL doesn't say: "1. You can copy this code any way you like. 2. There are the following conditions..." It says "You may distribute copies of the code along with a copy of the GPL etc. etc. ". GPL'd software is _not_ given away.
Re: (Score:2)
I'm not saying that will happen to the GPL, but it's happened to other agreements or attempts to impose terms in the past.
Re:Correct terminology (Score:5, Insightful)
The court must "test" the GPL if the defendant claims that he accepted the terms. At that point the judge will attempt to decide whether the defendant did indeed keep up his half of the bargain, potentially restricting the power of the GPL agreement where local laws say otherwise.
The GPL is a fairly air-tight design, but there's nothing erroneous about its need for court testing. A judge can (and will!) strike various parts of the agreement if he finds them to be in conflict with either the law or the intent of the agreement. As a result, it's difficult to legally "prove" that a given type of agreement will hold up in court unless either that same agreement or a similar agreement is tested. The GPL has had sufficient legal testing to show that it will hold up in court.
If I'm not mistaken, your confusion stems from section 5 of the GPL, which explicitly provides for the fact that no proof of an agreement takes place. According to the GPL, you don't have to accept it to use the software. It falls back on standard copyright law in that case. Thus when an infringer is identified, he faces a double-edged sword. Does he claim that he did not accept the GPL, in which case he's on the hook for copyright infringement? Or does he claim that he did indeed accept the terms of the GPL, in which case he's on the hook for (I'll phrase this carefully just to annoy the "contract vs. license" folks out there
The GPL is an interesting experiment in using a legal loophole as the foundation for a distribution agreement. This case provides further evidence that the concept works as well in practice as it does in legal theory.
Re: (Score:2)
No, he won't. The GPL deliberately omits the severability clause commonly found in contracts. This means that if any part of it is contrary to local law, the entire thing is void in that jurisdiction.
What a judge can do is clarify the contract. "I interpret this clause to mean X, not Y."
Re:Correct terminology (Score:5, Insightful)
Hey, we're having a legal discussion here -- pedantry is necessary!
Re: (Score:3, Insightful)
Re: (Score:3, Interesting)
Right, we need to protect copyright at all costs! Maybe insert some DRM to protect us from evil capitalists!!
I wonder how many slashdotters would agree that the idea to limit copyright to 12 years or so means that linux will be put in the public domain for anyone to do whatever they want, and to hell with the gpl.
Not trying to troll, but its funny to see people quote copyright law line and verse when it serves them.
Re: (Score:3, Insightful)
Re: (Score:2)
This is a popular open-source myth, but doesn't seem true under the little US case law applying the GPL (consider Progress Software v. MySQL AB), or under the express terms of the GPLv2 (which
Conflict and Chaos in the Hive Mind! (Score:4, Funny)
Conviction for copyright violation - Bad!
What's a loyal drone to believe anymore??
Re: (Score:2)
Re: (Score:2, Funny)
Re:Conflict and Chaos in the Hive Mind! (Score:5, Informative)
The GPL is permissive, and thus turns the usual function of copyright on it's head.
In other words, usually when people violate copyright it's through an act that increases the spread of the information, and prosecuting them for it would restict that spread. In contrast, when people violate copyright by failing to abide by the GPL, they themselves are restricting the spread of the information and prosecuting them restores it.
If one (e.g., a "loyal drone") consistently believes that spreading information is good and restricting it is bad, there is no contradiction.
Re: (Score:2)
GPL is permissive... But it prevents you from distributing something with out making the source available...
I happen to like GPL V2 but this statement is just not as slanted as the term Digital Rights Management.
You find it permissive because it gives you permission to do something you want while preventing someone else from doing what they want.
What I don't get is why is putting the source on the internet not good enough?
Re: (Score:3, Insightful)
The GPL is permissive the same way the 13th amendment is permissive. Both prevent you from taking away the rights of others.
What I don't get is why is putting the source on the internet not good enough?
Not everyone has access to the internet. Had they included a written offer to send the source code by post for a reasonable shipping charge they'd probably have been fine.
Re: (Score:3, Informative)
No, because under copyright law, you never had that right in the first place. The GPL gives you *more* rights than you had, it just doesn't give you the right to not give the same rights to others.
Not Really (Score:2)
Re: (Score:2)
Say what you will about the negatives of vendor lock-in (an argument with merit), cool gadgets mean big bucks. Take away profit, and where do iPhones come from?
Re: (Score:3, Insightful)
What drives innovation is a desire to capture a particular market share for a demand, in effect providing a new supply stream for an existing demand, or hoping to create demand due to a new supply stream for a new product or feature.
In
Re: (Score:2)
It doesn't restrict the others from doing better as long as they write their own stuff. It allows the originator to restrict them from taking his work and passing it off as their own long enough for the originator to make a profit. This worked well way back when the monopoly grante
Re: (Score:2)
1. Copyright in general is a good thing, but has too long of a term and his horribly misused today.
2. Anyone who does anything whatsoever that would be necessary to catch and convict someone violating copyright over P2P is a horrible totalitarian Nazi.
3. Copyright really only benefits the record companies, who are parasites.
4. It's possible to make money as a musician without copyright or the evil record companies, and is therefore possible today. Ignor
Misleading or incomplete summary. (Score:5, Informative)
Stop this rubbish (Score:2)
Re: (Score:2, Funny)
English translation of the decision (Score:2)
The story's link to the translated version of the decision doesn't work - probably because Google is only translating the <frameset> document, not the inner frames.
This link should work [google.com], though
Source Code (Score:5, Informative)
Can also check out this link for more info here [wifiphone24.com]
Holy Larva Batman! (Score:3, Funny)
It's a wonder why Microsoft hates the GPL, Balmer is afraid of GRUB(s)
The interesting part (Score:5, Interesting)
with the phone that contained URLs to the GPL-
license and to the source code . The articles do
not make any statement on whether the source code
contained all modifications, but they do not claim
otherwise.
The court decided that providing only an URL to the
license was not enough and that the whole license
should have been included in printed form.
So far, so good. Now the interesting part is that
according to the judge, providing a link to the
source code is only acceptable for software that
is provided on the internet. For software that comes
preinstalled, the source must also be delivered with
the device.
This decision seems extremely strange to me. It is
not what I read in the GPL v2. Here is the relevant
part:
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the
following:
a)
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your cost
of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c)
Re:The interesting part (Score:5, Insightful)
I think the judge looked at the paragraph a bit further on in that section where it talks about providing access to the source as a download from a server, and noted that that case is explicitly allowed only when the software itself is also distributed as a download. That led him to the conclusion that clause B that you quote, when it talks of "medium customarily used for software interchange", means exactly what it says: an actual copy on some storage medium, logic being that if it allowed downloads from servers then it wouldn't have been neccesary later to explicitly allow downloads from servers. Combine that with failing to include the license text when the license says plainly in section 1 that you must include a copy of it's text and the judge's decision doesn't seem unreasonable.
And I know the issue of downloads of source has been discussed, and IIRC the FSF's position is that it's not acceptable on it's own. Network servers can be taken down, files on them can be removed, some recipients may not have Internet access but none of those cases lifts the obligation to provide source code. The only way a distributor can guarantee he'll always be able to meet that obligation is to be prepared to provide source on a physical medium. The case of providing downloadable source for downloadable software was actually viewed as falling under 3a, not 3b, that is source code being provided along with the software itself, which makes a world of difference in the distributor's obligations.
Re: (Score:2)
a download link would be ok, but that you would be obliged
to keep it valid over the next three years. It would be a
violation if the link became invalid within those three
years, but until then, no violation has occured.
If this reasoning is not acceptable, you could still avoid
to ship the code with the product, if you provide a note
that you will ship it upon request. But isn't that just
what you're doing with the URL? It's just another form of
contact add
Re: (Score:3, Interesting)
Using the same mechanism as the RIAA to uphold freedom is good.
Using the same sore-winner attitude as the RIAA and punishing people for the heck of it is bad.
Umm I think they misread one part (Score:3, Informative)
Rough translation (but better than google):
"Later a note was included with the device, which said it used GPL software and a URL where the source code is available - but this was not enough for the court. The GPL only permits this for software that is delivered over the Internet."
Doesn't that get covered by 6 b) 2):
"6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
(...)
b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (...) or (2) access to copy the Corresponding Source from a network server at no charge."
Or maybe it didn't come as a permanent offer, in which case they might be talking about 6 d):
"d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. (...)"
I wonder... (Score:2)
If Microsoft will applaud the GPL developers for exercising their intellectual property rights...
When you think about it, if Skype had misappropriated WinCE, they'd be looking at a lot more damage than just releasing their source code...
No conviction (Score:3, Insightful)
A conviction is for criminal court. Copywrite law falls under civil law. No one from Skype is going to jail and no one is going to pay a huge fine to the government. However, the organization that won this case could potentially get a tidy sum.
Let's just pile onto the inaccuracies of the summary for this article. Let's hear it for inflamatory, add-pumping summaries!
Re: (Score:2)
...I decided that that instruction meant that I could begin every telephone conversation with a violator of the GPL with magic words: We don't want money. When I spoke those words, life got simpler. The next thing I said was, We don't want publicity. The third thing I said was, We want compliance. We won't settle for anything less than compliance, and that's all we want.
(from the keynote address of the plone conference 2006 available here : http://www.geof.net/research/2006/moglen-notes [geof.net] )
Hooray for Harald! (Score:2, Interesting)
He is swamped with submissions from folks claiming this company or that is in violation of the GPL. I submitted one myself about a year and a half ago. Nothing ever came of it. Not because the company is innocent, but because Harald has very few resources to go after the
Re: (Score:2, Insightful)
The case could easily be made that the violation was deliberately and intentionally obscured to make discovery difficult, and then the penalties could be even greater.
Re:Hooray for Harald! (Score:5, Informative)
Wow, did you drink some SCO FUD? Copyrights are never nullified because of lack of enforcement, and I dare you to find an example. Not enforcing them may limit your ability to collect damages, but at any time you can send an injunction to make them stop.
What's needed is enforcement of copyright law:
506. Criminal offenses
(a) Criminal Infringement.
(1) In general. Any person who willfully infringes a copyright shall be punished as provided under section 2319 of title 18, if the infringement was committed
(A) for purposes of commercial advantage or private financial gain;
2319. Criminal infringement of a copyright
(a) Any person who violates section 506 (a) (relating to criminal offenses) of title 17 shall be punished as provided in subsections (b), (c), and (d) and such penalties shall be in addition to any other provisions of title 17 or any other law.
(b) Any person who commits an offense under section 506 (a)(1)(A) of title 17
(1) shall be imprisoned not more than 5 years, or fined in the amount set forth in this title, or both, if the offense consists of the reproduction or distribution, including by electronic means, during any 180-day period, of at least 10 copies or phonorecords, of 1 or more copyrighted works, which have a total retail value of more than $2,500;
(2) shall be imprisoned not more than 10 years, or fined in the amount set forth in this title, or both, if the offense is a second or subsequent offense under paragraph (1); and
(3) shall be imprisoned not more than 1 year, or fined in the amount set forth in this title, or both, in any other case.
If you're using a substantial amount of GPL'd code beyond the rouge developer taking code, that should be enough to know you're willfully infringing. Being a for-profit company should be enough to prove "for commercial advantage". At which point they should be strung up on criminal charges and sent to jail like with SOX regulations. That's how it should be, note there's no minimum amount to make (3) go into effect and send them away for a year, even at a $0 "retail value" as long as you can prove *they* earned money on it.
Definitions... (Score:2)
Hrm. I just had an interesting thought which applies here but I'm sure folks have covered already. Somewhere.
So, you can copyright source code, no problem. I know there is a bit of confusion about the meaning of the term "derivative work" and here's an example.
Let's say I have a trivial program, say, "Hello World" or something like that. What exactly is the copyrighted bit here? Is it the source - that is, the exact language representation used - say, C++ or Pascal or Assembly? Or is it the instructions
Re: (Score:2)
Ask yourself this. Suppose you wrote a book. Suppose I go and translate it into another language (without a license from you) and begin selling copies. Suppose I record someone reading it onto audio tape and begin selling copies. Suppose I run it through a scanner and turn the scanned images into a PDF and begin selling it. What does copyright law hold on those scenarios? Answer that and you've answered your questions.
Short form, copyright applies to the source code. That copyright carries over into any de
Re: (Score:2)
The question is, do I deserve compensation for translating the work into a foreign language when I didn't do that translation?
The way I see it, the translator created a new actual work by changing the language. Sure it has the same story or whatever as the original, but the value that guy added is the translation, not the idea.
That's why I said the things of value are the creation of new ideas, the means to distribute them, and the ability to use them. The ideas themselves are not very valuable, so copyin
Re: (Score:3, Informative)
Certainly.
Provided that you (the copyright holder) generate them (by running the compil
Support your local GPL enforcer! (Score:2, Informative)
So, instead of talking about the GPL on
Hm, no a german court did _not_ "upheld" the GPL (Score:3, Interesting)
What me rely wonders is this wording A German court has once again upheld the GPLv2 .
No! A german court did not upheld the GPL. No court is interested in the GPL. the court honoured copyright law. The authors of the code in question are the copyright owners. The company distributing the code is not a copyright owner. The license is completely irrelevant.
Notpicking mode on:
A license could be void if it contained illegal terms, like: you agree to hand over your first born son, and his first born son and also his up to the 17th generation to follow to (insert your name here)
In this case the license would be void. Not copyright! You still had no right whatsoever to distribute the code / IP of the legal owners.
The court did not uphold the GPL. It only decided that Skype violated the GPL and in doing so violated copyright law If you violate a BSD or MIT license you violate copyright law as well.
To uphold a license you would need to challenge the legal-ness of the license. So instead of suing Skype for breaking copyright law you would need to sue the author over using an illegal license. However there is no real applicable law here. You could construct a case probably by having a license that also encourages murder and rape
angel'o'sphere
Skype was NOT convicted (Score:3, Informative)
They convicted SMC, who makes a Skype phone, of the GPL violation because they didn't include the source code with the phone. NOT skype
how can every slashdot mod and user be completely wrong?
Re:Slashdot Hypocrisy (Score:4, Funny)
In any case you have completely misrepresented peoples positions and conflated different groups.
Don't look now but I think your strawman is on fire.
Re:Slashdot Hypocrisy (Score:4, Funny)
Re:Slashdot Hypocrisy (Score:4, Insightful)
What do you mean? Opposing the RIAA means supporting the user's freedom. Enforcing the GPL also means supporting the user's freedom. There is no contradiction.
Re:Slashdot Hypocrisy (Score:5, Insightful)
In a perfect world, we wouldn't need the GPL, but we don't live in a perfect world. The GPL attempts to use the (imperfect) legal tools that do exist (read: copyright law) to accomplish its goal of access to source. The spirit behind it has little to do with copyright.
Re: (Score:2)
I would be pretty pissed if I spent 7 months writing a book with an agreement that I make some money on the sales only to have someone violate my copyright and take credit for my novel and I go broke. d
Copyright needs to exist to make sure authors are recongized and yes, compensated for their work. If you do not agree to pay for it then dont buy it. There are creative commons licenses for creative works such as free books too. But copyright enforces credits on who writes what. Even i
Re: (Score:2)
Copyrights are like guns... (Score:2)
That's basically what I said. As for your original comment, I see nothing hypocritical or contradictory about opposing the MAFIAA's use of copyrights while supporting legal action that enforces the GPL - the two are worlds apart. What's irrelevant is the fact that they fall under the same legal rubric. The MAFIAA's extortion and blatant abuse of the legal system vs. enforcing the GPL with a properly filed suit against a party
Re: (Score:3, Insightful)
What we're opposed to are the draconian enforcement and perpetual lengthening of copyright expiration.
So...no. I don't see where your argument has solid ground to stand on.
Re: (Score:2)
Have you ever stop to consider when software covered under the GPL will actually become public domain and no longer be bound by the terms of the GPL?
Like it are not, all those extensions that benefit the (MP|RI)AA also end up benefiting the open source world as well, only the benefits to FOSS will be a little later in coming in theory.
Re:Slashdot Hypocrisy (Score:4, Insightful)
I assume you're talking about the benefit of copyleft (i.e., enforcing the sharing) versus plain permissive (e.g. Public Domain). The thing is, plain permissive really isn't all that much worse than copyleft. In contrast, (from the RIAA's perspective) public domain is very much worse than proprietary. So, having a longer copyleft term doesn't benefit the Free Software community nearly as much as having a longer copyright term benefits the RIAA.
Besides, old music remains valuable to society. For the most part, old code doesn't.
For both of those reasons, it is unnecessary for Free Software to have long copyright, and thus most Free Software advocates oppose copyright extensions. The fact that the RIAA et al. abuse copyright only confirms that position more.
Re: (Score:2)
Re: (Score:3, Insightful)
Assuming Linus lives to at least 70 (born in 1969), the Linux kernel will not be released into the public domain for another 101 years or so. And that's only the parts he wrote. I think it's safe to say that the FOSS community will not be harmed by the release of what will then probably be an ancient and rather quaint bit of software from the turn of the la
Re:Slashdot Hypocrisy (Score:5, Insightful)
First and probably the most important is that not everyone who dislikes the **AAs voice their opinion for the GPL and vice versa. This means that you will see people vocal about one and not the other and when putting it all together, you see the static noise level to be about the same but totally neglect the fact that it is coming from different sources.
Second, And probably just as important, Most of the anti **IA people I speak to are in the position because of the what and how RIAA and the MPAA are handling things not because of their right to handle them. When they run threats of legal action in order to extort a settlement from the people who would seem to have the most difficulty defending from it, something is wrong. It would seem that if protecting against copy right infringement would be important, it would be important to go after everyone doing it and not just the people who stand a chance of having a successful defense.
I don't know of the GPL people going after widowed grandmothers who don't even own a computer and make them spend hundred if not thousands of dollars to prove that. I don't know of any GPL people falsely accusing people of infringement by infecting their computer and snooping around. I don't know of GPL people going around and writing virus and jamming networks with infect material in order to extract revenge on people and ruin their computer install because you used a legal service to do something legal.
If and when they start doing stuff like this and everything else the **IAs are doing, I will be just as vocal against them as some are for the **IAs. As it is, I don't usually comment in the RIAAs or whatever unless it is something really bad. So don't confuse the noise level on both as being from the same people or for the same reasons, they aren't.
Re: (Score:2)
"Now we will see the same people who oppose RIAA/MPAA copyrights cheering the copyright action that enforces open source. Don't you see that you can't have it both ways?"
And adding further humor, Skype was developed by the guys who developed Kazaa. They knew what Kazaa would be used for; they certainly weren't naive enough to think that it would be used only for Linux distros and Creative Commons materials.
At any rate, it's perfectly justified to ask to have something both ways. For example, many peop
Re: (Score:2)
Re: (Score:2)
Re: (Score:3, Insightful)
We also (And I think I speak for everyone of favor of copyrights 'round here) would like to see copyr
Re: (Score:2)
2. The RIAA/MPAA's member companies leverage copyrights and patents in contravention of fair use exceptions to obtain excessive control over the works in question.
3. The RIAA/MPAA's member companies intentionally provide inequitable compensation to all but the top tier of performers, given the revenues received by those companies, all the while claiming that file sharing d
Re: (Score:2)
Actually, there's one thing they can do about it: press copyright infringement charges. But I can almost guarantee that anyone who would even dream of saying such a refrain in front of a judge as their defense in such a case would find themselves in a bit of a pickle. So in actuality, people who would choose the path you describe are almost invariably hypocrites... as
Re: (Score:2)
That's not quite correct. When software is loaded into RAM, that RAM is a copy for copyright purposes (and making copies is the sort of thing that's generally prohibited). However, if you own the copy of the software you're starting from, then this is permitted under the law without a license
Re: (Score:3, Informative)
You are all wrong (Score:2, Informative)
This is opposed to items (say a CD) which says that you may not copy them, which is a lie since it is LEGAL to copy things for personal use. What you may not do, is to distribute them for your gains.
Re: (Score:3, Informative)
'for your gains' is not a required condition.
Re: (Score:3, Informative)
The court said including a website address to where the source could be downloaded wasn't good enough. I'd like to know why that wasn't good enough. Is it only because the text of the GPL wasn't included?
This doesn't look like a win for the GPL. This looks like a major pain in the ass. I didn't even know that distributing a copy of the GPL was a requirement
Re: (Score:2, Informative)
Section 1:
"You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you
Skype is good? (Score:2)
I'm not saying this in order to troll, I'm just trying to correct widespread misperceptions about Skype, characterised by the belief that it's in some way better than yet another phone company. If you can, use a SIP-based IP phone instead. There are lots of SIP programs to choose from, they inte
Re: (Score:3, Informative)
Re: (Score:2)
A translator is listening to a German radio broadcast and busily writing down what he hears. He says nothing for a long time, but keeps writing. A nearby woman is growing impatient for the translation.
Woman: What are they saying? What are they saying?
Translator: Just a minute, ma'am. I'm still waiting for the verb.
German re
Re:Beginning of the end for open source? (Score:5, Insightful)
"Holy shit, someone's actually enforcing GPL v2! Open Source is going to die!" is, excuse my language, but fucking retarded. Find something else to blow up about. I hear the sky is falling.
Re: (Score:2, Flamebait)
I have read here on
This is why I support the BSD and MIT licenses. This creates fud for other more free licenses.
But if I were developing software I would be very carefully on what I include or link to in my program. Its not worth losing your job to it.
Yes, RMS some software is always going to be closed because teh MBAs and ac
Re: (Score:2)
Re: (Score:2, Insightful)
Countless businesses use GPL software for all sorts of reasons - whether internally or for bespoke systems. Skype deciding not to isn't going to harm the cause. On the other hand, Skype getting away with not following the term
Re: (Score:2)