Github user ptgoetz commented on the pull request:

    https://github.com/apache/storm/pull/845#issuecomment-153497694
  
    @revans2 
    
    >I know you want to be careful about what gets merged in, and if you insist 
we will go through the IP clearance process, but if we can avoid it I really 
would prefer to do so. We have not had any issues in the past with large 
commits, like when we contributed the security code to storm which followed 
essentially the same process as this code. On my end it is probably going to 
take longer than the 72 hour waiting period to track down the right people to 
get signatures and they will all ask me why we have to do this when my team has 
blanket approval to contribute to storm.
    
    >Like I said if you insist on getting IP clearance we will do it, but all 
it is just going to do is add more pain for me which I really would like to 
avoid if I can.
    
    My apologies for seeming to come out of the blue on this, it’s not my 
intention to put up roadblocks or delay anything. Rather, I’m trying to make 
sure _**we, the PMC**_ do a better job of complying with ASF policy. It’s 
become clear to me that there were a number of cases in the past where we did 
not properly adhere to the IP Clearance policy. A lot of that stems from a lack 
of knowledge on my part and others’ as to when IP Clearance is required. 
I’m trying to correct that going forward.
    
    Admittedly, the paragraph regarding IP Clearance is vague. Here are a few 
points about the pull request that triggered the “IP Clearance flag” in my 
head (please correct me if I’m wrong about anything):
    
    * Was the code developed in the open, using ASF infrastructure? (No, it was 
developed internally at Yahoo, even though the intent was to eventually 
contribute it to the community).
    * Was the Apache community aware of its existence from inception, or early 
on, such that it could contribute to it’s development? (No, see previous 
point. Also, the initial JIRA stated that it was under development internally 
at Yahoo.)
    * Is the commit history intact such that all contributors can be 
identified? (No, all commits are by one individual, and the initial commit 
appears to be an import of an existing codebase that might have involved other 
contributors.)
    
    Please don’t take any of the above as criticisms, I’m just pointing out 
what triggered IP clearance consideration in my head. 
    
    If all the contributors involved are covered either by a CCLA or an ICLA, I 
think all we would need is a software grant. I can do the rest of the work, and 
the code review can certainly continue.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to