A little over a week ago we announced some of the improvements across the Bukkit project on which we have been working. One of the issues we touched upon was the unacceptable delay the community has been experiencing when it came to getting their pull requests into the project - or, in some cases, even getting a response. Unfortunately, we reached a point where we were not equipped to handle the bulk of the pull requests we were receiving and the entire queue stalled as a result. The Bukkit project is no stranger to community contributions and the clear benefits of fully utilising them: many of the features Bukkit has to offer are thanks to contributions from the community, so addressing this bottleneck is extremely important for us. The Pull Request Handling Improvements Initiative The Pull Request Handling Improvements initiative consists of several big and important changes to the way we handle code contributions from the community. One key aspect of this initiative is that we now have a Pull Request Handling team dedicated to working with you to get your pull request into the project. This new team consists of individuals hand picked from the Bukkit community to be the bridge between the community and the core Bukkit team. The Pull Request Handling Team members are: EdGruberman evilmidget38 These people listed above have joined the project in order to work closely with each pull request author to help you make sure your pull request meets our strict requirements. Our New Contributing Guidelines: The other key aspect of our push to improve our pull request handling process is our commitment to providing better documentation on getting involved with the project. Along with the new Get Involved tab (that we'll continue to expand upon) that can be found on this site, we have broken down every single requirement we have for code contributions in a new CONTRIBUTING.md. This CONTRIBUTING.md file is automatically linked by GitHub whenever a pull request is being created so every one knows exactly where to go to educate themselves on our contribution guidelines and requirements. In our new Contributing Guidelines, we not only go through every requirement we have, we've also included useful examples, a fancy flow chart and a Pull Request Format Template. Furthermore, if you would like to get a feel for the code formatting issues we keep an eye out for, we have this useful example here. Useful Links Contributing Guidelines and Requirements Pull Request Format Template An example pull request demonstrating the things we look out for Important Note: We no longer want pull request authors to handling squashing and end result commits. We will be handling this internally ourselves as we work with you on your pull request. Thanks for your continued support and patience as we work on these awesome improvements to our project. This new initiative is just the beginning of the many extensive changes we'll be making across the project in order to address our deficiencies and in answer to the mistakes that we've made over the years. As we continue to learn from our mistakes and experiments, we think you'll be happy with the direction we'll be taking the project.