Debian DPL Threatens to Leave SPI Over Sun Java
An anonymous reader writes "A three-week-long flame war in debian-devel over the new Java Distribution License has culminated in Anthony Towns, the newly elected Debian Project Lead, offering to separate Debian from its legal representative, SPI. This came as a response to SPI member John Goerzen's objections to the Debian project's interaction with Sun's legal team around the new JDL license without review from SPI's lawyers."
That's why my wife left me!
SPI wasn't trying to take the place of Debian's "governing body", it was simply trying to act as their legal representative.
The java packages are (if at all) only included in non-free, and that isn't part of the official debian. So yes, it may be a big fight, AFAIK the cause of the fight (the java packages in non-free) is only about an extra service Debian provides to it's users, not about debian itself.
So that would be the Debian Debian Project Leader?
This post brought to you by the Department of Redundancy Department.
I've got a fever and the only prescription is more COBOL.
Thats unpossible!
There are shills on slashdot. Apparently, I'm one of them.
Hmm ok I'm kind of surprised that the anti-Debian folks haven't jumped on this already. So....anyway, I guess that I'll inject my opinion anyway
Personally, I'm really glad we do have Debian. They don't shy away from politics, and I think that's a good thing. Why? Well, the Free Software/Open Source ideals are inherently political things. To shut up and just allow stuff to happen is almost completely opposite to the movements themselves.
Sure, you can claim that discussions like this hamper development. Maybe they do (although I doubt it). You can claim Debian is behind the times compared to Ubuntu or Gentoo or even Slackware depending on what you value. But these things do need to be discussed.
It might seem like a cop-out, but the following quote really stands out in my mind: "Geeks like to think that they can ignore politics; you can leave politics alone, but politics won't leave you alone.". RMS said that. I think it sums up the situation rather well.
On the one hand, it's nice to see a fundamentalist Linux distribution like Debian standing up on principle against encroachment of commercialization. On the other hand, non-fundamentalists like the rest of us are puzzled at how much time the Debian team wastes in throwing tantrums over license purity instead of shipping their next version. I guess I'm not a target user of their system since I just want Java to work on my system without being strip searched and violated.
One the one hand, SPI works for Debian. So they should go along with whatever Debian says. On the other hand, how can Debian expect SPI to do its job right if they are not included in legal discussions. Both sides have merit. Wow, and I haven't even read the article yet!
SPI is right to be pissed. They're Debians legal representation, and if some guy makes a stupid decission, without consulting them, it'll look baad for THEM (and not Debian). The legal implications of this thing could be huge.And as the guy said, you can't trust Sun to look iut for Debians best interests.
I do love "!" but not as much as I love "..."...
Bet they're regretting not running stable on Andy Towns now.
"Sure there's porn and piracy on the Web but there's probably a downside too."
Some people will do anything for a good cup of coffee.
Mod others as you would have them mod you.
It seems that Debian had a problem with parts of the Sun license, some Debian people had a private chat with Sun, and Sun basically said "don't worry about it, we won't enforce the license in that way". That's unremarkable.
What does surprise me is that the Debian people were silly enough to go "oh, that's alright then", and start distributing the software under this license, with nothing more than Sun's word, which they can't back up with any written communication whatsoever.
I don't get how SPI are involved though. What is the relationship between Debian and SPI? It seems SPI considers Debian to have agreed to this license on behalf of both Debian and SPI, but this doesn't really make any sense because the relationship is unclear. Can anybody clarify this?
Let me get this straight, the programmers behind Debian are threatening to give their legal team the boot? So it could be good, because sometimes lawyers suck, or it could be bad, because it implies Debian is about to make a huge legal mistake. Does anyone have a link to what the actual dispute is about, because the summary is lacking in details? (although it does have more than its fair share of alphabet soup: DPL, SPI, JDL)
Philosophy.
It's sad that Debian always provoke such ideologic wars as if no more important work and decisions are needed. What does it matter if Java is in none-free or else. Who cares much except users who just want to download a distribution as easy as possible.
IMO there are bigger issues at stake for Debian. The upcoming Ubuntu distribution is threatening to replace Debian as the leading distribution. The GPL v3 does nowhere fit in well into the DFSG. The Linux desktop while each year announced does not take place. It seems Debian people just fights these wars so nobody notices the real threads Debian is faced with.
I've myself switched to Ubuntu since I'm not happy with Debian anymore and I'm most probably don't write about the Linux desktop in the Debian mailing lists anymore etc. Any I'm quite sure quite a lot of others do the same. I've simply got tired of all this ideologic stuff.
O. Wyss
See http://wyoguide.sf.net/papers/Cross-platform.html
So basically you are agreeing that the Debian folks are fundamentalist licensing kooks who are being left behind by the computing world as it standardizes on distros like Ubuntu that aren't encumbered by loonies.
"Hmm ok I'm kind of surprised that the anti-Debian folks haven't jumped on this alread"
What more needs to be said after your comment?
First, without Debian, Ubuntu would be nothing. More importantly, as long as Debian exists, we know that we have access to an unencumbered, workable, and complete operating system / userspace. Should everything else hit the fan, we know there's still Debian.
Plus, stable's great for servers.
These are the problems:3 70245
3 70295
3 70296
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
The US places export restrictions on certain types of software (mostly encryption related stuff), which Sun has reflected in it's license. Since Debian can't/won't control which country has access to US-based mirrors then that means that they can't fuffill the obligation to screen out illegal downloads from certain countries and such. According to this license the work around Debian has used in the past is to have non-US for exported restricted software. Which is basicly you can only have the software on non-US based mirrors.
Debian has gotten rid of non-US for Sarge due to the relaxation of export controls by the U.S. government. But it would still violate Sun's licensing.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
This is Sun's obnoxiousness showing with this one:
""" (c) you do not combine, configure or distribute the Software to
run in conjunction with any additional software that implements
the same or similar functionality or APIs as the Software;"""
The bug author mentions the Java version of Python, but basicly it would make things like a distro shipping GCJ and Sun's java would be a licensing violation.
Obviously (in My eyes) Sun chooses this for two reasons:
A. To keep it's java runtime pure and functional. Avoids bug-inducing conflicts.
B. Help kill off Free software java implimentation.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
In Sun's License states that you can't modify any sort of copyright notices and whatnot. But by splitting the package up like Debian does they can't avoid modifying this stuff. Thusly Debian is violating Sun's distribution license.
Debian can ship non-free stuff in non-free obviously according to their bylaws.. but Debian doesn't have the authority to break OTHER people's licenses.
Sun says that this is OK and it's legal mumbo jumbo they can ignore. Debian's lawyer are basicly saying we can't violate Sun's licenses... ESPECIALLY without a discussion and you should pull the package from non-free until Sun fixes it's licensing so that Debian can use it legally.
This has happenned before with other software. Sun's license is shit and should be avoided by any sort of sane Linux distribution.
>Why? Well, the Free Software/Open Source ideals are inherently political things.
Nothing about using linux or writing OSS, requires me to jump on your political bandwagon.
I'm sure that open source is an ideal to you, but to most people it is not. It is software, and it is a business model to me and many others. It isn't inherently political to use it, and it's annoying when people try to drag the rest of us into their political battles.
Personally, as much as I use and love some open source software, I think that it is a good thing that developers have the freedom to release their software under whatever licensing they want, including a closed source one. I don't even think it would be a good thing if all software was open source. I think that closed source development is an important business model for many people.
n/t
my password really is 'stinkypants'
They should hire you to write the summaries instead.
Philosophy.
Similar things happened with Pine, which has similarly restrictive licensing. But Sun doesn't even publish source, which makes it even harder to deal with legally.
Those inanities are discussed in good depth at http://www.asty.org/articles/20010702pine.html. I highly recommend it as a good discussion of how bad licensing of "free" software can actually prevent it from being "open" and deliberately hinder people who want to work with it. Sun's licensing is similarly restrictive, with that caveat that Sun doesn't develop source code for Java. Washington University at least publishes their source code, even if you're not allowed to publish modifications of it under any circumstances.
Towns is turning this into a control issue when the Goerzen is just saying "Hey, it's not that tough to just run it buy our lawyers. Forewarned is forearmed."
I was part of a project that ended up blowing up. I was in SPI's position, just trying to keep everyone on the same page and help the person in control acheive goals. The person in control turned it into a control issue. It never was and I made every effort to make that clear. There was never any history to even suggest control issues. Finally, after much abuse, I left and so did several other people important to the project who knew what was going on. It turned out there were ideological problems, with the controller essentially wanting things one way while telling people things were to be another way in order to keep those people around.
Towns reminds me of the control freak of our own project. That was how it began - an irrational unwillingness to even hear what was being said and attributing everything as an attempt to control the project. Towns needs to step back and take a break. He needs some perspective. If there is anything he's not telling folks, he needs to come out with it. Because until that happens, anything he does is probably going to be to the detriment of Debian.
I've been following this thread on the list, and Towns' comment can only be taken as a threat if your adrenalin is pumping and your argument mode is set to Religion.
"I don't know, therefore Aliens" Wafflebox1
Ideologic war?
A small group of people has, it seems, in secret put Debian into a very dangerous legal position, without consulting the people who have the relevent legal expertise.
Non-free is not supported by Debian, but it is distributed anyway.
The "fight" is about licensing issues caused by Debian distributing java, as
discussed in the thread, as a follow-up to the comment linked by Slashdot.
I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
There are two types of OSS developers out there:
- the Linus type "have fun and cooperate" and
- the RMS type "OSS is religion"
The group of the relgious people however manages to silence the more pragmatic ones in the name of "higher ideals". But what is worse is that the concept of meritocracy fails too. Most of the people on debian-legal are no lawyers at all but amidst the blind the one eyed is king - even if color blind and short sighted.Example from debian-legal of a discussion about postgres: How could the situation be better exposed: "people (without any merits) looking for problems". That's what they are. All developers would reject a mailing list "debian-techadvice" where clueless people could make binding technical decisions, i.e. whether to use gcc 4.0 or 4.1.
One has to go through a notorious process to become a developer but it just needs an email client and a subscription to debian-legal in order to strangle 1500 developers. Time to change Debian back from a supermarket thing to one of the leaders of technology. Congrats Anthony!
It's pretty obvious that discussing java's license was going to be slow and painful and so it's also obviously why people would want to short circuit the whole process. But once you think about it for 5 seconds that's a really stupid plan. People are still going to discuss it but now they're going to be more pissed off.
Also this email is stupid. Debian needs SPI and when people start suggesting otherwise that means they are taking a vacation in retardo-land.
Here's the other thing. When I heard Debian had included java into their distro, I was like, "Wow. That must be a really improved license. Debian doesn't just include any old license into the distro." But a week later, I learned that 3 debian leaders had rammed java through without any discussion and really the license was very questionable. Debian is basically going off the informal Sun FAQ when they included. Does anyone even know that the FAQ was written by a lawyer or was it written by an intern in the PR dept?
So if non-free is not a part of Debian then who ever mirrors non-free is violating the license.
CORRECTION: Sun do publish the source code.
...well.. I think I speak for most of us when I say, "I'm going to continue using Ubuntu."
I love Debian, and I love Free software, but sometimes a guy just wants to run Java. You know what I'm saying? I think the distribution of Java would help linux immensely, and I'm all for seeing my beloved OS reach new levels of convenience and usability. Only way to oust Windows, you know...
You have to make nice to anyone doing you a favor for free, that includes lawyers.
And moreover there is nobody on debian-legal with any relevant legal expertise. I should maybe be renamed debian-ideolgues. It is indeed a big problem that Debian does not have any pragmatic legal expertise free of ideology that it can rely on. One has to understand that law is a non exact field of science - as opposed to source code. Software is deterministic (even race conditions are predictable), law is not. Nobody knows in advance how a court will decide.
Cheers.
So how many people consult their lawyer about the software license before purchasing/downloading the software? This seems to be a similar situation to me. It might have been wise to consult them but the tone of the SPI email should have been "it might be a good idea to talk to us about these sort of things since we are here to help you" and not "how dare you make a decision before you talked to us first". Lawyers are supposed to be their to help you with legal advice not to run your life for you...although it seems that many want to which is probably why so many end up in politics!
lol what
Who piddled in your Post Toasties this morning, Holmes?
Grow a sense of humour. Failing that, try going back to bed and getting up from the other side of it or something. Or just grow the fuck up already.
SPI is Debian, not the "legal representative". Debian, as a legal entity, Does Not Exist. When aj and the ftpmasters initiated distribution of the JDK, SPI was being contracted to the indemnification clause. If there is something to indemnify, SPI will have to shell out the dollars -- or sell out Debian's server farms, domain names and other assets, including copyrights and trademarks: all assets are SPI's, not Debian's.
That's the beauty of aj's bluff: hell yeah, Debian can detach itself from SPI (after some constitution change) but, oh, it cannot be called Debian anymore (the trademark belongs to SPI), nor use the twirl mark (ah-ha), huh, and it cannot use SPI's servers and other equipment either. This would amount to the separatist cabal being exiled from Debian, really.
It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
why don't you just get a big stick of dynamite and blast your worthless fatty body out of my plane of existence? right now. just get out of my plane of existence. go overreact to incredibly shitty jokes somewhere else. you give me AIDS. you wouldn't bother puking out this diseased crap unless you felt that you were the holy king of the tide.
just explode yourself now. you worthless piece of shit, you bring a bad taste to my entire fucking ocean. people like you give overreacting a bad name. you have officially shattered my hopes and dreams into a million pieces and slaughtered my family.
A three week public flame war? Incidents like this are why I have a hard time selling Linux as something other than a "high school kid" operating system. Regardless of the reasons behind it, there are much better ways to handle it than a flame war, let alone one that lasts three weeks.
A very good question, my good doctor. They are referring to Linux distributions. From that article:
There's a riot in the bazaar!
Quick! Let's hide in the cathedral!
But Sun doesn't even publish source
That's FUD, pure and simple - the source is available for download right on the same page as the rest of the JDK download links. You have to agree to one of two licences and have a (free) Sun Download Center account to get it, but it *is* available.
It's official. Most of you are morons.
This was bound to happen. Here you have a new guy at the steering wheel who has just become the head honcho of the GNU/Debian Linux project. So what is more important here? The wellfare of Debian as a whole or your building reputation as "the head honcho of...". This is just your regular bobo (IMO ofcourse) trying to make a name for himself while basicly ignoring the issues which are very relevant to Debian.
Here I see someone who is only doing the numbers without even caring what is being said and where things are going. "> SPI projects shouldn't be taking advice from Sun's attorneys.", puhlease... Ever heard of keeping an open mind? Or, if you wish to take it on the "Sun is our lesser Microsoft like evil empire" kind of approach the ancient old saying: "Know thy enemy". When the SCO issue was going on people also didn't go "We're not taking advice from SCO" because that is just the narrow minded kind of approach which will only get you into trouble. No, instead you hear them out, make them speak up their mind and then, and only then, will you start taking action based on the things they said.
But like I said; this crap was bound to happen. Debian has always been a distribution which keeps strict standards, so how does one make a better name for himself? Simple; take the whole issue one level upwards so people can say "Whoah, he's really protecting Debian's standards.". The next generation of people aren't always as great as the first, especially when their main goal isn't to help and push a certain project forward but has shifted to become part of that project due to its reputation and fame.
Well, the way I see it is simple: its not the rules, the policies, the lawyers, the software, etc. which is what makes Debian great. Its the people who show commitment every single day to keep Debian as great as it is. But sadly people like yourself don't wish to see this and only hammer on rules and policies, even if this means insulting and by-passing people who have been in their seat far longer than you have. It would really show of good leadership to make use of these people's expertise.
And during these times I have to say that Ubuntu begins to look very appealing.
I had wondered how debian could possibly agree to include that software in non-free with those license conditions.
c id=15398000
see: http://linux.slashdot.org/comments.pl?sid=186539&
I guess they "forgot" to check with the lawyers...
You can publish patches to the source code for Pine. You can publish modified binaries for Pine as long as you take them outside the UW versioning scheme so they don't get mistaken for actual UW products.
Gentoo and the BSDs, with their source-based ports systems, can all include Pine natively; since patching and compilation are done on the end user's computer. Debian could {by adding depends: for the complete development toolchain, and patching and compiling the source during preinstall}, but won't because it would seriously break the way their packaging system works {depends: is meant to be about running the package, not the preinstall phase, and mucking about with the toolchain shouldn't affect what's already been compiled}.
I personally don't have a problem with the Pine licence. And UW are currently happy about people downloading, compiling and using Pine; they're just too damn stubborn to solve everybody's problems in one fell swoop by switching to the GPL for PINE v5. But I can see why Debian are erring on the side of caution -- what will happen if some new top brass take over at UW, decide to make Pine a closed-source, commercial project, and begin vigorously pursuing past excesses of authority by software distributors?
Je fume. Tu fumes. Nous fûmes!
I think the other point of view is that Debian isn't a legal entity, it's just a bunch of cooperating people, and SPI exists to handle some formalities like owning servers and whatnot.
There seems to be an assumption that being amorphous, legally speaking, is some kind of shield. It's not. It's an invitation to drop the shit-bomb and cover everybody in sight. The way this works is that when the legal successors to Sun in owneship of Java (see below) have a legal hissy fit, their lawyers sue everybody in sight. The the judge dismisses the suits against every tom dick and harry and makes them go after the legal entity, unless somebody has made a very bad mistake. That's why corporations exist. They're the equivalent of legal fortesses for the individuals in an enterprise.
What should happen then is if SPI wins, great, if it loses, the individuals can continue on under a new corporation because of the open source licenses. The problem is that this is very close to legal chicanery. You're not supposed to protect yourself with legal fictions. Thus for the protection to work, people have to cooperate -- which sometimes means not doing what they want right away. If they don't then they expose everybody directly involved with the project, and everybody transitively involved for good measure. That's what lawyers do when they're looking to make money for their clients: they throw shit on everything and see what is allowed to stick. Even if it doesn't stick, it's an unpleasant experience.
Success in any enterprise depends on predicting the future, which is a dicey proposition at best. The main reason you need to consult lawyers is to avoid what other people's lawyers will do to you if your prediction turns out false.
In this case, take Sun. They are not doing so well as a business for the last several years. They're losing money. Let's hope they'll turn it around. But one thing that happens if this keeps going is that the stockholders decide they'd better cash out; the large stockholders can't do this because they own too much. So they start looking at selling the whole company, or liquidating its assets to turn them into cash. Java is currently the property of Sun. Next year it could be the legal property of another company, and one thing that company buys is the right to sue over uses of that property.
Now imagine a company that has a lot of cash that would have a strategic interest in gaining a hold over Java licensees. It's not hard. Imagine what they could do with their power to sue licensees and copyright infringers, not just for the immediate cash value but for the strategic value. Are they going to be reaonable and just go after the ftp maintainers?
I've been through this kind of thing before. Without consulting me, my business associate, who had a majority interest, entered into a casual legal relationship with an outside party. The arrangment seems reasonable and we're all reasonable likable folks. Then the outside party got into some trouble of his own not related to us at all. Suddenly he becomes less reasonable and likable. Next thing his lawyers were suing everybody in sight. We are getting hit with lawsuits from people we have no relationship with, who are really going after him, but since their lawyer's already working on the case the marginal cost of a second third and fourth lawsuit is nil. At that point I was very glad to have a corporation between me and them to take the liability.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
How is it possible to articulate an entire thought, enough to get you, an AC, a 5 rating, and yet, somehow, you misspell a simple word like "fulfill"/"fulfil".
I mean, come on, "fuffill"? What the hell is that.
Mark me as troll if you must, but for Pete's sake people, learn to spell basic words.
Anthony Towns is not suited for his position. It is obvious SPI should have been consulted on this matter. Java is flagship product by an industry heavyweight and Debian is a Linux cornerstone. You do not play fast and loose with this and then finish up by shooting from the lip as Tony Toons has done. As such, Anthony Towns presents more risk to Debian than Debian should be willing to accept and Towns should be demoted immediately at a minimum. Obviously he still needs training wheels which is not acceptable given his current position. Moreover, if the reasoning and reactions of Anthony Towns represents the current state of Debian brain trust then Debian is in trouble.
Let's be honest - most developers don't give a white sh@$#%t about what clauses and doubtful legal situations can arise of use of software, so Debian-legal thoughts are usually have been taken with lot of anger and confusion. Devs just want to work with software and apps, but D-L is full of idealists and clever individuals in legal field, who see things quite differently (and it is NOTHING bad about that), and so conflict is in full force.
But in this case, I *think* it is totally overblown and feels like that Debian-legal just want to say big f12#$%k off to Java usage in Debian - non-legal arguments like "I don't use non-free", "there are ALMOST working free software implementation in main", etc says almost everything about discusssion - it is not about LEGAL situation, but about fears that if Java will be aviable in non-free and will be supported by DD, CLASSPATH and other Java projects will slowly loose momentum they achieved so far now (Again, it is just my thougts after reading almost half of thread).
I can understand both sides, but thinking "We will get free implementation, we don't need stinkin Sun official implementation" sounds like too much dreaming. Let's be honest - it is simply not possible. Oracle won't use CLASSPATH, they will insist to use JRE. Other software will too. Yes, there will be desktop apps which will run on Free Software versions just fine - like Eclipse, lot of different small aps, but for enterprise it will be big NO-NO.
user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
he went with his gut feeling. he is sure that history will judge him in a positive light. and the javais will enjoy freedom and democracy
You obviously haven't worked with Pine source code. Mark Crispin apparently deliberately writes updates to Pine and the UW Imap package using the same libraries to break patches he doesn't like, such as patches to keep the server from treating every file in someone's home directory as an mbox file for IMAP, or years ago with the SSL patches published when UWash refused to publish their SSL-enabled version. Then they started threatening ths SSL patch authors with copyright violation, without ever actually looking at their code. (It turned out upon examination, a year later, to very definitely not be UWash code: the published patches weren't very good, but they worked.)
I know, I was involved in providing source patches for both, and the rewrites of the code between minor releases served absolutely no purpose but to break the patches. You can't hope to maintain patches in that hostile environment with the author, and you can't fork it. Mark has proven he's happy to use the copyright to interfere with packagers doing things he doesn't like: you should ask his ex-wife about how much worse he can get in person.
* lon3st4r *
No, I was missing it on the download page. Thank you for the correction. The conditions under which they publish it are still pretty difficult to work with: getting that "Download Center" account involves giving your home address, phone number, real name, and email account, all all required. But as near as I can tell, you can't easily bundle it into a DEB or RPM with those licensing restrictuions without some serious risk of violating Sun's licensing, for reasons that are pretty obvious if you look at the rest of the Debian history.
Whether one can compile what Sun actually publishes from that source is something I'll have XÀDðest.
See ya, close the door on the way out.
Is that a SCSI connector or are you just glad to see me?
M$ spent millions of dollars telling people that Windoze 2000 and XP were "based on NT Technology". NT itself stood for "Net Technology", making XP into a Technology Technology. What does it do? We don't know!
Friends don't help friends install M$ junk.
And there you will find the ass that tried to start a riot. I can do without Java and all the bull shit that goes along with it, thanks.
Friends don't help friends install M$ junk.
Here's a hint:
A lawyer should be consulted on a license- NOT a developer. It's a legal matter, not a coding matter.
There's a legal gotcha on the Java license that SPI, being the legal interface for the Debian
project, that if things go wrong, they'd have to absorb and deal with. Without SPI, each of
the devs involved with the project would be held individually liable for potentially millions
of dollars each (And that is exactly what is possible with the new licensing from Sun on Java).
Do you now see WHY devs shouldn't be the final call on a license?
I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
how do you get the fancy quote markers - looks a lot better than just italics
We've secretly replaced Slashdot with new Folgers Crystals - let's see if it notices.
I have a better idea: why don't you just pass by posts you disagree with or don't find funny, and let everyone else who finds a shed of humor in it chuckle? I'll bet you're one of those users who wastes mod points modding everyone down rather than modding really great posts up.
I don't want to stand in either side in this discussion - I don't use Java and I would be happy that world would go with Python, which is more portable and that stuff - but let's be real, Java is used heavily in enterprise and that is where Debian is aimed at and it would be very good, because hey, we are not here to make enemies, but friends :)
So what I want is clearly compromise solution, not flamewar. Problem is here that SPI and Debian-legal are in clear opposition in ANY deal with current Sun attitude. They want clear hands and not even vague hint about legal problems but there is no such possibilty, because we are living in real world, with real, different people with different goals. And legal world is fucked up that there can be any treat from anyone, so if you want to avoid that, better go to the wild and live in the tent.
And my pick is that you are not reading your own hint quite right. Lawyer should be "consulted". There are words "should" and "consulted", not "must" and "decide".
Let's be honest in what we believe. It is good that we have FSF, Debian-legal, and lot of clever minds who wants to avoid legal trouble. But in same time - let's be in touch with real world and real issues. Lot of Debian users - even faitful ones - wants to have easy instable and supported Java. No editing sources.list, no obscure packages, reading mailing lists, howtos... It is a fact. And nothing will change it.
user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
But prompted by this I've just had a look at those licenses and the FAQ.
Scheesh, what a mess, I very quickly got bored with Suns verbiage, my feelings can be summed up in two words.
Fuck them!
Maybe (probably) I'm missing some subtlety specific to Debian/SPI, but when I compare this situation to what I encounter in my professional life, it appears that SPI is in the wrong.
I work for a corporation. In my position, I frequently negotiate deals with software vendors, and this includes negotiating the contract terms. I am not a lawyer, however, so I work with our corporate attorneys in negotiating these contracts. They are responsible for understanding and explaining the legal ramifications of the contract terms, and I am responsible for understanding and explaining the business objectives of why we are trying to license the software.
Indemnification in particular is often a sticky subject in these negotiations. We usually get the indemnification clause that makes our lawyers happy, but in rare cases we do not.
In the end, however, it is notthe lawyer's job to decide whether or not we accept the terms of any contract. It is their job to advise me (and my managers) what risk we are taking with any given contract. It is then up to management to decide of that risk outweighs the business benefits we are trying to seek.
If somehow the Debian developers have gotten themselves in the position of needing permission from their attorney to sign a contract, then something has gotten seriously screwed up in their relationship. That would be like the CEO of McDonalds needing permission from some random fry cook to enter into a legal agreement. The attorney is to be an advisor, not a decision maker.
The net agrees: "fulfil" is a very obscure alternate spelling of "fulfill".
What's this about learning to spell?
feb@murgatroyd:~$ aptitude show java-packagen compressed Size: 270k
Package: java-package
State: installed
Automatically installed: no
Version: 0.24
Priority: optional
Section: contrib/misc
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
U
Depends: debhelper, fakeroot, coreutils | stat
Description: utility for building Java(TM) 2 related Debian packages
This package provides the capability to create a debian package from a
Java(TM) 2 distribution by just running make-jpkg <filename>.
This program currently works with the following Java(TM) 2 Runtime
Environments and Development Kits:
* Sun Microsystems(TM) 1.4 and 1.5 Standard Edition
* IBM(TM) 1.3 and 1.4 Standard Edition
* Blackdown Java-Linux 1.3 and 1.4 Standard Edition
How is having Java in non-free any better than a wrapper package that installs Java for you?
First you welcome the arrival of the new Debian overlord and now that he starts acting like one people cry out about ;)
In order to spread these ideas a project must be somewhat successful and Debian is losing more and more grounds here. The users are running over to Ubuntu and the developers are alienated - to check the last point you may follow the links in my OP and check who Joey Hess, Bruce Momsen and Tom Lane are.
Definition from wikipedia: Debian gets more and more trapped in nit picking discussions about GPL, LGPL, GFDL etc. which outside of the OSS world nobody can follow und thus losing users and developers.
Go back in american history and ask yourself if the concepts of helping each other, sharing and cooperating have been invented by RMS.
Removing support for postgres because that indirectly links to OpenSSL simply is zealotry. It harms the users and is an ivory tower discussion you can't possibly explain to an average human being.
The didn't consult their lawyers, they consulted the lawyers of the people they're entering into an agreement with- a formula for disaster. That's what the brouhaha is all about. That's what Debian-legal isn't happy about this- the developers did something that nobody in their right minds would do under any other circumstances. They went and listend to the advice of "opposing" counsel on a contract- the side making the agreement.
If you think this is a good idea, you might want to talk with my lawyer on a contract that I'm going to bind you to. Be more than happy to give you access to him, even- just don't be pissed off at me when I've screwed you out of a lot of time and possibly money.
I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
really. and not because i disagree with them, but because they are -- the truth is not always in the middle.
Debian has a flamewar over a license.
Microsoft said Vista will be out by end of 2006. Now it will be out by Q1-Q2 2007. Lots of people got sacked.
So, MS OS is mature because they throw out people (left for better oppotunities) for not delivering on some deadline, but Debian is a "high school kid OS" because they have a flamewar (lively discussion, to be politically correct) about a license.
I guess we'll see next week why Taliban is a better gov't than UK's constitutional monarchy, because in UK they have flamewars in politics. Give me break man.
You seem to think this issue came up because of of Debian's so-called dilligent pursuit of legal correctness.
No. This is issue comes up because Debian as an organization is sick and by and large an incompetent body that has all sorts of problem taking their tasks forward. Once again, instead of getting work done, the dysfunctional nature of the Debian organization raises its ugly head.
Mmmm, nothing like a good dose of smug. I wonder if Towns farts in a glass or if he just takes a straight shot.
I saw it on Slashdot, it must be true!
Good enough for Wikipedia, actually: http://www.spindazzle.org/green/index.php?p=48
You're just jealous because you didn't get FRWMF (First Reply to Whiney Mac Fanboy), so you could tell that to him directly.
Oh it's the same way at tech companies. We just don't have our emails up for everyone on the internet to see. Open source projects tend to air their dirty laundry out where everyone can see.
But honestly, I think few people who would "buy" Linux even know what Debian is, let along would have seen any of this on Slashdot.
Ubuntu is just as good (it's the same) and they don't have flamewars (that I'm aware of). Also, Debian doesn't represent all of Linux and GNU. Just like Red Hat doesn't represent all of Linux and GNU. It's really tough for people to understand that Linux, as an OS, is actually a bunch of little indepedent projects all stitched together by a distro maker.
“Common sense is not so common.” — Voltaire
Flamware might also be stuff made in the Flam fjord or a type of drum rudiment. Either of these would fit the discussion very nicely. Of course, the Real Ultimate Power version of flamware would be software where the license requires harsh criticism by means of sending flam-filled music bought in Flam.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
Whether the license allows free distribution is under debate.
It would appear to prohibit distribution along with the GNU java classes, for example.
It also seems to require indemnification from 3rd-party lawsuits - which is a potentially expensive license term (ie MS downloads java from debian, finds a legal issue, sues Sun, sun asks Debian to take care of the suit for them).
stop distributing java! its a blight on society anyway.
--- Liberty in our Lifetime
Y'know what? It's true. Nobody really gives a shit about legal wranglings between companies, until it affects the software they get at home. Most of the time, even that won't stir people out of their chairs.
It's just not that big of a deal for 99+% of the population.
"People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
So I went and took a look at the source. If Sun is successfully compiling from that mass of broken Makefiles and poorly written shell madness, they're braver and considerably luckier than I am. I have to assume that there are compilation tricks they're simply not including in that source bundle, based on failure to compile on 3 different OS's in a row.
Note especially that the RPM and similar packages are not compiled from source: they're typically installation wrappers around the Sun-published binaries, I assume because actually compiling it from the published source is so very painful and difficult. Has anyone actually compiled the SDK from the source code on a Linux system, other than Sun? I'd love to see your configuration and especially what compiler you got it to work with.
Obviously (in My eyes) Sun chooses this for two reasons:
A. To keep it's java runtime pure and functional. Avoids bug-inducing conflicts.
B. Help kill off Free software java implimentation.
what about
C. Prevent Microsoft from forking Java
Try reading the thread, not your prejudices!
"I don't use non-free" and "there are ALMOST working free software implementation in main" were not arguments against Java's licence. They were reasons given by some developers for not working on/worrying about this too much, along with the decision being improperly made, so it is the maintainers in legal peril if the shit hits the fan, not the project.
Hard to believe slashdotters tagged such a misleading post as "insightful"
Thanks for that comment, it's important to make that as clear as you have.