> we have allowed (and IMO should continue) podlings to have licensing issues during their incubator releases
Thanks for pointing this out, Greg. I wasn't aware of this and have always had releases fail when we discover licensing issues. I think there's a significant risk of license problems, so I had assumed we would require a thorough scrub before the first release. What's the argument for finishing this work before graduation rather than first release? Isn't the release a product for which the ASF is legally responsible? Given that we fail releases for known license issues, shouldn't we also be more careful when we know there are likely to be issues? rb On Mon, Jun 18, 2018 at 12:24 PM, Greg Stein <gst...@gmail.com> wrote: > On Mon, Jun 18, 2018 at 2:08 PM Ryan Blue <rb...@netflix.com.invalid> > wrote: > >... > >> 2. The license problems so far show that the project has not paid adequate >> attention to licensing up to now, which is a big risk. I'd like to see >> what >> kind of licensing scrub is proposed before the potential podling's first >> release. I don't think that catching all the obvious ones is sufficient. > > > To be clear: we have allowed (and IMO should continue) podlings to have > licensing issues during their incubator releases. For example, while > they're still dealing with Hibernate dependencies. It is understandable and > (IMO) acceptable that such releases will have problems. That is just part > of the process. As long as it gets cleaned up before graduation. > > Not diminishing the need for a good scrub, but I would not want to see > releases gated on that. (it's unclear from your text; maybe just a *plan* > rather than completion of the scrub?) > > Cheers, > -g > > -- Ryan Blue Software Engineer Netflix
