accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Billie Rinaldi <>
Subject Re: Contributions from github pull requests and license grant
Date Tue, 15 Oct 2013 20:11:22 GMT
Oops, sorry [1].

All of these links still say that you explicitly need to check a box
assigning license to the ASF.  That is not actually true: any code
submitted through ASF infrastructure is assumed to have license assigned to
the ASF, and the checkbox used to exist as a way not to assign license.
The checkbox no longer exists.  Anyway, I haven't seen any guidance yet
that says we can accept pull requests without the contents of the patch
also being attached to a ticket.


On Tue, Oct 15, 2013 at 1:08 PM, Billie Rinaldi <>wrote:

> Here [1] is another data point.
> On Tue, Oct 15, 2013 at 1:03 PM, Josh Elser <> wrote:
>> We should probably be ensuring that we have something stating that the
>> contributor is assigning license to the ASF. I remember talking about this,
>> but I don't recall the outcome (will have to search history).
>> I'm not sure if there are specific steps that need to be formally
>> followed or if the contributor stating the above on a Jira issue is
>> sufficient.
>> On 10/15/13 3:50 PM, Sean Busbey wrote:
>>> I don't recall a discussion happening about granting license to the ASF
>>> when the repo moved to git. Looking at the git workflow guide[1], I don't
>>> see any mention of licensing.
>>> In other projects (e.g. Avro[2] and Hive[3]) assigning license to the ASF
>>> is an important part of submitting a contribution. In those projects,
>>> people are instructed to attach their patches to an open jira so that
>>> license can be granted; pull requests from github generally aren't
>>> allowed.
>>> Do we have a stance as a project on this? I think those two projects
>>> basically say that the grant is required by the Apache License itself.
>>> Are
>>> there ASF rules that can provide guidance on this?
>>> -Sean
>>> [1]:**git.html<>
>>> [2]:
>>> To+Contribute#HowToContribute-**Contributingyourwork<>
>>> [3]:
>>> HowToContribute-**Contributingyourwork<>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message