3 ms·
One of the missing bits of context here is that because of the licensing and EULA issues, a few weeks ago all the then-active Bukkit developers decided to shut
by makomk 12y ago
One of the missing bits of context here is that because of the licensing and EULA issues, a few weeks ago all the then-active Bukkit developers decided to shut down development and end the project. Mojang then announced that they couldn't do that because it wasn't their project to close down since Mojang had secretly acquired it several years back. (All of the current Mojang employees who were formerly Bukkit devs had stopped participating in development and weren't following the discussions.)
- djur 12y agoDid they say what, exactly, they had "acquired"? Obviously they could continue distributing and developing the GPL/LGPL source, and depending on whether the name is trademarked they could keep calling it Bukkit. Does Mojang own the issue tracker, the website, etc.? In that case, sure, they can keep those going, although without any developers I don't see the point.
- makomk 12y agoThat is a very good question which I don't think they've ever really answered. The domain seems to be registered to Curse, who formerly owned Bukkit and presumably still provide hosting for it. They certainly don't own the copright on most of the code, and probably have no more right to use much of it than anyone else. Stuff like trademarks and the Github project? Who knows. Plus Mojang keep contradicting themselves about the relationship between Bukkit and them.
- shawn-furyan 12y agoThat's interesting. It seems strange to secretly acquire a public GPL project from a subset of its developers. It seems like perhaps all they bought was the option to carry over the name and a fraction of the code if a fork became necessary. Or perhaps to cripple the project in case of disputes.