Fix Copyright Placeholder in LICENSE File#4
Open
KaganCanSit wants to merge 1 commit intoLaurieWired:mainfrom
Open
Fix Copyright Placeholder in LICENSE File#4KaganCanSit wants to merge 1 commit intoLaurieWired:mainfrom
KaganCanSit wants to merge 1 commit intoLaurieWired:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello Ms. Laurie,
I reviewed the project after watching your video and noticed a small issue in the LICENSE file.
The Apache 2.0 license template was present but the copyright line was still using placeholder values:
Copyright [yyyy] [copyright holder's name]I've replaced this line with:
Copyright 2025 Laurie Kirk (LaurieWired)to make the license legally valid and unambiguous for downstream users. I thought it might be good to highlight your Github username. I'm not sure.Note on License Compliance
According to Section 4 of the Apache License 2.0, each source file should ideally include a license header. For example:
Adding such headers ensures full license compliance and prevents ambiguities when individual files are reused.
If you prefer a follow-up PR on this issue or have any other suggestions for changes you think we could make, please let me know.
Best regards,