Garrett D'Amore wrote: > John Plocher wrote: >> Garrett D'Amore wrote: >> >> Rather than complaining, we should be actively figuring out how to solve >> this problem: >> >> We want to be able to build the thousands and thousands of >> FOSS components out there and make them available to our users. >> How can we make this happen? > > Yes! I want to figure out a solution to make everyone happy. I'd > really really like to do this quickly, so that cases like unison, > star, and even unzoo, have a way to deliver bits to customer, without > having to achieve unreasonable bars set for "core" components, and > without risk of degrading the overall quality of a (as yet > undetermined) "core" product. > > IMO, what we really need is a Sun-supported version of "blastwave", > with "caveat emptor" plastered over its contents. I had believed that > this was what IPS was supposed to bring us. But unfortunately (IMO), > we have projects like the aforementioned which seem determined to > deliver into the WOS asap, without waiting for what might perhaps be a > better and simpler IPS-based approach. (And of course, I don't recall > any ARC cases covering IPS itself yet... so ARC can hardly ask these > FOSS projects to use it!) > > -- Garrett And why is the ARC the locus of this?
You guys have a great project in mind. Get your managers to fund you to begin the initial investigations. Remember, the ARCs review projects, not create them. Of course, the ARCs have found a loophole (little used). You could burden all proposed FOSS integrations with a dependency on this phantom project. Or, you could assert that Comay's project is really this project and force it to morph dramatically. Or, you could just file a 1/2 pager... :-) - jek3
