[dkhenry]

Not much in here as of right now , so if you looking as to what can be done immediately there isn't much of anything. It is cool that this is being worked on in public. Honestly I don't know why this is a fresh project instead of just an official fork of Bukkit.

[josso]

Besides the mentioned licensing-issues, Dinnerbone (the guy hired by Mojang, who used to work on Bukkit) – as well as others involved – has said that they like the opportunity to start fresh. Things, which was done one way in Bukkit, isn't necessary the best way and given the opportunity to do it better, it's not a hard choice.

[dkhenry]

I completely understand the start fresh mentality. I just know there is a lot of man hours that went into the Bukkit API to get it to the level of features it at now. I would hate to see it take just as long to get the official API up to feature parity.

[aprendo]

I think legal problems … I guess. Not sure. But it also seems like they want to do quite a few things differently, though I'm not sure whether that's good idea.

[Pyrodogg]

It's licensing issues, Bukkit is GPL. Mojang doesn't want to have to open up everything.

https://github.com/Bukkit/Bukkit/blob/master/LICENCE.txt