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 > <[email protected]>: > > 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 with that. > > Here is the link to the survey: https://forms.gle/T6LLqQGYgKke2b8e9 > <https://forms.gle/T6LLqQGYgKke2b8e9> > > For the moment, we have 11 responses. Thank you for those who responded. > Please be sure that it's really quick and your time is really important to us. > > Regards, > -- Adrien > > Le jeu. 30 juin 2022 à 14:38, Adrien Lecharpentier > <[email protected] <mailto:[email protected]>> a > écrit : > 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 others, some > don't have a valid SCM link as well. We still haven't implemented anything > that could tell us which is the parent pom version used by each plugin, but > it is in the plan. > > The plan here, is to get a sense of what make sense for the community, but > the weight of each rule will have to evolve with time. For example, if we say > "having a Jenkinsfile" is very important, but in 6months we have all plugins > with one, then we can lower the rule (new plugins don't come often) and just > have a warning if / when the Jenkinsfile disappear. > Same thing, for new probes, we don't intend to have all the probes in > September and be done with it. We want this project to serve the community > for the years to come. So, the probes and weight will have to evolve with the > community. > > I know I haven't answered your question specifically, but that's the best I > can offer you. > -- Adrien > > Le jeu. 30 juin 2022 à 08:58, '[email protected] > <mailto:[email protected]>' via Jenkins Developers > <[email protected] <mailto:[email protected]>> a > écrit : > 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] > <mailto:[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 > <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] > <mailto:[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 > > <https://groups.google.com/d/msgid/jenkinsci-dev/cc2dc61a-03a8-4695-8f6b-4436189f9690n%40googlegroups.com?utm_medium=email&utm_source=footer>. > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAKwJSvxj3BYB7WcKtFpiU%2Big0B9kWBa-nmPFy7yeTO%2BGF8UCew%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CAKwJSvxj3BYB7WcKtFpiU%2Big0B9kWBa-nmPFy7yeTO%2BGF8UCew%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- 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/44C2EC78-C108-4595-AB18-6C58D87630FC%40gmail.com.
