A question on correct copyright text in new files

[Gustavo Romero]

Mark, thanks for clarifying the conventions.

Volker, thanks for providing an example for each case.

Regards,
Gustavo

On 23-03-2017 05:08, Volker Simonis wrote:
> That's right. Just take a look at:
> 
> http://hg.openjdk.java.net/jdk9/dev/hotspot/file/a49c7926d151/test/runtime/7158988/TestPostFieldModification.java
> http://hg.openjdk.java.net/jdk9/dev/hotspot/file/a49c7926d151/test/compiler/codegen/IntRotateWithImmediate.java
> http://hg.openjdk.java.net/jdk9/dev/hotspot/file/a49c7926d151/src/cpu/ppc/vm/assembler_ppc.hpp
> 
> for the various variants.
> 
> Regards,
> Volker
> 
> On Thu, Mar 23, 2017 at 1:21 AM,  <mark.reinhold at oracle.com> wrote:
>> 2017/3/22 14:01:40 -0700, Gustavo Romero <gromero at linux.vnet.ibm.com>:
>>> If it's necessary to include a new file in the hotspot tree, for instance, let's
>>> say the following files:
>>>
>>> src/jdk.vm.ci/share/classes/jdk.vm.ci.hotspot.ppc/src/jdk/vm/ci/hotspot/ppc/PPC64HotSpotJVMCIBackendFactory.java
>>> src/cpu/ppc/vm/macroAssembler_ppc_sha.cpp
>>>
>>> What would be the correct copyright in the header of these two files if the file
>>> is contributed from (a) a person or (b) an entity that signed the OCA?
>>>
>>> License text is kept the same (GPL v2), but besides Oracle copyright should the
>>> author's full name [in case of (a)] or the legal entity name [in case of (b)]
>>> be included as well? What governs the correct choice here?
>>
>> If the file was written solely by a non-Oracle entity (whether an
>> individual or an organization doesn't really matter) and is being
>> contributed under the OCA then a single copyright line naming that
>> entity should be used.
>>
>> If the file was derived by a non-Oracle entity from an existing file
>> somewhere in OpenJDK, with existing copyright lines, then those lines
>> should be carried over to the new file, and a new copyright line naming
>> the entity who created the derived work can be added, if desired.
>>
>> (As usual: This is not legal advice, just a summary of the conventions
>>  long in use around here.)
>>
>> - Mark
>