Working in large open source projects, with several people contributing to the code, can be challenging, especially trying to keep everyone on the same page, and generating code that has enough similarities to allow shared maintenance. The advent of platforms like GitHub also made it easier for one time contributors to donate small and large bits of code to the platform, generating in the process a fair amout of “review stress” in the project maintainers. The presentation covers how pull request checks, formatting and static analysis tools have been used to streamline basic checks in the code: - Testing the code on a variety of operating systems, Java versions and integrations with data sources before the code can be contributed to the project - Enforcing common formatting - Adding basic checks with CheckStyle - Locating obvious errors, leftover code, basic optimization issues using the Java compiler linting, ErrorProne, PMD and SpotBugs - Improving readability of the code as well as enforcing best practices and common approaches with the same tools. - Effects on the dynamics of code reviews The presentation will cover all those aspects, with examples from the author’s experience with the GeoTools, GeoWebCache and GeoServer projects.