Doesn't sound like something you'd want to play with... 1kW is enough to kill or maim, 100kW is enough to explode and melt things significantly larger than a person. And I wouldn't expect OSHW to be nearly safe enough, or well enough engineered, to deal with it responsibly and safely (not to mention efficiently and cheaply).
OS is something that works well when there's little or no incremental cost or barrier to entry associated with the subject. Almost anyone can learn a programming language and sit down and write [bad] functions, or hopefully, rewrite someone else's drivel into something readable and good... So OSS works well. When it's big enough to be popular, also (like Firefox).
Droves of small OSS projects fester with poor development and support. Often times very useful, but narrow in purpose, low in visibility, and never drawing the attention and time of those who would serve it well.
And that's just software. Hardware these days is getting cheaper, but big hardware projects are largely unavailable to the average tinkerer:
1. You'll spend $100 just on surplus/eBay transistors for such a project, and without also having a comprehensive engineering background (whether formal or informal), you're guaranteed to be blowing those out on each. and. every. single. test. And it will take hundreds of those cycles before you learn your lessons (pass/fail is a very, very low information-yielding criterion..). And the rest of the hardware will run $2000 minimum, not to mention batteries (you can't run something like this off the AC line, not when the average household tops out at 30kW total for the whole drop), load (dyno??), motor, all the mechanical and electrical hardware, etc.
2. Development doesn't do much good unless every engineer working on the thing has a model to play with. (See also #1.) The development/prototyping cost increases arithmetically with the number of developers. That's insane.
3. There simply aren't very many engineers out there. And most of them are busy working, and don't much care to do more of it during their off hours. You'll still get a few hours here or there, but nothing focused. And lack of focus and involvement is an absolute killer in something as comprehensive as this.
And being that real engineering is in short supply... they probably won't be taken seriously by the overall group/direction/management, leading to more festering of the project, and even less interest from real engineers (why would anyone want to join a project where they won't be taken seriously?). Perhaps I'm overestimating the democratic hardships of OSHW projects, but I'm probably not wrong by direction, if by magnitude.
So in my opinion, I don't see OSHW being any more than a pipe dream for a product like this.
How can you get real engineers interested? Draw up a comprehensive project plan, get it planned out by real engineers and managers. Then get those steps executed. Again, at least under the direction of real engineers, but preferably using real engineers to draw up the plans, do the layouts, you know. You'll most likely need money along the way. Kickstart it, or something? That leaves it up to the donators: if it's simply not popular or vital or attractive enough, then obviously, no one wants it anyway, and that's as good a vote against going ahead as anything, regardless of how you feel about it. If it does succeed, then soon enough (assuming it's well enough managed), it'll actually succeed.
But doing it by amateur hours, whenever, no, this simply isn't an Arduino weekend project. There's almost no way to go from "here" to "there", when it's something this big.
Tim