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
I'm used to seeing a license included in the readme or a txt file in the root (license.txt, legalnotes, etc.). Is this information found somewhere else in the repo? Can someone add an appropriate reference in a "usual" place?
The text was updated successfully, but these errors were encountered:
Apparently, I need to go a step further and ask "how is anyone using this library legally" under the current license. According to CC, this license is only compatible with itself:
Since this is an OWASP project, we stick with the OWASP policies regarding licensing. After looking into it again, I believe OWASP has changed it's licensing policies.
Thanks. If they're resistant to a different license (whether GPL-compatible or not), I'm happy to make the case directly to OWASP. It's not uncommon for content production organizations to try and use content licenses for software. Unfortunately, these licenses (except CC0) really aren't appropriate for this use... and the people it hurts most are the people who make the effort to respect the license.
I'm used to seeing a license included in the readme or a txt file in the root (license.txt, legalnotes, etc.). Is this information found somewhere else in the repo? Can someone add an appropriate reference in a "usual" place?
The text was updated successfully, but these errors were encountered: