I didn't get the sense that the BDFL would be a bottle neck when you explained it to us at the contributor summit. To me it seemed like the BDFL would only have to get involved if consensus between the author, editors and other reviewers can't be reached, or if he needs to put in a veto to stop something (in his mind) crazy from happening.
That said having Subject Matter Experts on hand to either serve as a "Deputy BDFL" for a specific area, or just someone that gets an explicit ping when a JEP affecting "their" area comes in might be good to have. /B 2017-09-19 19:12 GMT+02:00 R. Tyler Croy <ty...@monkeypox.org>: > (replies inline) > > On Wed, 13 Sep 2017, R. Tyler Croy wrote: > > > https://github.com/jenkinsci/jep/tree/jep-1/jep/1 > > > Since I'm sure not everybody has been following along with some of the pull > requests and changes while we've been hammering out JEP-1, I would like to > provide a little bit of an update and solicit some help. This topic is very > important, so please read this email! > > First, thanks to reviews from a number of folks including Oleg, Owen, > Daniel, > and others, we have been able to tighten the proposal up quite a bit. > Mostly > thanks to Liam's diligent slicing and dicing of text :) > > While I had hoped we might be able to get some consensus in time for > tomorrow's > project meeting, I don't think we are quite there yet. There has been lots > of > helpful feedback on the review and decision-making process > (BDFL/BDFL-delegate): > https://github.com/jenkinsci/jep/tree/jep-1/jep/1#review > > > To summarize the primary, and valid, criticisms if I may: > > 1. Kohsuke as the BDFL introduces a problematic bottleneck to the process > (there are way more of us, than there are of him). > > 2. JEP-1 introduces a different way of decision making than has been > traditionally followed with the Governance Meeting > (https://jenkins.io/project/governance/#meeting) > > > I would like to guide the discussion towards addressing these. I also want > to > ensure our process is sensitive to contributors around the world, > especially > those in Australia and Asia who are typically asleep during the scheduled > project meetings and rely on asynchronous mediums like email. > > If you have an example structure for technical decision-making from another > project, which you think is applicable, please chime in! > > > Personally, what I'm thinking right now is to flip the Python model upside > down: when the JEP Author creates a draft they (or a JEP Editor) list a > "Delegate" who would be somebody with good standing as the maintainer of > that > subject area, other than themselves. > > For example, if I were proposing a design on Remoting, Oleg would be the > obvious Delegate. If Andrew were proposing some design around Pipeline, > Jesse > would be a reasonable Delegate. Rather than expecting a BDFL to be "plugged > into" each JEP, we self-select more (which I think we're all capable of > doing). > For the times when we might have conflcit, then we can use the Governance > Meeting process to resolve who the appropriate Delegate for a proposal may > be. > To help new comers, including a list of "Suggested Delegates" in the JEP > repo > could also be helpful. > > I think that could avoid the problems with the current BDFL proposal, while > reducing the need to run every JEP through the Governance Meeting process, > where not all the stakeholders will necessarily be present. > > > > Of course, I'm open to more suggestions and discussion. Like I said at the > beginning of the email, I think getting this right is important. > > > Cheers > - R. Tyler Croy > > ------------------------------------------------------ > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > xmpp: rty...@jabber.org > > % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F > ------------------------------------------------------ > > -- > 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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/20170919171212.j3sjo4fawhisfieb%40blackberry. > coupleofllamas.com. > For more options, visit https://groups.google.com/d/optout. > -- Robert Sandell *Software Engineer* *CloudBees Inc.* -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0gCQcc3qAJJ%2Bimw2j4E-%3DqZVnwcrpP2AefFW000_Y0Kw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
