Skip to content

Add Copyright header to the MIT License#331

Merged
Veetaha merged 1 commit intomasterfrom
feat/add-copyright-to-mit
Aug 19, 2025
Merged

Add Copyright header to the MIT License#331
Veetaha merged 1 commit intomasterfrom
feat/add-copyright-to-mit

Conversation

@Veetaha
Copy link
Copy Markdown
Collaborator

@Veetaha Veetaha commented Aug 19, 2025

The MIT license has a standard header for the copyright notice. Apache doesn't seem to have one. Anyway, I think this should be enough

@Veetaha Veetaha mentioned this pull request Aug 19, 2025
@Veetaha Veetaha requested a review from anelson August 19, 2025 18:14
@WeepingClown13
Copy link
Copy Markdown

@Veetaha this looks good, thanks a lot :) btw why not 2025? copyright years are not necessary in a copyright, but since you have it and are just starting, might as well go with the latest year.

@Veetaha
Copy link
Copy Markdown
Collaborator Author

Veetaha commented Aug 19, 2025

@WeepingClown13

2024 is the year this work started and was made public, which is what the year should stand for according to Wiki🤔

Use of the notice informs the public that a work is protected by copyright, identifies the copyright owner, and shows the year of first publication.

@WeepingClown13
Copy link
Copy Markdown

@Veetaha as I said, copyright years are not mandatory. If you have 2024, then 2024-current is inferred. If you have 2025, then we take it that you have the copyright in the latest year. Even if you not add anything, it still doesn't matter as you own the copyright anyway since the first publishing of the work. So it's nothing to be hung up on. It's your call, doesn't really matter :)

@Veetaha
Copy link
Copy Markdown
Collaborator Author

Veetaha commented Aug 19, 2025

Okay, thanks for looking at this. The year doesn't seem very important, so I'll follow Wiki's stance on this here. Merging, and preparing a patch

@Veetaha Veetaha merged commit f2d1790 into master Aug 19, 2025
36 checks passed
@Veetaha Veetaha deleted the feat/add-copyright-to-mit branch August 19, 2025 19:03
@WeepingClown13
Copy link
Copy Markdown

@Veetaha thank you!

an example for some further reading: https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/

@Veetaha
Copy link
Copy Markdown
Collaborator Author

Veetaha commented Aug 19, 2025

Huh, thanks for sharing that. Curl's view on this is really useful. It's also the reason I intentionally avoided a range of years here =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants