Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upLicense #8
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
steveklabnik
Dec 28, 2015
Member
Since I derived this from @phil-opp 's code, which is apache2 licensed, it should also be apache2. https://github.com/phil-opp/blog_os/blob/printing_to_screen/LICENSE
Thanks for pointing this out, I'm really good about it usually, but forgot in this case. Phil, is it just apache2 or dual licensed?
|
Since I derived this from @phil-opp 's code, which is apache2 licensed, it should also be apache2. https://github.com/phil-opp/blog_os/blob/printing_to_screen/LICENSE Thanks for pointing this out, I'm really good about it usually, but forgot in this case. Phil, is it just apache2 or dual licensed? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
phil-opp
Dec 28, 2015
Contributor
Well, honestly I don't know much about licenses. What would be the advantages of dual licensing?
|
Well, honestly I don't know much about licenses. What would be the advantages of dual licensing? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
steveklabnik
Dec 28, 2015
Member
Well, the only reason I ask is because Rust itself is dual licensed apache2/MIT, and so a lot of rust projects are as well.
The advantage is that if someone prefers one license over the other, they can create derived works under just the one they prefer. People do dual apache2/MIT because MIT is simpler, but has no patent clauses, and apache2 is more complex, but has protection for them. So some people don't like the extra complexity.
Really, it doesn't matter to me personally, I just want to make sure I do right by you, and anyone else who I happen to take a peek at their code :).
|
Well, the only reason I ask is because Rust itself is dual licensed apache2/MIT, and so a lot of rust projects are as well. The advantage is that if someone prefers one license over the other, they can create derived works under just the one they prefer. People do dual apache2/MIT because MIT is simpler, but has no patent clauses, and apache2 is more complex, but has protection for them. So some people don't like the extra complexity. Really, it doesn't matter to me personally, I just want to make sure I do right by you, and anyone else who I happen to take a peek at their code :). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
phil-opp
Dec 28, 2015
Contributor
Ok thanks for the overview. I'm too tired to think about licenses right now but I will consider dual licensing (any drawbacks?).
|
Ok thanks for the overview. I'm too tired to think about licenses right now but I will consider dual licensing (any drawbacks?). |
steveklabnik
closed this
in
607e0ee
Dec 28, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
I've pushed up the Apache2 license. Thanks again @dpen2000 ! |
added a commit
to dpen2000/kernel
that referenced
this issue
Dec 29, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
phil-opp
Dec 29, 2015
Contributor
I've updated the license of blog_os. It's now apache2/MIT dual licensed.
|
I've updated the license of blog_os. It's now apache2/MIT dual licensed. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Cool, I will follow suit. |
dpen2000 commentedDec 28, 2015
What's the license for the code here?