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
