You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main point of the date is to indicate when the oldest code might start to become public domain.
The start of the date range is more important than adding the current year - you don't have to append the current year to assert copyright ownership.
In general, the current year is not a "copyrightable year" for every track repo.
Therefore the date in each track repo's LICENSE should be specific to that repo, and LICENSE should not be in org-wide-files. Instead, I think we should update every track repo LICENSE to include the year of that repo's creation, and then add the LICENSE to CODEOWNERS so that it requires admin approval to change.
If desired, we could automate appending the current year to each copyright notice when a repo receives "copyrightable changes" in that year. But that's less important.
Additional complication: for older repos, maybe it should be like:
Additional complication, the Inc only existed briefly in... 2017-2018 maybe? I updated the copyright across the board when that happened, then dissolved the Inc and reassigned all assets, copyright, and ownership to the not-for-profit Exercism.
Currently, this repo has a
LICENSE
file in the track-wide files. That is, last year, we changed theLICENSE
in every track repo to contain:org-wide-files/tracks-files/LICENSE
Line 3 in f208e7b
My understanding is that this is bad, because:
Therefore the date in each track repo's
LICENSE
should be specific to that repo, andLICENSE
should not be inorg-wide-files
. Instead, I think we should update every track repoLICENSE
to include the year of that repo's creation, and then add theLICENSE
toCODEOWNERS
so that it requires admin approval to change.If desired, we could automate appending the current year to each copyright notice when a repo receives "copyrightable changes" in that year. But that's less important.
Additional complication: for older repos, maybe it should be like:
See also:
The text was updated successfully, but these errors were encountered: