Open
Conversation
Removing Microsoft's copyright violates the license, that's pretty much the point of open-source licenses
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
1 participant
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.
Removing Microsoft's copyright violates the license, that's pretty much the point of open-source licenses. You can add your own copyright but not remove the copyright of others. Otherwise I could just fork any of your open-source projects and remove all references to your name, and by your logic in removing Microsoft's copyright it would be allowed…
Also you can't remove the notice that "Selawik" is a reserved font name, otherwise you could remove any reserved font name by forking the font, changing the name, forking your fork and changing the name back to the original one