This repository has been archived by the owner on Sep 22, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
Using a single LICENSE file #2
Comments
As far as I'm concerned, any permissive open source license works for this repo. However, I don't know if IETF requires some specific license for projects like this. |
Checking into it now. |
It's up to the WG. I'll suggest Apache 2.0 on-list. |
Folks on-list seem to prefer Simplified BSD. If this causes heartache for any contributors, please speak up; I'd rather have the contribution. |
I'm also OK with relicensing my previous work on this. |
squirrelfm
pushed a commit
to microsoftarchive/http2-test
that referenced
this issue
Feb 18, 2014
squirrelfm
pushed a commit
to microsoftarchive/http2-test
that referenced
this issue
Feb 18, 2014
panarasi
pushed a commit
to microsoftarchive/http2-test
that referenced
this issue
Feb 18, 2014
Fixed issue http2#2
Closed
Working on a pull request for this. |
BSD 2-clause is fine. |
squirrelfm
pushed a commit
to microsoftarchive/http2-test
that referenced
this issue
Feb 19, 2014
Merged
panarasi
pushed a commit
to microsoftarchive/http2-test
that referenced
this issue
Feb 19, 2014
Looks good to me. |
See my comments there. Common practice is to do something like:
in the files. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'd suggest using a single LICENSE file in the root directory instead of pasting the license in every file. Is there any reason to copy it around everywhere?
The text was updated successfully, but these errors were encountered: