Casper.Dik at Sun.COM writes: > > >I agree, but if we can have open ARC reviews of closed source that would > >help: the source might always be opened later, presenting OpenSolaris > >with a fait accompli. > > For one, closed source can export public APIs and the Open ARCs may want > to have something to tell about them.
The APIs are just the tip of the iceberg. Effectively reviewing the open portions that share (depend on, supply, use) those APIs very often means understanding a bit about how the closed part works. It's not as clean a process as simply saying "this part is closed source, so use closed ARC; this part is open, so use open ARC." It'd be nice if it were that simple, and perhaps it is in some restricted cases (particularly where the closed source just implements some standards-defined bit of functionality). There are many other cases (such as, say, LDOMS) where understanding the details of the open parts necessarily depends on having a broader view. That's where we're shoving people into a corner. As I said before, there are multiple possible schemes you can use, but all of them have faults. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
