Apologies for potentially coming out of left field on this… But I think that IP clearance is currently a difficult road to travel, and I worry that we are graduating podlings that don’t even know when or how to go down that road. It’s all too easy to merge a github pull request without considering IP clearance.
I’ll admit that I’m unclear on the policy, and try to err on the cautious side. I’ve seen commits to TLP projects that made me think “WTF… how did this evade IP clearance?”. I may be overreacting, but it seems to me IP clearance is REALLY important, and I worry that it may be taken for granted. -Taylor > On Oct 21, 2015, at 10:11 PM, Greg Stein <gst...@gmail.com> wrote: > > On Wed, Oct 21, 2015 at 8:45 PM, John D. Ament <johndam...@apache.org > <mailto:johndam...@apache.org>> > wrote: > >> On Wed, Oct 21, 2015 at 9:40 PM Greg Stein <gst...@gmail.com> wrote: >> >>> I believe a PMC is capable of performing IP clearance itself. They have a >>> VP that is an Officer and can take responsibility for the Foundation in >>> matters of that Project. The forms/recording are valid, so I haven't >>> suggested changing that (tho I'd like to see them move under /legal/, I'm >>> not fussed about their location). >>> >>> I would hope that a PMC includes a note in their report to the Board, >> that >>> they filed a clearance form. That is just natural reporting. But that is >>> quite different from one TLP being subject to another TLP's vote (whether >>> lazy consensus or not). >>> >>> There could certainly be an argument that a PMC needs to be >> double-checked >>> by $entity. But that kind of second-guessing means $entity needs to >>> double-check all commits and all release artifacts. We trust PMCs to get >>> their IP done correctly, as they work on their project and make releases. >>> >> >> What you're saying makes a lot of sense. I've always questioned the >> benefit of TLPs submitting IP Clearances to the incubator, but not >> questioned it because they're so few and far between it's irrelevant. >> > > I get a bit crazy-headed when I perceive the ASF encroaches on the > independence of a TLP. This isn't really a case of the ASF imposing, but > similar. In my view, the Incubator cannot impede/affect the independence of > another TLP. Structurally. The Foundation creates each PMC as an > individual, independent group. Thus, I believe a few of these steps are > just incorrect. I'd like our documentation to reflect the reality of the > independence of our TLPs. > > I would however pressure that podlings are not capable of completing this >> on their own, and that they should continue to follow the processes defined >> already. They have knowledgeable mentors, but we should generally note >> that the IPMC as a whole is responsible for the podlings. >> > > Absolutely! The referenced page (and the associated guide) explicitly state > it is for existing projects only. (the language could be clarified as "TLP, > not podling", but yeah: definitely not for podlings) > > Cheers, > -g
signature.asc
Description: Message signed with OpenPGP using GPGMail
