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

[REQ] Add a (GH-compliant) license file #2

Closed
MarcoRavich opened this issue Feb 3, 2025 · 3 comments
Closed

[REQ] Add a (GH-compliant) license file #2

MarcoRavich opened this issue Feb 3, 2025 · 3 comments

Comments

@MarcoRavich
Copy link

Hi there, 1st of all thanks for this awesome work !

Since I've 'doxed' it under the TWEAKERS page of the Opendows project, can you please add a GH-compliant license file for it ?

As you know, expliciting licensing terms is extremely important to let anyone better/faster understand how to reuse/adapt/modify sources (and not only) in other open projects and vice-versa.

Although it may sounds like a minor aspect, license file omission obviously causes an inconsistent generation of the relative badge too:


(badge-generator URL: https://badgen.net/github/license/Awneti/Optimizing-File)

You can easily set a standardized one through the GH's license wizard tool.

Last but not least, I invite you to join CS Discussions to share ideas about Windows tweakings.

Hope that helps/inspires !

@Awneti
Copy link
Owner

Awneti commented Feb 3, 2025 via email

@MarcoRavich
Copy link
Author

Since I am new to github and posting my work online, I would like to kindly
ask you to explain what a GH Compliant is. In my understanding, this is
some type of agreement for using something, isn't it?
Looking forward to a prompt reply!
Yours faithfully,
Awneti

Hi there, thanks for quick reply.

Well GitHub recognizes a subset of all open source licenses - just click on GH's license wizard tool to check the list - as "compliant" even if, of course, you can choose anyone you like.

Hope that helps.

@Awneti
Copy link
Owner

Awneti commented Feb 9, 2025

Greetings once again!

I had some troubles understanding the concept of licensing on GitHub and as a result I couldn't figure out what you meant in your comment. However, after I released WSC v2 I finally understood the meaning of your words and added a license branch.

Thank you for assisting me throughout the way!

Repository owner locked as resolved and limited conversation to collaborators Feb 9, 2025
@Awneti Awneti closed this as completed Feb 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants