Roman Shaposhnik wrote on 6/7/17 4:20 PM: > On Wed, Jun 7, 2017 at 10:56 AM, Mark Thomas <ma...@apache.org> wrote: >> On 07/06/17 17:53, Roman Shaposhnik wrote: >>> On Wed, Jun 7, 2017 at 8:32 AM, Sean Busbey <bus...@apache.org> wrote: >>>> On 2017-06-06 11:59 (-0500), Roman Shaposhnik <ro...@shaposhnik.org> wrote: >>>>> On Mon, Jun 5, 2017 at 8:25 PM, John D. Ament <johndam...@apache.org> >>>>> wrote: >>>>>> While these are all great discussion points, I don't believe they're >>>>>> relevant to incubator only and probably should have remained on the >>>>>> legal-discuss list. Ignite graduated ~2 years ago. The incubator >>>>>> probably >>>>>> doesn't have an opinion about this, but it's good to know that the policy >>>>>> may change (and I do personally have an opinion on said types of >>>>>> software). >>>>> >>>>> The reason I'm bringing it on the IPMC mailing list has nothing to do >>>>> with how long >>>>> ago Ignite graduated and everything to do with the following two points: >>>>> 1. It can be very useful to the future podlings >>>>> 2. I honestly don't know any other forum where I can meaningfully >>>>> discuss changes to release policy >>>>> >>>>> I'll take advice on #2, of course. >>>> >>>> >>>> Who owns release policy? I presume it's VP Legal, which would suggest >>>> legal-discuss. >>> >>> I would really be surprised if VP Legal actually *owned* it. This >>> feels someplace between >>> INFRA, ComDev and Legal, but it still doesn't answer the question >>> who's a single throat >>> to choke. >> >> Consider yourself surprised then. V.P. Legal owns the release policy. > > Is legal-discuss then the appropriate forum to actually build the consensus? > I surely hope V.P. Legal won't play a BDFL with our release policy, will he?
Huh? Only the board and specifically authorized officers can set policy like the release policy that all PMCs MUST follow. So yes, VP Legal is the final determiner of release policy updates, not anyone else. legal-discuss@ is the best place to bring any specific requests from project(s) to change the actual policy itself. But first it would be useful to get some rough consensus on some of those specific requests here from the IPMC or from ComDev. Having specific changes backed up by actual *needs* from one or more PMCs is the best way to start. Note that ComDev is a PMC itself, and has no authority to set *policy* for other PMCs. But they do provide a lot of good docs and best practices, and dev@community is becoming quite a good cross-project discussion area, so it's a good place to get other feedback on a proposal. > Thanks, > Roman. -- - Shane https://www.apache.org/foundation/marks/resources --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
