Expliciting the licensing terms is extremely important to let other devs (and not only) better/faster understand how to reuse/adapt/modify your code 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:
Anyway you can easily set a standardized one through the GH's license wizard tool.
Last but not least, let us know how - in your opinion - we could improve our categorizations and links to resources in order to favor collaboration between developers (and therefore evolution) of listed projects.
MarcoRavich
commented
9 months ago
Hi there, 1st of all thanks for your awesome work !
Since we've "doxed" it in our HyMPS project (under the AUDIO \ Tools page \ Declipping subsection), can you please add a license for it ?
Expliciting the licensing terms is extremely important to let other devs (and not only) better/faster understand how to reuse/adapt/modify your code 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:
Anyway you can easily set a standardized one through the GH's license wizard tool.
Last but not least, let us know how - in your opinion - we could improve our categorizations and links to resources in order to favor collaboration between developers (and therefore evolution) of listed projects.
Thanks in advance.