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.

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

Apache license is not filled out #441

Closed
Darksonn opened this issue Oct 23, 2019 · 2 comments
Closed

Apache license is not filled out #441

Darksonn opened this issue Oct 23, 2019 · 2 comments

Comments

@Darksonn
Copy link
Contributor

See the following snippet:

crossbeam/LICENSE-APACHE

Lines 188 to 190 in f54db88

Copyright [yyyy] [name of copyright owner]

Compare to:

crossbeam/LICENSE-MIT

Lines 2 to 4 in f54db88

Copyright (c) 2019 The Crossbeam Project Developers

@taiki-e
Copy link
Member

taiki-e commented Oct 31, 2019

If I understand correctly, that is a template for how to apply the Apache License to your work. (see also rust-lang/rust#52236 (comment) and rust-lang/rust#43498)

crossbeam/LICENSE-APACHE

Lines 176 to 189 in f54db88

END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]

@ghost
Copy link

ghost commented Nov 20, 2019

I have filled out the missing parts in LICENSE-APACHE 26 days ago and forgot to close this issue :)

@ghost ghost closed this as completed Nov 20, 2019
exrook pushed a commit to exrook/crossbeam that referenced this issue Oct 7, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants