Closed MarcoRavich closed 1 month ago
It's not as easy as it seems because we must cover multiple different Licenses. See here: https://github.com/brummer10/guitarix/blob/master/trunk/COPYING
additional some parts been Licensed under the 0BSD
Hi there, GitHub allows to insert multiple licenses on a single repository: https://github.blog/changelog/2022-05-26-easily-discover-and-navigate-to-multiple-licenses-in-repositories/ https://github.com/todogroup/gh-issues/issues/72 https://stackoverflow.com/questions/74181328/github-how-to-add-several-discoverable-licenses
We'll post you an example (that we've already seen... LICENSE.GPL, LICENSE.LGPL and so on as licenses filenames, if not mistaken) as soon as we track it down: stay tuned.
Check out the @xiph's FLAC git to have a good example: https://github.com/xiph/flac
Thanks in advance.
Hi there, 1st of all thanks for this awesome work !
Since we've 'doxed' it in our HyMPS project (under AUDIO resources \ Effects \ Guitar \ Amp Sims), 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/brummer10/guitarix)
You can easily set a standardized one through the GH's license wizard tool.
Last but not least, let us know how we could improve - in your opinion - our categorizations and links to resources in order to favor collaboration between developers (and therefore evolution) of listed projects.
Hope that helps/inspires !