Update the year in the license file #165

Closed
C-BJ wants to merge 2 commits from C-BJ-patch-1 into main
C-BJ commented 2022-02-14 15:13:53 +00:00 (Migrated from github.com)
  • By selecting this checkbox, I agree to license my contributions to this project under the license(s) described in the LICENSE file, and I have the right to do so or have received permission to do so by an employer or client I am producing work for whom has this right.
- [x] By selecting this checkbox, I agree to license my contributions to this project under the license(s) described in the LICENSE file, and I have the right to do so or have received permission to do so by an employer or client I am producing work for whom has this right.
emidoots commented 2022-02-18 08:07:14 +00:00 (Migrated from github.com)

Hi, sorry but I don't really see a need to do this.

Copyright law in US and EU is the lifetime of the author plus like 70 years. Maybe it makes sense to do in China where copyright expires after 50 years apparently.. but in any case, the code is given away under two very permissive open source licenses so I'm not really worried about this every year.

It's also annoying/tedious to do this everywhere, in every repository, etc. every year 😜 For example, there are multiple copies of these licenses in this repo you missed by accident in this update.

I do appreciate the PR, thank you for taking the time to look / contribute! Hope it's okay I turn this change down. :)

Hi, sorry but I don't really see a need to do this. Copyright law in US and EU is the lifetime of the author plus like 70 years. Maybe it makes sense to do in China where copyright expires after 50 years apparently.. but in any case, the code is given away under two very permissive open source licenses so I'm not really worried about this every year. It's also annoying/tedious to do this everywhere, in every repository, etc. every year 😜 For example, there are multiple copies of these licenses in this repo you missed by accident in this update. I do appreciate the PR, thank you for taking the time to look / contribute! Hope it's okay I turn this change down. :)

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
hexops/mach!165
No description provided.