Sorry about the delayed response. Between a vacation day on Monday, a miserable Tuesday where pretty much nothing worked right, and JavaOne yesterday, I'm still catching up on email.
>>>>> "jek3" == Joseph Kowalski <jek3 at sun.com> writes: jek3> One concept discussed was to have a machine farm under OpenSolaris jek3> auspicies. Probably not as simple as it sounds (to prevent jek3> abuse), but certainly possible. Well, we need a build farm anyway, so that external committers can build and test on both x86 and SPARC prior to putback. But my point (which admittedly wasn't made clearly) was that you seem to be asking upstream maintainers to expand their test matrix and take on additional administrative tasks. If they're willing to do it, that's great for OpenSolaris. And the advantage to upstream is that it gives their code wider reach. But it is still more work for them, and I expect that a very common reaction will be "if you give us OpenSolaris packages, we'll post them; if you give us Solaris-specific patches, we'll look at incorporating them." I think a more successful strategy will be for OpenSolaris community members to get involved with the upstream projects that they care about. They can test development builds and produce packages. Which may have been what you had in mind in the first place, and I just didn't understand what you meant by pushing things upstream. mike
