As the parent poster stated: "in EXCHANGE", or in other words you're paying for it. You can't rebut an statement if you've only bothered to read half of it.
Parent poster is right: western nations with higher tax rates generally do offer more stable, safer, societies, and corporations are all too happy to take advantage of that without making their contribution to that society.
And yes, governments do have the right to tax you. You can bleat about libertarianism all you like, but elected governments get to make the laws, and you can either abide by them, or piss off somewhere else without any pesky laws. I understand Somalia is nice at this time of year.
The damn naturally occuring volcanoes give off more greenhouse gasses in a week than 50 years of modern innovation has ever produced.
Is that why global carbon emissions briefly decreased when Eyjafjallajokull erupted in 2010, grounding the majority of European flights?
Yeah, you've bought the bullshit and are trying to peddle it on. http://tamino.wordpress.com/20...
You keep using the word dim as an insult towards me yet seem to repeatedly be unable to grasp the concept that offering the open sourcing of the Minecraft server source code as a solution to the problem he has decided to create is identical to asking for the Minecraft source code, I'm not sure why you struggle with with such a simple concept, but apparently you do. Maybe you're, well, a bit dim?
I've used the term dim once, so I'm not sure why you think I "keep" using it; however, I've come to the conclusion that it's pretty well merited here. I'll say it once more, in the probably vain hope that you'll actually read it: Wolfe has neither asked for nor offered the open sourcing of Mojang's server source code. Once again: you made that part up yourself.
I can't quite tell if you're a bit dim, or just being deliberately obtuse here. Wolfe has never demanded that Mojang release their proprietary source code (and he doesn't have the legal right to do that anyway). He's saying, correctly, that CraftBukkit cannot legally be distributed under its current license. It can certainly be argued that this is a petty move - he is basically making the entire project unavailable to everyone - and I'm in two minds about that myself, but it's a bit more than just a "pet peeve". It's two years of his work (and Wolfe was one of the biggest contributors to the project) under basically false pretences.
It's now up to Mojang to decide how to proceed. They have several choices, only one of which is re-licensing their server code under the GPL (and I very much doubt that will happen). They could alternatively shelve the Bukkit project (they are after all working on their own modding API), or they could meet Wolfe in court.
The problem is not entirely Mojang's fault, but they have basically been storing up trouble for themselves since the release of CraftBukkit in January 2011 by not dealing with the license issue then. It seems pretty clear they wanted the Bukkit project to continue (let's face it, it's certainly helped their bottom line), up to and including acquiring the project, but it was foolish of them not to immediately clarify the licence.
By the way, using the blanket insult "you FOSS zealots" says a lot more about you than it does me. You know nothing about me, or my overall stance on software licensing.
Stop being dense. He's not demanding the "Minecraft server source code" and no one who's actually paying attention has ever claimed that. He's saying that his GPL'd contributions can't legally be distributed in CraftBukkit along with Mojang's proprietary classes, and in that respect he's correct.
Of course this has been the case all along - CraftBukkit has never been legally licensed - but until now both Mojang and the Bukkit development team have basically swept that problem under the carpet. What gotten Wolfe (and no doubt other) contributors annoyed is that Mojang concealed their ownership of Bukkit until the current Bukkit team basically threw in the towel due to the difficulty of keeping CraftBukkit up-to-date wrt. Minecraft. At the point, Mojang basically said, "no problem, we've actually owned Bukkit all along!".
This is the fault of the original Bukkit team (who are now Mojang employees, or have been) for their poor licensing decisions, and also the fault of Mojang for failing to deal with the licensing problems either initially or when they clandestinely acquired the Bukkit project. Wolfe and other contributors may be accused of poor judgement for continuing to contribute to such a legally shaky project, but the original licensing problems are not theirs, and their contributions were made under the false belief that Bukkit remained a community-owned project.
Wolfe didn't do the original decompiling of Mojang's code and combining it with GPL'd and LGPL'd code. That was done by individuals who were since hired by Mojang as developers for their own planned modding API.
So while Wolfe's contributed a huge amount of GPL'd code to Bukkit/CraftBukkit, he's not the original infringer. If Mojang want to sue, they'll basically have to sue their own employees (whom they hired knowing full well that they'd been releasing decompiled Mojang code).
CraftBukkit has never been legally licensed. That does not however invalidate the copyright that Wolfe (and every other contributor) has over his own contributions. And he does maintain copyright since Mojang have never required contributors to agree to a Contributor License Agreement.
He's not trying to ransom it back. At no point has there been a suggestion that Wolvereness wants any kind of material gain for his code. He's unhappy that the GPL code he contributed to Bukkit is now being distributed by Mojang in breach of the GPL.
There's an awful lot of guesswork and name-calling going on here, and a sense that the argument is divided into "Mojang sux!" and "Mojang rulez!" camps. The truth is of course, way more complex. Here's an attempt to lay out some (hopefully) objective facts, mixed with my subjective opinion. Disclaimer: I've been involved with Bukkit for over 3 years as a plugin developer and contributor to the forums, and (very minor) contributor to the Bukkit project itself.
* The Bukkit project was started late 2010/beginning 2011 as a replacement for hMod, an earlier server mod, by 4 people: Dinnerbone, EvilSeph, Tahg and Grum.
* The Bukkit project consists of two main deliverables: the Bukkit API, licensed under the GPL, and the CraftBukkit server, licensed under the LGPL.
* The Bukkit API contains no Mojang code. It's the Java JAR against which Bukkit plugins are compiled.
* The CraftBukkit server contains a copy of the Bukkit API (via Maven shading), some original Java classes in the org.bukkit.craftbukkit Java package (most of which either implement Bukkit API interfaces or serve as glue code between Bukkit and Mojang's own code), and decompiled/semi-deobfuscated copies of Mojang classes from Mojang's official minecraft_server.jar.
* Effectively craftbukkit.jar contains code with three separate licenses: GPL, LGPL, and Mojang's proprietary license. My opinion: "what the hell were the Bukkit team thinking when they chose this license model?"
* Mojang were presumably aware of CraftBukkit from the start, it being the pre-eminent server modding platform, but chose not to take any legal action over the inclusion of (decompiled copies of) their code in a GPL'd project. In fact, Mojang even went so far as to supply deobfuscation mappings to the original Bukkit team, so it's very clear that they supported the Bukkit project. My opinion: "of course they would, it's helped their sales enormously"
* Early 2012, Mojang announced that the original Bukkit team (Dinnerbone, EvilSeph, Tahg and Grum) were being hired to work on Mojang's own planned modding API. Note that this API had been announced some time before, and has yet to materialise.
* Apparently at the same time, Mojang also acquired rights to the entire Bukkit project. This, however, was not publicised.
* The Bukkit project continued under new direct leadership (mainly feildmaster, Wolvereness and Amaranth) after the original team were hired by Mojang. feildmaster recently stated that Mojang stopped providing deobfuscation mappings shortly after the original team were hired. However, Mojang allowed the project to continue, and did not take any legal action over the CraftBukkit server.
* EvilSeph left Mojang shortly after, and is the only member of the original four to remain involved with the Bukkit project.
* Cut to last month: EvilSeph posted an announcement that the Bukkit project was being ended, due to the increasing difficulty of updating it for new Minecraft releases (remember: no more deobfuscation mappings from Mojang), and concerns of its legal status being exacerbated by Mojang's recent EULA changes.
* At this point, Mojang sprang into action, asserting ownership over the entire Bukkit project. Dinnerbone tweeted that he'd personally update Bukkit for the new Minecraft 1.8 release. Mojang's Jeb confirmed that Mojang owns Bukkit (I quote his tweet: "we checked the receipts"), having acquired it when the original four joined Mojang in 2012.
* The revelation over Mojang's ownership of Bukkit caused very significant consternation for many contributors to the project (there are around 170 individuals, including myself, who have contributed code licensed under the GPL).
* Wesley Wolfe aka Wolvereness, one of the new Bukkit dev team leaders, filed a DMCA takedown notice on Sep 5th, on the grounds that Mojang cannot legally distribute CraftBukkit when it contains both GPL'd code from him, and proprietary code from Mojang.
* In the last couple of days, pretty much all of the existing Bukkit staff (forum administration, plugin review & approval...) have resigned, effectively gutting the project.
* Also in the last couple of days, a new modding initiative called Sponge has been started by many individuals from the Bukkit project as well Forge, Spout, Flow - other leading Minecraft modding efforts. It's intended to be a higher-level abstraction layer on top of Forge, and won't be Bukkit compatible or contain any code from Bukkit. Given the calibre of many involved and the solid foundation of Forge, it has a very strong chance of success IMHO.
So those are the facts, basically. My opinions:
* The Bukkit team should not originally have chosen a LGPL license for CraftBukkit. And given that the Bukkit API is licensed under the GPL, and distributed in the CraftBukkit JAR file, this was also a poor licensing choice.
* Mojang had the opportunity to complain about this licensing decision at the start. Not only did they choose not to, but they provided tacit support to the Bukkit team, and later hired them as developers for their own API.
* Mojang's failure to make it clear that they owned the project subsequent to hiring the original dev team was unfortunate, and left many contributors feeling deceived when their ownership came to light. There is a feeling that people were being tricked into writing code for Mojang for free, when they believed they were contributing to a community-driven project.
* Wolvereness's decision to file a takedown is justified, although it's stirred up a huge amount of resentment from people who believe they're automatically entitled to software that he and others have spent a lot of time writing for little or no recompense. In addition, it may have the useful effect of forcing a solid resolution to the affair.
tl;dr Bukkit is most likely dead.
Very clever. I approve.
The clothes have no emperor. -- C.A.R. Hoare, commenting on ADA.