According to the LICENSE file in their git repo, the code in the repo seems to be gplv2. Not sure if that proves anything. I'll do the licensecheck -r later and update you guys.
On Mon 10 Sep, 2018, 6:08 PM Richard Shaw, <hobbes1...@gmail.com> wrote: > On Mon, Sep 10, 2018 at 7:27 AM Rex Dieter <rdie...@math.unl.edu> wrote: > >> Jan Rybar wrote: >> >> > Hi Abhiram, >> > >> > you can make COPR. No one asks, no harm done, everyone's happy. >> >> I don't think copr is appropriate either, >> https://docs.pagure.org/copr.copr/user_documentation.html#faq >> >> To me, makes it pretty clear that if it can't be in fedora, it can't be >> in >> copr either. >> > > You need to go through the code (maybe use licensecheck -r to help) to see > if all the code is acceptable. If so I'll defer to Neal on the COPR > acceptability. Another alternative is until formal support is added to the > kernel you can look at packaging it in RPM Fusion. If it's truly FOSS but > just not acceptable because it's a kernel module it can go in the Free > repository. If it's using proprietary code (even if the project is GPL > licensed) then as long as it's redistributable, it can go in the Non-Free > repository. > > Thanks, > Richard > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org >
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
