Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When we fork an Apache License 2.0 project that we depend on, are there any restrictions on the name/path for imports #354

Closed
dims opened this issue May 27, 2022 · 3 comments
Closed

When we fork an Apache License 2.0 project that we depend on, are there any restrictions on the name/path for imports #354

dims opened this issue May 27, 2022 · 3 comments

Comments

@dims
Copy link
Member

dims commented May 27, 2022

Context: please see discussion in kubernetes-sigs/yaml#76 (comment)

cc @mkdolan
@dims dims mentioned this issue May 27, 2022
Merged
@caniszczyk
Copy link
Contributor

In short, no restrictions on name/path for imports, you just have to preserve any copyright information in the files (along with any usual attributions)

@dims
Copy link
Member Author

dims commented May 27, 2022

thanks @caniszczyk !!! wanted this on the record :)

@dims
Copy link
Member Author

dims commented Aug 9, 2022

related to cncf/toc#877

@dims dims mentioned this issue Aug 9, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dims @caniszczyk