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

No open source license for this repository #5

Open
ghost opened this issue Jan 31, 2023 · 10 comments
Open

No open source license for this repository #5

ghost opened this issue Jan 31, 2023 · 10 comments

Comments

@ghost
Copy link

ghost commented Jan 31, 2023

For the project to be truly open source it needs to have an open source license. Without a license it's not clear if anyone is allowed to use, modify, or share this repository. You can choose whatever license you want :) I'll show some resources that I personally found helpful.
https://choosealicense.com/
https://opensource.org/licenses
If you have included a license already and I just haven't found it let me know haha.

@TorchedSammy
Copy link
Member

ive actually opened an issue about this on the original repo at cfpi-fpsi/OpenSC4#5 (funnily enough same issue number) and im not sure how to go about adding a license here since the code is really theirs without a license.

@ghost
Copy link
Author

ghost commented Feb 1, 2023

also could i ask? why is this repository completely separate and not a fork of https://github.com/AJEKsoft/OpenSC4/? They seem to have the same git history

@ghost
Copy link
Author

ghost commented Feb 1, 2023

the original developers have been inactive for months 😭

@TorchedSammy
Copy link
Member

the original developers have been inactive for months 😭

yes, that's why. me and a few other people are starting it up again, and having this org repo allows for one central repo for contributions and other things

@AdrienJaguenet
Copy link
Contributor

I'd rather use (A)GPLv3 but I'm willing to use another license if other contributors prefer.

@TorchedSammy
Copy link
Member

I don't think the additional clause in the agpl is needed, so just plain gpl works fine.

@AdrienJaguenet
Copy link
Contributor

I'm thinking AGPL because networking features are planned

@TorchedSammy
Copy link
Member

oh true, it'd be good then

@ghost
Copy link
Author

ghost commented Feb 1, 2023

I prefer the GPL licenses personally because im not a big fan of someone potentially using open source code in proprietary software. AGPLv3 is fine with me :D!

@stephen-zhao
Copy link

Ya that's my main concern with MIT too

@TorchedSammy TorchedSammy linked a pull request Feb 9, 2023 that will close this issue
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

Successfully merging a pull request may close this issue.

3 participants