I would check with [email protected] to be sure, but here is my understanding of relevant ASF policies:
All work done and contributed by an individual is bound by the terms of your ICLA. You retain the copyright ownership under ASLv2, but have granted the ASF (an irrevocable?) permission and license to use your work. If the work is copyright assigned to a different organization, then I believe it has to be brought in as a 3rd party work. It can retain the original headers, as long as the terms as compatible, and needs to be called out in NOTICE file like you alluded to. Dev-for-hire work happens pretty regularly in today's world; I don't think anybody is under the illusion that Lucene is built solely by a group of hobbyists. CCLAs cover most of the cases where the funding organization is willing to forgo copyright ownership, but that doesn't sound like the case here. I'm not sure what happens if a different person comes in later and finds a bug and makes changes to those files. Presumably we're fine, but some people might feel a little strange assigning copyright back to a unknown company instead of licensing use to the ASF. Mike On Tue, Mar 1, 2016 at 3:19 PM, [email protected] < [email protected]> wrote: > I'm considering doing some enhancements to Lucene/Solr on behalf of > another organization/entity who wants me to include copyright statements to > them. Same ASLv2 license. This is no big deal; right? I see we've > already got some source files with non-ASF copyright licenses (e.g. > Automata.java and others), and I see we have NOTICE files referencing it > too. I also see some special support in common-build.xml to detect it. > > ~ David > -- > Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker > LinkedIn: http://linkedin.com/in/davidwsmiley | Book: > http://www.solrenterprisesearchserver.com >
