6 ms·
Mojang and the Bukkit Project
- binarymax 12y agoHard to tell what's going on here - but it looks like the developer of a mod (Bukkit) has a large enough userbase, that he's using that as leverage and trying to blackmail Mojang to open source the official Minecraft Server. --EDIT-- fixed spelling.
- teraflop 12y agoLooking at the actual DMCA request [1], it's definitely weird. The argument seems to be that: * Wolvereness's contributions to CraftBukkit are licensed under the GPL, and therefore may only be redistributed on that license * CraftBukkit itself is released under the GPL * ...but Wolvereness claims that CraftBukkit includes Mojang's Minecraft server, which is proprietary (apparently this is disputed by Mojang themselves, though) * Therefore CraftBukkit's GPL license is illegitimate, and the CraftBukkit developers' right to use Wolvereness's contributions is terminated. Even if the factual claims in the DMCA takedown are correct (which is hard to verify now that the repository is offline), it strikes me as an abuse of the process. When you file a lawsuit, you have to demonstrate that you have standing because of some adverse effect that specifically affects you. By that logic, Wolvereness shouldn't be able to use a third party's copyright to enforce a takedown. [1]: https://github.com/github/dmca/blob/master/2014-09-05-CraftBukkit.md https://github.com/github/dmca/blob/master/2014-09-05-CraftB...
- DannyBee 12y agoThis seems to be accurate, except for #4. It does not make their license "illegitimate". It's true that he can terminate his right to use the contributions (particularly if no CLA was signed granting rights), contrary to their assertion that he can't because he knew what the licensing was. He can also sue for copyright infringement in previous versions. But that's it. At least in the US, the only one who could sue for copyright infringement is a copyright holder. That means, in this case, the folks who own copyright to CraftBukkit. Right now that includes him. They could remove his contributions, but that would not put them in compliance for the versions already distributed, and they could be sued for those. (For the curious, Breach of contract wise, third party beneficiary arguments around the GPL have repeatedly failed, AFAIK, so others trying to get source as beneficiaries have not succeeded).
- teraflop 12y agoYeah, to be clear, I'm not arguing the validity of these positions, and #4 is the part I'm most suspicious of.
- Danieru 12y agoJust to be clear, if they did remove his contributions they must also make so none of the left over code is a derivative work. That would be a task beyond even a security audit. Mojang is not in a very business friendly situation right now. The only 100% not-lawsuit-libel approach is to either open source minecraft or rewrite the entire thing. They are still open to lawsuits related to the existing distributions but the traditional settlement is a combination of stopping to infringe and medium cash payment.
- DannyBee 12y agoYes. This is why, when folks say "CLA's are not necessary, you'd just remove the code" (like bradley kuhn recently did), i think they are very very wrong :)
- tedks 12y agoThe GPL states that any derivative work created by combining the GPL'd work and another work must be licensed under a GPL-compatible license. Violating any clause of the GPL revokes your copy of the license. So if I'm a company that distributes GPL'd binaries without providing corresponding source (a legal term in the GPL that means the preferred version of the source that a developer would edit, so decompiled code does NOT satisfy the license), I lose that license and am violating the copyright of the original author. In this case, Wolvereness' code has been incorporated into a derivative work, with other code (the Mojang decompilation) that isn't licensed compatibly with the GPL. Note that the form of the copyrighted work (the Mojang Minecraft server) is irrelevant. Mojang's copyrighted work is there, whether it's decompiled or in binary form or in any other form. The work is the same, much in the same way a vinyl record, a digital file, and a live performance all can contain the same copyrighted work. I don't think this is weird at all; this is a very straightforward case of GPL incompatibility. If Wolvereness wanted to include an exception for linking to the Mojang server, he could have done so using the infrastructure in the GPLv3, or with a special exception in the GPLv2. Mojang has definitely violated the GPL, and as such they have no claim to Wolvereness's license. Wolvereness is the party with standing here.
- tzs 12y agoDidn't he implicitly include a GPL exception when he contributed his GPL code to a project that was not GPL? If I'm understanding this correctly, CraftBukkit purports to be GPL, but includes disassembled, deobfuscated code that they did not own and was not available under a GPL compatible license.
- tedks 12y agoNo. There's no such thing as an "implicit" GPL exception. You're right that the original CraftBukkit project equally violated the GPL, but now that Mojang is distributing it, they're the ones liable for the violation.
- tzs 12y ago> No. There's no such thing as an "implicit" GPL exception. You don't think a court would use some equitable doctrine such as estoppel to find that if I explicitly contribute my code to a project with the intent that they include it and distribute it, I am giving them whatever licenses is necessary to allow that?
- ObviousScience 12y agoThis is a good summary. A few relevant facts about the political landscape involved: Bukkit is used by a large number of Minecraft fans to run servers, due to the availability of plugins and other improvements in the modded server. The developer in question contributed significantly to Bukkit, and has stated that without the full Bukkit product being open sourced (including the base Minecraft binary it's based around), it's a copyright violation to be using his contribution. This is legal, because of the nature of his code licensing, however, it is not a demand that the Bukkit team can comply with, as they don't hold the original Minecraft code. As such, their only option is to comply with the take down (and not use that code) until such time as Mojang releases the source to the Minecraft code that Bukkit uses. Mojang is under no obligation to do so, because they're not using any of the dev in question's code, as he only contributed to Bukkit. However, Mojang risk upsetting a large portion of their tech savvy and more active user base (including YouTubers and streams), because relying on Bukkit servers is common in those circles.
- shawn-furyan 12y agoOne piece I think you're missing in this description is that Mojang aqui-hired[1] part of the Bukkit team but left Wolverness (the DMCA takedown originator) out. Wolverness had contributed 10s of thousands of lines of code to the project. So Wolverness isn't just using the popularity of Bukkit as leverage. Rather, Mojang is redistributing his code without having sought his permission. Of course, Bukkit itself was a derivative work of the Minecraft Server (the decompiled java bytecode) in violation of that piece of software's license, so the whole matter seems to be a tangle of license violations. In any case, Mojang is (or WAS, rather) distributing Wolverness's copyrighted code without his permission, and so are apparently in violation of his copy rights. I think that's where the leverage comes in. Wolverness seems to be hoping that it will be easier for Mojang to relicense and release Minecraft code to make it compatible with his bukkit code than to work around his code. [1] Reportedly. I've seen various, partially contradictory characterizations of how this happened, but there seems to have been at least some sort business deal between Mojang, and a subset of the Bukkit team not including Wolverness [edit: added footnote]
- XorNot 12y agoThe issue of license violation is that someone had to claim damages. Mojang could have, but didn't - and you could argue in a court benefited greatly from this state of affairs (selling Minecraft licenses). The fact that Mojang now wants to distribute GPL code without providing full source would, I suspect, stand badly against that since a claim of license violation has been made now. Generally, you can't ignore copyright by yelling "two wrongs make a right".
- shawn-furyan 12y agoWell, yeah, I agree. I'm not saying that Mojang hasn't likely been willfully ignoring the license violation, just that Bukkit seems to infringe on the letter of the official Minecraft Server license. And yeah, I don't think that that has any bearing on the copyright claim. Incidentally, the link has been changed since I began commenting. I find this assertion from the now-linked post to be odd: "Additionally, we believe that Wesley has no right to prevent the continued use of his contributions to the project – which he gave freely, knowing them to be subject to applicable open source licenses. We believe these licenses continue to bind all those who contributed to the Bukkit Project." This doesn't really address the primary charge from Wolverness, to paraphrase, that essentially the bukkit and related projects are distributing code incompatible with its license and therefore are not permitted to distribute the copyrighted code contained in the bukkit project without express permission. If the license for the code is not adhered to, then you don't have permission to distribute the copyrighted material... So one party is saying that the license was broken, and the other party responds by saying that there was a license. That's kind of a non sequitur.
- Shank 12y agoHere's the DMCA request that was sent to GitHub: https://github.com/github/dmca/blob/master/2014-09-05-CraftBukkit.md https://github.com/github/dmca/blob/master/2014-09-05-CraftB...
- templeos2 12y agoI wrote every line from scratch. On penalty of your eternal soul burning in hell, don't fuck with me. Jesus saith unto them, How many loaves have ye? And they said, Seven, and a few little fishes. 15:35 And he commanded the multitude to sit down on the ground. 15:36 And he took the seven loaves and the fishes, and gave thanks, and brake them, and gave to his disciples, and the disciples to the multitude. 15:37 And they did all eat, and were filled: and they took up of the broken meat that was left seven baskets full. 15:38 And they that did eat were four thousand men, beside women and children. 15:39 And he sent away the multitude, and took ship, and came into the coasts of Magdala. 16:1 The Pharisees also with the Sadducees came, and tempting desired him that he would shew them a sign from heaven.
- deleted 12y ago[deleted]
- Airhat 12y agoFirst, has HN really fallen so far as to link slashdot of all things? Second, a quick explanation of the issue, as I have it: Bukkit is a server made by the community to make up for the simplicity of the official server. It uses deobfuscated, reverse engineered java code from the official server, and has never been given the actual source from Mojang. While Bukkit was sort-of folded into Mojang (They own the name, and a few of the developers went to work for Mojang), no one at Mojang is paid to work on Bukkit and they still don't get source access. Now, a disgruntled Bukkit Dev, Wolverness, has thrown out this DCMA request in some sort of retaliation / blackmail attempt.
- djur 12y agoI haven't been able to find any evidence that Mojang owns a trademark on "Bukkit", or even that such a trademark exists. They apparently don't own the domain name or the hosting accounts. And they don't own the entirety of the source code. Mojang is definitely claiming they "acquired" some kind of rights to Bukkit, but I can't find any description of what those rights are -- and, for a community project, I don't understand what they could possibly own that isn't public knowledge. You can't own secret trademarks.
- kevinpet 12y agoI think the game is the following: 1. Bukkit is GPL, developed without help from Mojang, but with a questionable use of the decompiled source. 2. Mojang likes Bukkit, hires some of the devs and buys name. And I'll assume the these core devs would be willing to assign copyright to Mojang. 3. (Eventually) One of these core devs, now a Mojang employee, makes a new release of CraftBukkit, including Bukkit and linked against the Mojang official server blob. Although the timing is different, this is exactly the situation with GPL libraries like Readline. You can't use them in a proprietary product. On the other hand, I suspect if this went to court, Mojang could argue that since that's all bukkit ever did, and this dev contributed to it while that was the case, the license should be interpreted as including something like the classpath exemption, because it's absurd to assume that people wrote code and distributed it but did not legally intend for it to be used in exactly that way.
- DannyBee 12y ago"Although the timing is different, this is exactly the situation with GPL libraries like Readline. You can't use them in a proprietary product. " Actually, this is disputed by a number of good open source lawyers. In particular, it's not clear what the line for derivative works is, despite what the FSF/etc claim. "On the other hand, I suspect if this went to court, Mojang could argue that since that's all bukkit ever did, and this dev contributed to it while that was the case, the license should be interpreted as including something like the classpath exemption, because it's absurd to assume that people wrote code and distributed it but did not legally intend for it to be used in exactly that way." I'm not sure what you are trying to say here. Let me give you an official open source lawyer view: There is a roughly 0% chance this guy could force Mojang to open source anything. He can sue for CraftBukkit for copyright infringement over previous versions. He can stop them from distributing new versions with his code in it. That's it. This is because his rights are in his code, not Mojang's. At least in the US, he cannot sue for copyright infringement of someone else's source code, no matter what license it's released under. So once they removed his contributions, they would be fine, except for whatever damages already exist. If CraftBukkit included decompiled source without Mojang's authorization, the most likely outcome is that they would pay some small amount of money damages, and maybe be enjoined from distributing older versions.
- dang 12y agoUrl changed from http://games.slashdot.org/story/14/09/06/1323225/dmca-claim-over-gpl-non-compliance-shuts-off-minecraft-plug-ins?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Slashdot%2FslashdotGames%2Fto+%28%28Title%29Slashdot%3Agames+%28rdf%29%29 http://games.slashdot.org/story/14/09/06/1323225/dmca-claim-..., which points to this.
- cwyers 12y agoI feel like the original Slashdot link has a lot more context for someone who doesn't follow the Minecraft scene closely, even if the new link has more content.
- dang 12y agoThat's true. I'd say the balance tips slightly in favor of HN's preference for original stories [1], mainly because the thread here also fills in the context. But yeah, this one is a borderline call. If people feel strongly about it we can change the url back. 1. HN already consists of pointers to stories, and pointers to pointers don't work as well.
- bane 12y agoI submitted this instead of one of the original sources because it both contains links to multiple original sources which summarize the story as well as a writeup of the story. The changes link doesn't point to the DMCA request response which is here http://www.spigotmc.org/threads/our-dmca-response.28772/ http://www.spigotmc.org/threads/our-dmca-response.28772/ which I think is equally important to the story.
- nightpool 12y agoEDIT2: I might have been a little harsh here. I was missing some context that I've been avoiding over the past few weeks. On further reflection, I have nothing but anger for the way Mojang has handled this situation. Even though they claim that they "own Bukkit outright", completely devaluing the many, many, many community contributions made, they continue to refuse to support the project in even the most trivial ways, and I have nothing but respect for many of the community leaders they've driven away, including @mbaxter, @EvilSeph, @amaranth and many more. Mojang is absolutely to blame for this, no matter how childish Wolverness' behavior may be. I've left my original comment below, to give some context on the complexities of the situation, but I can maybe understand where Wolverness is coming from at this point. This is my perspective as someone who was once inside of the Bukkit community as an outside developer (not one of the core team), but Wolverness has been a very toxic maintainer of the project, especially as it regards to responding to pull requests. Either your code complies 100% with the contributing guidelines (including confusingly written and sometimes unwritten rules about spacing, formatting, naming and pull request formatting) or it gets rejected out of hand. Any mention of forks of the Bukkit project (such as Spigot, Glowstone or SportBukkit) could get you banned from IRC, the forums and your comments deleted on Github. This upon many, many instances of just caustic behaviors and treatment of interested developers and contributors. I'm still subscribed to the projects on Github, and I was never burned by these rules personally (so these feelings are not out of spite--they're out of sorrow for the developers who were turned away) but I don't think I'd ever have a chance of getting any non-trivial PR integrated into the project. The standards were just too insane. I'm no fan of how Mojang has been handling the minecraft community recently, but anything that would drive this guy out is just fine by me. (This takedown is BS btw. CraftBukkit has ALWAYS linked against the minecraft official server library--a release of CB made by a Mojang employee doesn't change ANYTHING about the GPL status of Minecraft. Note that the proprietary minecraft server DOESN'T link against in any way shape or form)
- djur 12y agoI'm baffled by the claim that Mojang "obtained rights [to]" Bukkit. I'm not involved in the community, but to me it looks like they hired some of the lead devs, and maybe had those devs transfer their copyrights to Mojang? But unless Bukkit/CraftBukkit had a copyright assignment policy, which it doesn't appear to have had, the developers Mojang hired could not transfer the entirety of Bukkit to Mojang's ownership, and thus the "obtained rights [to]" language by the COO seems either inaccurate or meaningless. Doesn't Mojang have lawyers? Their behavior seems baffling and their public statements even more so.
- fencepost 12y agoA couple additional notes: 1. Many (most?) of the servers running with Bukkit also had some form of payment for items, skills, ranks, etc. that can affect game play, also known as "pay-to-win." Mojang recently announced that they were going to be cracking down on this since it's a violation of the license, though I don't know what if any enforcement has actually happened. Enforcement was due to start August 1. 2. Mojang has a couple of multiplayer options without Bukkit - the Minecraft Server piece that is part of this discussion and Minecraft Realms. If Bukkit is dead (which may be the case no matter what happens because W. is not the only outside developer who could pull this kind of stunt), there are still multiplayer options and Mojang could likely implement some of the features currently in Bukkit but under their control - perhaps under a licensing model that lets them sell the server software as well. Basically this guy has managed to shut down something being used by folks with business practices that Mojang was already having some issues with, while leaving available some less feature-rich options fully approved (and controlled by) Mojang. The odds of that resulting in their giving in and open-sourcing something that's included in Minecraft as a whole are somewhere around nil - worst case for Mojang is that the Minecraft server community that they're not a direct part of takes a feature and popularity hit for some time while they get to point at this guy as the reason why.