> > Perfect, this makes the barrier to acceptance quite low, without forcing a > change on anyone. > Yes, I do not think we are in position to enforce the process at the moment. Historically Jenkins project gives a lot of freedom to plugin maintainers to define how they operate, and IMHO it is a part of the project's culture. IMHO we should rather lead by example there and help by providing tools and solutions simplifying the work and removing routine.
On Thursday, January 9, 2020 at 3:04:51 PM UTC+1, Jesse Glick wrote: > > On Thu, Jan 9, 2020 at 8:05 AM Oleg Nenashev <[email protected] > <javascript:>> wrote: > > We add CODEOWNERS template to plugin archetypes > > Yes, though we need to do JENKINS-58557 first. > > > We submit pull requests […] > > Each plugin maintainer or maintainer team will decide on their own > whether they accept the process or not. Merging or closing the pull request > will indicate the decision > > Perfect, this makes the barrier to acceptance quite low, without > forcing a change on anyone. > -- 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/f3f0b2d4-bb98-458d-9c96-ccdee1d1fec1%40googlegroups.com.
