David Nalley wrote on Wed, 03 Jul 2019 16:21 -0400: > On Wed, Jul 3, 2019 at 2:38 PM Roman Shaposhnik <ro...@shaposhnik.org> wrote: > > > > On Tue, Jul 2, 2019 at 10:27 PM Greg Stein <gst...@gmail.com> wrote: > > > > > > On Wed, Jul 3, 2019 at 12:10 AM Justin Mclean <jus...@classsoftware.com> > > > wrote: > > > >... > > > > > > > Hi, > > > > > > > > > Although not a "real" PMC, we do need to provide legal protection for > > > > each PPMC and distributing releases is the time that most legal > > > > considerations "kick in" as it were. So we need a > > > > > > > > > Or we *don't* provide legal protections. That *is* what the disclaimer is > > > there for. > > > > That's exactly the direction I personally would like this to go into. > > > > As VP Legal, I think that's well within your bailiwick to make such a > decision. > As a member, I find that it's counter to one of the stated purposes of > the Foundation - which is to shield individuals[1] and find it > concerning that we are wanting to shift that back to the individual.
2017 - Project Foo is a non-Apache project 2018 - Project Foo has joined the Incubator 2019 - Project Foo graduated to PMC Releases in 2017 are not Apache releases. Releases in 2019 are Apache releases. Starting from some point in 2018 the Foo podling releases should enter the legal shield — but that point needn't coincide with the start of Incubation. Thus, instead of expecting that *every* release made while in Incubation be an Apache release, expect that *eventually* every release will be an Apache release. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
