You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A quick but careful inspection of Falcon's source directory did not reveal information as to what was Falcon's license.
This is an important issue as it means that, by default, Falcon is covered by the usual author copyright policy, which does not allow very much (in particular not reuse of the sources). Whatever your preference as authors are, it should be made explicit with, at the very least:
a mention of the software license you prefer in the README of the project, along with enough information to identify the authors (names and mail adresses)
if there is any ambiguity as to what this license is (eg. "the BSD license" may mean several), a copy of the license text in a LICENSE file at the root of the repository, or the src/ directory
Cautious licensing-aware open source developers also add a comment header to each source file in the project, recapitulating the authors copyright and the chosen license. I know that academic code dumps are not always that rigorous and that's probably ok, but the licensing information must still be provided somewhere.
PS: In case you would be unfamiliar with licensing questions and unwilling to make the investment to look at depth at those issues, I would recommend simply reusing the license of the upstream CPython code -- but I don't actually know which it is.
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up. I had intended on putting a license file in at some point, but obviously forgot along the way.
The CPython license itself appears to be specific to the Python foundation; I instead used the Apache license which they recommend for modules which might end up in the CPython distribution. (Not that I expect that for Falcon!)
A quick but careful inspection of Falcon's source directory did not reveal information as to what was Falcon's license.
This is an important issue as it means that, by default, Falcon is covered by the usual author copyright policy, which does not allow very much (in particular not reuse of the sources). Whatever your preference as authors are, it should be made explicit with, at the very least:
src/
directoryCautious licensing-aware open source developers also add a comment header to each source file in the project, recapitulating the authors copyright and the chosen license. I know that academic code dumps are not always that rigorous and that's probably ok, but the licensing information must still be provided somewhere.
PS: In case you would be unfamiliar with licensing questions and unwilling to make the investment to look at depth at those issues, I would recommend simply reusing the license of the upstream CPython code -- but I don't actually know which it is.
The text was updated successfully, but these errors were encountered: