6 Months of Static Analysis on Core and Contrib

Since DrupalCon Dublin 2016, a prototype of integration between Code Climate and Drupal has been running to track the code quality of Drupal 8.2 and 8.3, as well as several Contrib modules, which serves as a starting point to discuss the future of static analysis and reporting on drupal.org for Core and Contrib contributions.

In this session, we will first cover how this prototype was setup and what insights have come from it. We will look at which indicators have been most useful in finding problematic areas in code, how churn can and size of code are related, and how Drupal’s quality compares with other open source projects like Symfony and WordPress. We will also include case studies of how Code Climate has helped newcomers to the Drupal community improve quality of module code for acceptance onto drupal.org, as well as their own Drupal projects.

Last, we will look at a roadmap for how this prototype can become a realistic solution on drupal.org, including concepts for longer term functionality, such as improving the module review process, code review, Security Team audits, architectural reviews, and the ability to represent the quality of Drupal contributions and code with greater transparency.

If you are interested in discussing how automated static analysis can have a positive impact in the Drupal community, this session is for you. The key takeaway from this session is an understanding of how static analysis can start benefiting the Drupal community today.