You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@crunch.apache.org by Josh Wills <jw...@cloudera.com> on 2012/06/29 19:32:41 UTC

kiyan's contribution

My dear mentors,

I'm trying to understand the best way to incorporate this contribution
into Crunch-- a scala repl for Scrunch:

https://github.com/cloudera/crunch/pull/42

He did the pull relative to the cloudera/crunch mirror, which I've
been keeping in sync with the apache git repo while we get the rest of
the infrastructure setup.

I'm doing the CCLA emails today-- should I incorporate this change now
and have Kiyan sign off on it as part of the CLA email I send him for
his other patches? Or should we do it as a new patch separate from the
contributor license agreeements on the existing code? And if so, what
is the best way to do that? Create a JIRA and have him check the box
indicating that the copyright to the code is assigned to apache?

Sorry for the basic Q-- we hadn't run into this situation yet since
all of the patches since the apache repo were setup have come from
committers.

J

-- 
Director of Data Science
Cloudera
Twitter: @josh_wills

Re: kiyan's contribution

Posted by Arun C Murthy <ac...@hortonworks.com>.

I'd wait and ask him to post it as a patch to Apache Jira.

thanks,
Arun

On Jun 29, 2012, at 10:32 AM, Josh Wills wrote:

> My dear mentors,
> 
> I'm trying to understand the best way to incorporate this contribution
> into Crunch-- a scala repl for Scrunch:
> 
> https://github.com/cloudera/crunch/pull/42
> 
> He did the pull relative to the cloudera/crunch mirror, which I've
> been keeping in sync with the apache git repo while we get the rest of
> the infrastructure setup.
> 
> I'm doing the CCLA emails today-- should I incorporate this change now
> and have Kiyan sign off on it as part of the CLA email I send him for
> his other patches? Or should we do it as a new patch separate from the
> contributor license agreeements on the existing code? And if so, what
> is the best way to do that? Create a JIRA and have him check the box
> indicating that the copyright to the code is assigned to apache?
> 
> Sorry for the basic Q-- we hadn't run into this situation yet since
> all of the patches since the apache repo were setup have come from
> committers.
> 
> J
> 
> -- 
> Director of Data Science
> Cloudera
> Twitter: @josh_wills

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/