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

License question #185

Closed
IzzySoft opened this issue Feb 19, 2022 · 6 comments
Closed

License question #185

IzzySoft opened this issue Feb 19, 2022 · 6 comments

Comments

@IzzySoft
Copy link

I've searched the repo, but couldn't find any information concerning the license used by this project. What license does apply to your code? Could you please add that information? Thanks in advance!

@IzzySoft
Copy link
Author

That means "all rights reserved" and might scare away potential contributors as well as potential users. Why not choose one that fits? If you don't care, that could even be the WTFPL (Do What The F*ck You Want To Public License). Otherwise, you can e.g. find some good recommendations here. It's your software, so the choice is yours 😃

@yasinkacmaz
Copy link
Owner

The thing is I didn’t think about it, just made the repo as open. I am not even sure whether it is required.

@IzzySoft
Copy link
Author

If it's "required" depends on many things. If you want your app being "F/LOSS" – i.e. free, libre, open-source software – it indeed is required, as without a license it's just "source available" and neither free/libre (as "no license" implicitly means "all rights reserved": you didn't grant usage) nor "open" (as due to the "all rights reserved" nobody except you is really "open" to fully use it).

So it's fully up to what you want it to be. If you want others to "freely participate" (actively or passively), you should choose a license. Depending on how permissive you want it to be, and how much "rights" you want to preserve, you can choose a rather permissive license (PublicDomain, WTFPL, Apache-2.0, MIT, BSD-*-Clause). If you want to avoid someone else makes profit from your work without giving back, pick something on the more restrictive end (e.g. AGPL-3.0 – so-called "copy-left" licenses including a clause that all derivative works must use the same license, to put it simple).

@IzzySoft
Copy link
Author

So anydecision on this, @yasinkacmaz? I'd really like to include your app with my repo – but cannot without a license (to my experience, it rarely is "added soon" thereafter, and users of my repo expect FOSS, which means it must have a FOSS license).

@yasinkacmaz
Copy link
Owner

Hello @IzzySoft sorry for the delayed response. I've included MIT Licence for this repository. I guess now you can use it safely.

@IzzySoft
Copy link
Author

Thanks a lot! I've just integrated it with my catalog, it will show up here with the next sync around 6 pm UTC tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants