The past few weeks we've been going over each and every piece of feedback you, our community, have provided us on various aspects of the Bukkit project and how we do things. In response to your concerns, we are making a number of changes to address the weaknesses some of you have highlighted for us: Improving community coverage and approval times We're looking to bolster our numbers both on the forums and on BukkitDev in order to be able to provide you guys with the quality of service you've come to expect from Bukkit. Our goal is to clean up the community and make the approval delay on BukkitDev a thing of the past and we're prepared to do whatever it takes to make this happen. Plugin Developers badge system Due to the move to BukkitDev, managing the Plugin Developers badge system has become cumbersome, difficult and largely impractical. As a result, the Plugin Developers badge system is being frozen until we can decide what would be the best direction to take it. Better BukkitDev icons The category icons we currently use on BukkitDev are very vague and generic. We need icons that are distinct, tell you what the category is at a glance, are properly themed and are relatively high quality. It's taking us much longer than intended to get some of the people we know to get some icons done so we're hoping our community can help us out. New Development System I'm just going to come out and say it. Pull request handling, development and innovation is slower than we'd all like. We get it and we're probably more unhappy with it than anyone else, so let's change that. Over the past few weeks we've been discussing the possibility of a new development model we'd like to introduce with a preliminary name of 'bleeding'. I'm still working out the details of the system, however here's what we have so far: We'll have two separate bleeding edge repos for Bukkit and CraftBukkit, these will be the sandboxes the active contributors from the community can play around in. The usual requirements (possibly more, to be determined) will apply in order to eventually get your polished work into the main repos. This means some things will be denied, but we'll always provide a detailed reason why this is. The main branches are to be synched with stable HEAD; all work is to be done in branches. A private IRC channel for bleeding committers will be created. A private forum for bleeding committers with one thread per branch will be created. The idea is that pull requests will be largely handled through bleeding where there will be many eyes looking at each one. We will be actively and closely working with people on their ideas in order to help nudge them in the right direction for inclusion into the main repos. One of the biggest reasons for pull request handling delays is the amount of work it takes to deal with each one. As it is right now, we need to review each PR to see if it is what we want, check the styling, figure out if it is the best way, pull it into a test build and throw it on a test server to verify it works and doesn't break anything else, and so on. This is all a lot of work we need to go through for each PR and results in a significant delay in dealing with them. We feel that this new system will help expedite the development process and better involve the community in the project. Through the collaboration we hope will happen as a result of this system, we'll be able to better build a public facing roadmap to improve communication with the rest of the community. Moving forward, we’re looking into sharing a public design document on Bleeding soon where the community can provide input on the new development system before it goes live. At the end of the day, we can't even begin to fix an issue we are not aware of. It is thanks to the people who are able to provide honest, mature and constructive feedback that really make a difference in the community. Thank you for your continued support and feedback, it is all greatly appreciated!