As you probably already know, expliciting licensing terms is extremely important to let other devs - and not only - 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 "compliant" one through the GH's license wizard tool.
Last but not least, let us know how - in your opinion - we could improve categorization/sorting of collected projects in order to push their evolution by favouring collaborations between developers (and not only).
Hi there, happy 2024 !
Since we've "doxed" it in our HyMPS project (under the VIDEO \ Tools \ Encoders subsection), can you add a license file please ?
As you probably already know, expliciting licensing terms is extremely important to let other devs - and not only - 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:
(badge-generator URL: https://flat.badgen.net/github/license/pigpeppa/xin26x/?label=LICENSE)
Anyway you can easily set a "compliant" one through the GH's license wizard tool.
Last but not least, let us know how - in your opinion - we could improve categorization/sorting of collected projects in order to push their evolution by favouring collaborations between developers (and not only).
Thanks in advance.