OSDL and the kernel community

I quote here:

It was created by 17 of the top Linux kernel developers, and has their implicit backing. If anyone wants more details, please just let me know Proposals for how OSDL can help serve the vendor community

• [0]Create a program that can be used to get hardware specifications that are only available under a NDA to individual developers. This will entail creating a legal entity under OSDL that can sign the NDA with the company, and provide the individual developer that needs the spec with it. Also, if the developer moves on to do something else, OSDL will still have access to the spec if another developer wants access to it.
• Provide some way for developers to access hardware before it is publicly available. This will [1]help the company by allowing kernel developers to help out with drivers and code before it is released to the general public, which will help them with their deadlines of releasing working drivers at the same time hardware is available.
• A lot of time, when a vendor tries to get code accepted into the Linux kernel, it is a very frustrating task for both sides. Large code changes are sometimes just dismissed as they do not take into [2]consideration the way the kernel is developed (small changes over time), or they just do not follow the basic rules (coding style, submission process, etc.) We need an approach that will make it easier for everyone involved, and one proposal to do this is to have a training conference. [3]Kernel developers and subsystem maintainers will be willing to provide training on what the proper procedures are, and case studies of what has failed in the past, and why. It will also allow [4]vendor developers to meet directly with the kernel developers to help ease any tension that might occur over email, and will provide a neutral ground for everyone involved.

Since after all, the results of such maintenance will have to satisfy the whatever (public) community would be left.

[1]: Will this "help" be compensatable? Since you mention that "deadlines" will be involved?
If such a "help" would be compensatible, then how does Tom, Dick and Harriet get into the OSDL recommended developer club, since from [0] OSDL has singed an NDA for the specs and such specs are given by OSDL to a developer of their (OSDL's) choosing (from [0]).

[2]: Will such rules be evolving? Will they be publicly announced to the community? Would it be possible for Joe Schmoe to adhere to those rules without going through one of your training sessions (from [3])?

[3]: How much will such a training cost? Will I have to travel to Portland to take this training, or will you open franchises world-wide? Can I take this training on-line? Will I be able to take this training alongside RHCE and MSCE training sessions?

[4]: You say "vendor developers meet directly with kernel developers" -- I thought that "vendor developers" were the "kernel developers". I didn't know that there were a distinction between the two. I thought that "kernel developers" were in fact holding jobs at vendors, and contributing to the kernel wasn't their full time job, but was merely a by-product of their professional job.

From [0], and [1] I thought that there would no longer be any need for "vendor developers", since this has now been annexed by "company gets in touch with OSDL, OSDL signs NDA and appoints a developer, which ensures the code will be accepted into the Linux kernel".

I have a dream...

"OSDL, Inc."

This is nothing but a history lesson. Now, who watches the History channel?

Greg, I thought the point of Open Source Development is the opposite of what you've suggested to the OSDL Board of Directors above. I thought that the point of Open Source Development is to happen everywhere, by anyone, by any means. I didn't know that soon enough this task would be reserved to the "17 of the top Linux kernel developers".

Is it worth to note the reason why Linux is where it is right now? Is it necessary to change how Linux has been developing up until now?