3 ms·

EDIT2: 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

EDIT2: 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 ago
I'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.
- deleted 12y ago
  [deleted]
- onedognight 12y ago
  > Mojang obtained rights in the project over 2 years ago To me this reads as "obtained [some] rights in" which seems correct.
  - djur 12y ago
    I see that, but that reading makes it a meaningless statement. Mojang owning the rights to some subset of the Bukkit source doesn't give them any more power to continue the project than anyone else. They're clearly suggesting they have some kind of proprietary interest in Bukkit that allows them to decide whether the project continues or not. The context of that quote is: > As Jeb announced on twitter, Mojang obtained rights in the project over 2 years ago The tweet from Jeb says that Mojang "bought" Bukkit, and a subsequent tweet says that they "dug up the receipt to be sure". The previously hired Bukkit devs have also said Mojang "acquired" and "owns" Bukkit.
erikb 12y ago
That's really interesting. It would be great to read more about the different open source contributions and the people involved. Haven't played it for a long time. E.g., how did a person that is perceived as poisonous become a maintainer of a seemingly important tool of the community? He must've done some things right, or not?
mcphage 12y ago
> Mojang is absolutely to blame for this, no matter how childish Wolverness' behavior may be. Mojang is to blame for not letting @EvilSeph shut down the project? Despite his reason for shutting it down was that he was worried Mojang was going to issue a takedown against them—something Mojang showed no interest in doing, and then was done by one of their own developers? I'm curious how you think they should have handled this. EvilSeph wanted to take down Bukkit, something that would have freaked out a whole lot of server admins (and did freak out a whole lot of server admins, now that Wolverness managed to actually do it). Clearly they didn't want it taken down. They owned it (although what that means is unknown). What else should they have done?

djur 12y ago

I'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.

deleted 12y ago
[deleted]
onedognight 12y ago
> Mojang obtained rights in the project over 2 years ago To me this reads as "obtained [some] rights in" which seems correct.
- djur 12y ago
  I see that, but that reading makes it a meaningless statement. Mojang owning the rights to some subset of the Bukkit source doesn't give them any more power to continue the project than anyone else. They're clearly suggesting they have some kind of proprietary interest in Bukkit that allows them to decide whether the project continues or not. The context of that quote is: > As Jeb announced on twitter, Mojang obtained rights in the project over 2 years ago The tweet from Jeb says that Mojang "bought" Bukkit, and a subsequent tweet says that they "dug up the receipt to be sure". The previously hired Bukkit devs have also said Mojang "acquired" and "owns" Bukkit.

erikb 12y ago

That's really interesting. It would be great to read more about the different open source contributions and the people involved. Haven't played it for a long time. E.g., how did a person that is perceived as poisonous become a maintainer of a seemingly important tool of the community? He must've done some things right, or not?

mcphage 12y ago

> Mojang is absolutely to blame for this, no matter how childish Wolverness' behavior may be. Mojang is to blame for not letting @EvilSeph shut down the project? Despite his reason for shutting it down was that he was worried Mojang was going to issue a takedown against them—something Mojang showed no interest in doing, and then was done by one of their own developers? I'm curious how you think they should have handled this. EvilSeph wanted to take down Bukkit, something that would have freaked out a whole lot of server admins (and did freak out a whole lot of server admins, now that Wolverness managed to actually do it). Clearly they didn't want it taken down. They owned it (although what that means is unknown). What else should they have done?