Darren Reed writes: > >We will. That said, one of our team members is on PSARC, and other PSARC > >members (such as Jim Carlson) have already been active in providing > >feedback. > > > > This comment disturbs me as it implies that by having someone from > the ARC as part of your team and providing feedback outside of the > ARC environment that there is some implicit approval here.
What? I can't quite tell what you're saying. > Whilst having such people on your team can help guide to a better > design, I can't imagine that it can be held up in place of review > by an ARC. > > Is the implication here that all Solaris projects should have a PSARC > member as a part of their team so that they can cut down on requirements > in dealing with the ARC? > > Jim, would you like to comment here, with your PSARC hat on? With my ARC hat on, I think it's great when project teams choose to consult with particular ARC members or interns whom they feel might have relevant experience. It's not completely fool-proof, but it does tend to reduce the chance for surprises later. More generally, I think it's a good idea to get folks involved in a project any time you think they might be able to provide useful feedback. I don't think any such consultation is tantamount to approval. I can't predict (nor would I ever attempt to) how the other ARC members might view any particular proposal. The ARC isn't some ivory tower; it's just a review body made up of independent engineers. And I think we all know how widely divergent individual engineers can be when asked for an opinion. If you've got a specific complaint that someone isn't following the development process properly, or that there's some sort of improper behavior going on, please take that up with management rather than with any mailing list, open or otherwise. I seriously doubt that meem or any of the other Clearview team members would do as you suggest -- holding up team composition "in place of review by an ARC" -- but if you do, I don't think this is really the right way to solve the problem. -- James Carlson, KISS Network <[EMAIL PROTECTED]> 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 _______________________________________________ networking-discuss mailing list [email protected]
