Re: Draft schedule for tomorrow's FESCo meeting (19 March 2012)
Hi! /me gave the mail a subject Jon Ciesla wrote on 18.03.2012 23:33: = New business = [...] #topic #822 F18 Feature: AE1000 USB wifi driver - https://fedoraproject.org/wiki/Features/AE1000usb .fesco 822 I must be missing something here. Is that a early April fools joke or is that simply a feature where the Feature owner (and apparently nobody else) first asked for advise on this list and on ker...@lists.fedoraproject.org. If he did it I missed that, which is possible, but I'd assume he would have quickly been told that Fedora normally(¹) doesn't do things like that (e.g. include kernel drivers that are not in the upstream kernel). CU knurd (¹) yes, there are exceptions, but I doubt one will be given here -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Draft schedule for tomorrow's FESCo meeting (19 March 2012)
On Mon, Mar 19, 2012 at 8:25 AM, Thorsten Leemhuis fed...@leemhuis.info wrote: Hi! /me gave the mail a subject Jon Ciesla wrote on 18.03.2012 23:33: = New business = [...] #topic #822 F18 Feature: AE1000 USB wifi driver - https://fedoraproject.org/wiki/Features/AE1000usb .fesco 822 I must be missing something here. Is that a early April fools joke or is that simply a feature where the Feature owner (and apparently nobody else) first asked for advise on this list and on ker...@lists.fedoraproject.org. If he did it I missed that, which is possible, but I'd assume he would have quickly been told that Fedora normally(¹) doesn't do things like that (e.g. include kernel drivers that are not in the upstream kernel). It looks like the feature owner has answered your question on the Talk page already: - https://fedoraproject.org/wiki/Talk:Features/AE1000usb Cheers, Niels -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Draft schedule for tomorrow's FESCo meeting (19 March 2012)
On Mon, Mar 19, 2012 at 08:25:38AM +0100, Thorsten Leemhuis wrote: Hi! /me gave the mail a subject Jon Ciesla wrote on 18.03.2012 23:33: = New business = [...] #topic #822 F18 Feature: AE1000 USB wifi driver - https://fedoraproject.org/wiki/Features/AE1000usb .fesco 822 I must be missing something here. Is that a early April fools joke or is that simply a feature where the Feature owner (and apparently nobody else) first asked for advise on this list and on ker...@lists.fedoraproject.org. If he did it I missed that, which is possible, but I'd assume he would have quickly been told that Fedora normally(¹) doesn't do things like that (e.g. include kernel drivers that are not in the upstream kernel). Yeah, there are a number of problems with this Feature request. 1) No discussion at all with the kernel maintainers 2) Testing and development entirely done against F16, not F17 3) kmod 4) out-of-tree kmod 5) No links to upstream patch submissions Fortunately, I don't think this is even needed anymore. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Draft schedule for tomorrow's FESCo meeting (19 March 2012)
On Mon, Mar 19, 2012 at 8:04 AM, Josh Boyer jwbo...@redhat.com wrote: On Mon, Mar 19, 2012 at 08:25:38AM +0100, Thorsten Leemhuis wrote: Hi! /me gave the mail a subject Thanks! :) Jon Ciesla wrote on 18.03.2012 23:33: = New business = [...] #topic #822 F18 Feature: AE1000 USB wifi driver - https://fedoraproject.org/wiki/Features/AE1000usb .fesco 822 I must be missing something here. Is that a early April fools joke or is that simply a feature where the Feature owner (and apparently nobody else) first asked for advise on this list and on ker...@lists.fedoraproject.org. If he did it I missed that, which is possible, but I'd assume he would have quickly been told that Fedora normally(¹) doesn't do things like that (e.g. include kernel drivers that are not in the upstream kernel). Yeah, there are a number of problems with this Feature request. 1) No discussion at all with the kernel maintainers 2) Testing and development entirely done against F16, not F17 3) kmod 4) out-of-tree kmod 5) No links to upstream patch submissions Fortunately, I don't think this is even needed anymore. I'd think 3 and 4 alone would be enough to block this. 1 is pretty bad, 2 isn't great, and 5 is made worse by 3 and 4. . . -J josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- in your fear, seek only peace in your fear, seek only love -d. bowie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Draft schedule for tomorrow's FESCo meeting (19 March 2012)
Josh Boyer wrote: 5) No links to upstream patch submissions What upstream patch submissions? ;-) The driver he's proposing to ship is the Ralink vendor driver (which happens to be GPLed), not a driver ever intended to go upstream. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Draft schedule for tomorrow's FESCo meeting (19 March 2012)
On 03/19/2012 08:21 PM, Kevin Kofler wrote: Josh Boyer wrote: 5) No links to upstream patch submissions What upstream patch submissions? ;-) The driver he's proposing to ship is the Ralink vendor driver (which happens to be GPLed), not a driver ever intended to go upstream. I think that was his point, yes. -- Peter RFC 882 put the dots in .com. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
