> not authorizing his contributions to be used Actually, it's a lot more interesting than that. My understanding was that said contributor realized that since

> not authorizing his contributions to be used Actually, it's a lot more interesting than that. My understanding was that said contributor realized that since Bukkit is GPL, it can't be legally distributed combined with proprietary Mojang code. His takedown notices were based on GPL violation, not just revoking authorization (which he probably can't do with the GPL?)