[Proposal] PMM-7 Updade year in license headers

[artemgavrilov]

PMM-7

[ademidoff]

@artemgavrilov IMO this is not necessary, since the meaning of the year in copyrights is "Since [year] up to now".

Therefore, the repo files will bear that license until it changes, which is when we should update the year. If there is no intention to change the license, we can leave the year as is.

[artemgavrilov]

@artemgavrilov IMO this is not necessary, since the meaning of the year in copyrights is "Since [year] up to now".

Therefore, the repo files will bear that license until it changes, which is when we should update the year.

Hm, I barely remember that we discussed what to do with the year and I thought that we agreed to update it. I am mistaken and we agreed to not touch year, shouldn't in be 2017 then (year when PMM project started)?

[ademidoff]

@artemgavrilov IMO this is not necessary, since the meaning of the year in copyrights is "Since [year] up to now".
Therefore, the repo files will bear that license until it changes, which is when we should update the year.

Hm, I barely remember that we discussed what to do with the year and I thought that we agreed to update it. I am mistaken and we agreed to not touch year, shouldn't in be 2017 then (year when PMM project started)?

In theory we could put 2017 in there, but I don't see much value added.

Anyway, even if there was a theoretical benefit, in my opinion it would just not be worth the effort of:

• touching 750+ files
• dealing with conflicts in v3

[artemgavrilov]

@artemgavrilov IMO this is not necessary, since the meaning of the year in copyrights is "Since [year] up to now".
Therefore, the repo files will bear that license until it changes, which is when we should update the year.

Hm, I barely remember that we discussed what to do with the year and I thought that we agreed to update it. I am mistaken and we agreed to not touch year, shouldn't in be 2017 then (year when PMM project started)?

In theory we could put 2017 in there, but I don't see much value added.

Anyway, even if there was a theoretical benefit, in my opinion it would just not be worth the effort of:

* touching 750+ files

* dealing with conflicts in v3

Up to PMM team to decide, that's just a proposal.

Regarding approaches, PostgreSQL for example updates headers yearly: postgres/postgres@29275b1

If we will stick with 2023 over time it may look weird.

[artemgavrilov]

@BupycHuk @ademidoff Folks, I'm leaving this up to you to decide what to do. I'm ok with any option.

[ademidoff]

Closing this for now, will revisit once we stop maintaining v2.