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.

Sign up for GitHub

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

Jump to bottom

Figure out licensing problems #312

Open
KyleMaas opened this issue Jan 28, 2023 · 0 comments
Open

Figure out licensing problems #312

KyleMaas opened this issue Jan 28, 2023 · 0 comments
Labels
licensing

Comments

@KyleMaas
Copy link
Contributor

Related to #305, REUSE found some components which are licensed as AGPL-3.0-only. This is a little problematic because most of the rest of the project seems to be MIT, but because of those components, the whole thing could only really be used as AGPL-3.0 which means all applications built on a go-ssb core would also have to use that license. Would be great if we could find all AGPL-3.0-only stuff and either replace it with libraries which give the developer more freedom or see if we can get those components relicensed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
licensing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@decentral1se @KyleMaas