Good question, John! We will handle it the same way we handle patches that come in via JIRA, or the mailing list, or any other channel. i.e. The creation of a PR against the official mirror is seen as an indication of intent that the work be contributed to the project, as the Apache licenses quite cleverly handles the rest, so we don't have to do anything in particular.
On 27 April 2013 18:05, John Burwell <jburw...@basho.com> wrote: > Noah, > > How do we handle the contributor agreement/IP issues when handling code > submitted through a Github PR? > > Thanks, > -John > > > On Sat, Apr 27, 2013 at 12:45 PM, Noah Slater <nsla...@apache.org> wrote: > > > On 27 April 2013 17:35, Noah Slater <nsla...@apache.org> wrote: > > > > > If we reach consensus, I will start the corresponding [VOTE] thread and > > > complete the rest of process. > > > > > > > D'oh. That's what I get for copying and pasting email templates. > > > > Edit: if we reach consensus, I will just go ahead and request the > > notifications. No need for a vote on something like this unless lazy > > consensus fails. ;) > > > > -- > > NS > > > -- NS
