Goal: First iteration of the tool provided a limited set of probes. To improve the effectiveness of the scoring system, more probes are needed.
The project proposes to add new probes to the Plugin Health Score tool. Originally started in 2022 as a part of a GSoC project, this tool determines the health score of a plugin. Probes are the heart of the tool. To extend the work started last year, I propose adding new probes to make the tool more valuable and feature-complete.
In general, probes serve two purposes within the context of this toolset:
To collect the data to compute the score of the plugin systematically. Based on the computed score, the health of the plugin can be determined.
Based on the score future contributors, maintainers, and adopters decide which plugin(s) they want to invest their time in.
To enhance the effectiveness and usefulness of the Plugin Health Scoring System for the community, I propose to expand the number of probes used to gather data on plugin performance.
While the current probes provide valuable insights, they may not capture all the necessary criteria to fully evaluate the health of a plugin. Adding more probes can provide a more comprehensive and accurate assessment of plugin health, benefiting a wider range of users.
The project will be implemented in three parts:
Interaction of probes with each other
Probe’s execution order
Finally, the health percentage of the probe will be determined.
Health percentage categories
Low health: < Q1 (25th percentile)
Medium health: > Q1 (25th percentile) and < (75th percentile)
High health: > Q3 (75th percentile)
(General) Official weekly Jenkins office hours: Thursdays 15:00 UTC
(Project-based) Weekly project based office hours: Tuesdays 14:30 UTC