Skip to content

Replace copyright notice with Apache License 2.0 text#31

Open
ResonanceCache wants to merge 2 commits into
oapi-codegen:mainfrom
ResonanceCache:patch-1
Open

Replace copyright notice with Apache License 2.0 text#31
ResonanceCache wants to merge 2 commits into
oapi-codegen:mainfrom
ResonanceCache:patch-1

Conversation

@ResonanceCache
Copy link
Copy Markdown

Updated the LICENSE file to include the full text of the Apache License 2.0, replacing the previous copyright notice. This follows the same pattern as https://github.com/oapi-codegen/oapi-codegen.

Updated the LICENSE file to include the full text of the Apache License 2.0, replacing the previous copyright notice. This follows the same pattern as https://github.com/oapi-codegen/oapi-codegen.
@ResonanceCache ResonanceCache requested a review from a team as a code owner May 20, 2026 15:42
Comment thread LICENSE Outdated
same "printed page" as the copyright notice for easier
identification within third-party archives.

Copyright [yyyy] [name of copyright owner]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we do this on oapi-codegen itself

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jamietanna I've updated in the next commit

Update copyright year and owner in LICENSE file
@ResonanceCache
Copy link
Copy Markdown
Author

@jamietanna bump with the copyright info.

@jamietanna
Copy link
Copy Markdown
Member

Will take a look in the next few days, thanks. No need to re-nudge :)

Unless there's a specific reason it's higher priority for you?

@ResonanceCache
Copy link
Copy Markdown
Author

My company uses this package (as a dependency of the main oapi-codegen) and we have strict licensing policies, hence the need to have the full license in the repo. Understood if you have other priorities, but it is high for me and my team.

@jamietanna
Copy link
Copy Markdown
Member

OK - I will say in that sense (as someone who's worked in and around the space for a while, but who is not a lawyer) - a short licence is often sufficient for the most widely used tools on the market, so might be worth feeding back to your vendor

For instance https://pkg.go.dev/github.com/oapi-codegen/nullable correctly identifies this as Apache-2.0

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.

2 participants