Hello Jenkins Contributors! We are the group working on the Google Summer of Code project that is the Plugin Health Score. Briefly, the Plugin Health Score is a composite score of various different probes related to Jenkins Plugins. These different probes will have different weights(value) and focus on different areas(think administrative metrics, code quality, best practices and security) and we will generate a final score for each plugin within the Jenkins ecosystem.

We would love to get the broader communities opinion on what are the more important aspects of a great plugin!

Administrative Metrics/Maintainer(s) Activity - This umbrella of probes focuses on the maintainer(s), more or less.
     - Last Release Date
     - Number of Commits since last release
     - Number of Open PRs (Current)
     - Number of Open PRs (Rolling Avg)
     - Average time to review PRs
     - Average time to merge approved PRs
     - Average time to release after merged PRs
     - Open Bug Tickets
     - Plugin is up for adoption

Code Quality/Best Practices - This umbrella of probes focuses on best practices and quality of the code.
     - Code Coverage
     - Continuous Integration Configured
     - Continuous Delivery (JEP-229)
     - Dependabot Configured (or similar tools - updatecli, renovatebot, kodak)
     - Spotbugs Configured
     - Code linter Configured
     - Documentation in GitHub
     - Release Drafter Configured
     - Security and known vulnerabilities