On Mon, Jan 27, 2020 at 2:55 PM Jesse Glick <[email protected]> wrote:
> > Echoing KK (I think!), JEP should be a tool which assists people who > are already comfortable working on Jenkins. Keep the “editor” role, > responsible for matters of form and administration; and merge > “sponsor”, “contributors”, “BDFL”, “BDFL delegate”, and “reviewer” > into a simple “author” who is responsible for submitting the JEP, > doing the implementation, and delivering it, or delegating pieces of > this as they see fit. The board would just be a last resort in case > someone is trying to push through an unpopular change, with or without > a JEP. > I remember it as a tool to help especially less experienced contributors (from a governance/community involvement POV) get larger scale changes in without them lingering in review forever or being rejected at the last step, wasting a lot of time. I don't know how well it worked for that use case but we should work towards enabling such work rather than just make it a place where "the regular suspects" document their major changes. -- 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/CAMo7Pt%2BOh29_385K2KJponNQvAG2z7uEKa7JLw0Vkj9pAN0arA%40mail.gmail.com.
