Sent from my iPhone

> On May 4, 2021, at 8:31 AM, John D. Ament <johndam...@apache.org> wrote:
> 
> IP clearance should be required per this line.
> 
> *This form is not for new projects.*
> 
> This is for projects and PMCs that have already been created and are
> receiving a code donation into an existing codebase. Any code that was
> developed outside of the ASF SVN repository and our public mailing lists
> must be processed like this, even if the external developer is already an
> ASF committer.
> 
> Though I’m realizing we need to clarify that we have more than SVN now.

Considering that people develop PRs in their own branches and forks I think 
that we might need to rethink this interpretation some more.

IMO If there is an ICLA or CCLA that covers the contribution it should be fine.

Regards,
Dave
> 
> 
>> On Tue, May 4, 2021 at 11:07 Wes McKinney <wesmck...@gmail.com> wrote:
>> 
>> We have a situation in Arrow where one of our committers / PMC members
>> built an add-on project based on Apache Arrow but in his separate
>> GitHub account
>> 
>> http://github.com/jorgecarleitao/datafusion-python
>> 
>> The proposal is to merge it into one of Arrow's new satellite Rust
>> repositories
>> 
>> http://github.com/apache/arrow-datafusion
>> 
>> While this code was externally developed by a single person with an
>> ICLA on file, the hope was simply to PR the code and be done with it,
>> but we would like to know if it is recommended to do a full IP
>> clearance procedure for this simplified situation of a smallish solo
>> project from an existing committer in an Apache community.
>> 
>> Thanks,
>> Wes
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to