Hello Ullrich,
this is a good point, we thought about it but for the moment, we wanted to
focus the project on the maintainers.
The idea was to give direction to maintainers to help them have the best
grade possible. Something like: "The plugin has a grade of 80%. Could gain
5% with dependabot."
Maybe it would help to post in https://community.jenkins.io as well?
It would be also helpful to ask the users what they think, so the users mailing
list may increase the number of return answers?
> Am 12.07.2022 um 17:24 schrieb Adrien Lecharpentier
> :
>
> Hello everyone,
>
> just a
Hello everyone,
just a reminder that the feedback that you can give us is really important
for us. The idea is, when we will be in the "grading" phase of the project,
to be fair to the community.
By that I mean we don't want to say "Rule A is 90% of the grade" when in
fact the community disagree
Hello Wadeck,
let me answer here for Dheeraj (as mentor of the GSoC project).
At the moment, we don't have any probes in actions and we don't have a lot
of data. I know that we have for example, 52 plugins out of the 1872
currently in the update-center that don't have any SCM link. Out of the
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
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
