Question regarding license

[krisgry]

Hi,
Is it really necessary to include the license header, and specifically the ever-changing copyright years, in all the files in the project? With version control it should not be a problem to figure out what license applied at any given point in time (the LICENCE.md file).

The reason I ask is that the "Updated copyright" commits are difficult to deal with from a maintenance perspective. Three drawbacks, at least:

1. I'm trying to maintain our version of DUNE by keeping it in sync with your upstream version, and every year there is a monster commit that changes every file.
2. It also makes it a bit more cumbersome to track changes in files that have not changed much in a long time, where the git log will have a bunch of "Updated copyright" commits in between the actual changes.
3. from your side, you have to (remember to) update the copyright year every year

Yes, these are relatively easy to get around, but I wanted to hear if there is a good reason for sticking with the current setup, or if it is just old habits.

K

[Bernardo-Gabriel]

Hi @krisgry

Thank you for your patience...
I am guessing this is more of an old (bad) habit than anything else.
We will stick to the current setup until we agree on an approach that better fits our software toolchain.

Bernardo