Justin,
Sorry, I forgot to CC you. If this makes it more frictionless to turn around,
here is a link to a .docx:
https://enfascination.com/cloud/index.php/s/aocOsOLDVFV4Vpi
If you can, please provide it with letterhead and signature in pdf format.
best,
seth.
Seth Frey
Assistant Professor
C
Hi,
> If you look at these NOTICE files: for Hadoop, it is still dated 2006;
> Spark is dated 2014;
Spark and Hadoop license and notice files, are for a a number of reasons. poor
examples to copy, please don’t copy what they do.
Thanks,
Justin
--
Hi,
> It is my understanding that if a file has not been substantially changed,
> that it is not necessary to change the year on a Copyright notice every
> time the year rolls over.
INAL but under US law my understanding is:
- The copyright notice contains the word copyright or the symbol, the y
IANAL, but I think for an individual file your analysis is correct, i.e. no
change required if no substantive change to the file.
For the NOTICE file, my understanding is that it represents a summary for
the entire release, so best to change.
I don't have a definitive reference to give you though t
Paul,
WRT the year bump on Copyright notices.
It is my understanding that if a file has not been substantially changed,
that it is not necessary to change the year on a Copyright notice every
time the year rolls over.
As for the NOTICE file, it has not changed at all. So it should not be
necess
