On Tue, Oct 15, 2013 at 6:34 PM, Billie Rinaldi <[email protected]> wrote: > > The licensing of a "Contribution" is explicitly discussed in the Apache > License. So the licensing isn't assumed because it's ASF JIRA, it's > assumed because our code is licensed under the Apache License, and any > "Contribution" to it is therefore also Apache licensed.
I think we (specifically, me) are getting mixed up on the terminology. I didn't think we were talking about what the license is (contributions are most certainly AL 2.0 licensed), so much as its assignment (or perhaps, rather, the assignment of ownership or copyright), which determines things like whether the license can be changed (relicensed under a future AL 3.0, for instance), and how we cite it (eg. do we have to put something separate in the NOTICE file). > Judging by how other projects are handling this, I am left to conclude that > a "Contribution" must consist of a patch itself, and not a reference to a > patch that exists outside of our infrastructure. I have not yet found > explicit guidance about this. If that's true, then I'm not sure how it benefits us to have the ASF infrastructure forward pull requests to the GitHub mirror to our dev list. Instead, we should emphasize how to create patches with "git format-patch", and how to apply them with a quick "curl <JIRA patch url> | git am" or similar command.
