Sure, COPR is always an option, but since this is a driver, I think it
would benefit everyone if it was pushed upstream, y'know?

I'm currently reading up on how to contribute to the kernel so that I can
help push this. :D

Any tips are welcome!

On Mon 10 Sep, 2018, 1:18 PM Jan Rybar, <[email protected]> wrote:

> Hi Abhiram,
>
> you can make COPR. No one asks, no harm done, everyone's happy.
>
> On 09/08/2018 02:52 PM, Neal Gompa wrote:
> > On Sat, Sep 8, 2018 at 8:49 AM Abhiram Kuchibhotla
> > <[email protected]> wrote:
> >>
> >> Hi all,
> >> So, the other day I ordered a USB Wireless AC adapter for my pc, and I
> was surprised to see that it didn't automatically start working.
> >> After looking around, I came across this tutorial that mentioned this
> github page.
> >>
> >> The driver installation worked, and the device runs.
> >>
> >> So, I would like to package it for Fedora, but I am not sure if it is
> allowed. The github page's LICENSE document says GPLv2, but I just wanted
> to make sure before I packaged it.
> >>
> >> Could someone please help me out?
> >
> > kmod packages are not permitted in Fedora, in any form:
> >
> https://fedoraproject.org/wiki/Packaging:Guidelines#No_External_Kernel_Modules
> >
> > Instead, you should work with the Fedora kernel maintainers to figure
> > out what's needed to make it work upstream.
> >
> _______________________________________________
> devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]
>
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]

Reply via email to