Hello Dheeraj,

Are you able to share the data distribution for the individual probes you 
already have in place? This will greatly help us understanding what should 
be done with the rules.

E.g. if all plugins have a code coverage of 50%+, the weight should take 
that into consideration, in opposition to the situation where only the top 
5% of the plugin have more than 5% of coverage.
>From my PoV the project has two goals, showing the current situation and 
also providing guidance about what to improve on a plugin, to follow the 
good practices.

Thanks in advance,

Wadeck

On Wednesday, June 29, 2022 at 8:15:08 PM UTC+2 [email protected] wrote:

> Hello Jenkins Contributors!
>
> My name is Dheeraj Singh Jodha and I'm selected as a Google Summer Of Code 
> 2022 student for the Jenkins project where I'm part of a group of 4 people 
> currently working on the project that is titled Plugin Health Scoring 
> System 
> <https://www.jenkins.io/projects/gsoc/2022/projects/plugin-health-scoring-system/>
> .
>
> 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.
>
> As communicated earlier in one of the previous emails, we're now very 
> happy to share with you the Community-wide Survey link!
>
> Please find the link here: https://forms.gle/T6LLqQGYgKke2b8e9
>
> Your 5 mins spent on this survey would help us deliver the best results 
> for our project. Thank you in advance!
>
> Regards,
> Dheeraj
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/cc2dc61a-03a8-4695-8f6b-4436189f9690n%40googlegroups.com.

Reply via email to