Nico Huber has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/36479 )
Change subject: vendorcode/eltan: cleanup of Kconfig files ......................................................................
Patch Set 2:
(1 comment)
https://review.coreboot.org/c/coreboot/+/36479/1/src/vendorcode/eltan/Kconfi... File src/vendorcode/eltan/Kconfig:
https://review.coreboot.org/c/coreboot/+/36479/1/src/vendorcode/eltan/Kconfi... PS1, Line 4: 2014-2019
As far as I your interpretation of a range is not correct. In my opinion, this means that the file was created in 2014 and last updated in 2019.
That disagrees with the article you linked below.
It doesn't state anything about the frequency of the changes.
I looked it up and found the explanation below on: https://epiphany.law/articles/copyright/copyright-dates-single-year-or-range
Once in a while, you might see what looks like a date range instead of a single year of first publication, such as: Epiphany Law Pty Ltd, 2006-2016. This is appropriate for ‘documents’ such as web pages or software programs which are constantly being revised and updated incrementally. The ‘start’ year should be the date of the oldest content still contained in the work, with the ‘end’ year being the last year that the work was revised.
This is oversimplifying things. But so was I. It's not worth arguing about, as copyright doesn't apply to this kind of file, IMHO.
This is basically independent of the comment that the copyright to code ratio is a bit odd. I will change it to 2019 as this is the first version on coreboot anyhow
What matters most is the year of the first publication, if that is 2019, sounds good to me.