On Fri, Oct 10, 2008 at 10:51 AM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: > On Thu, Jul 31, 2008 at 10:19 AM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: >> On Thu, Jul 31, 2008 at 10:12 AM, Johannes Berg >> <johannes@xxxxxxxxxxxxxxxx> wrote: >>> On Thu, 2008-07-31 at 10:05 -0700, Luis R. Rodriguez wrote: >>> >>>> > I would also add to the contract a requirement to offer Linux support >>>> > for, say, the next five years. >>>> >>>> Not sure if we should call it a contract unless its understood its an >>>> informal contract with the community. >>> >>> There has to be some form of contract. The logo is copyrighted, >>> obviously, so there has to be a contract for you to be allowed to print >>> it on a box. >> >> Heh, Whatever makes the copyright holders happy :) I suspect the >> copyright holder are after the community's best interests anyway. >> >>>> Also I don't think we should be >>>> specific about a time frame for support -- its difficult enough to get >>>> the driver upstream, not that its not possible I just think it we >>>> should strive to at least get vendors to properly support Linux by >>>> submitting their drivers for upstream into Linus' tree. Support tends >>>> to come naturally after that :) >>> >>> Because sometimes there are users who care. I think though that the >>> vendor should participate in future development by testing and fixing >>> their driver, for at least a period of time. Five years may be too much, >>> given the current chip livetime maybe one or two would make sense, >>> kernel releases are only roughly every three months. >>> >>> Mind you, I wasn't talking about user support, but rather development >>> support, kinda like a SUPPORTED tag in the MAINTAINERS file. >> >> This seems reasonable. > > If we can formalize on this it would be great. Oh and the reason is we want to help users track devices supported by us on the kernel (2.6.27, which was released today). Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
