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.

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

Muter should have an explicit license #71

ZevEisenberg opened this issue Feb 16, 2019 · 2 comments


None yet
2 participants
Copy link

commented Feb 16, 2019

From the GitHub help page on licenses:

You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The Open Source Guide provides additional guidance on choosing the correct license for your project.


This comment has been minimized.

Copy link
Contributor Author

commented Feb 18, 2019

Cool! I hadn't heard of GNU Affero before. What was the main factor for choosing it?


This comment has been minimized.

Copy link

commented Feb 18, 2019

Essentially, it prevents closed source software from incorporating any derivatives of Muter without them needing to fully disclose their source code. My main thinking behind this decision was to ensure that a team/individual/organization didn't come along and suck Muter into their code base for a closed-source, for-profit product.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.