James Carlson wrote:
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.
Absolutely, given time constraints of all parties involved.
I don't think any such consultation is tantamount to approval.
...
That's the comment I was looking for. In the way I read what meem
said, it suggested to me that perhaps this consultation was like
getting approval. Maybe he didn't mean it to be read that way but
the comment did raise my eyebrow.
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..
...
No, that's not the case at all, far from it.
I'm more afraid that someone could spend too much time getting
consultation without ARC'ing and then go to the ARC and still end
up with a large bunch of design issues. Whenever I hear people
say they are afraid of ARCs, I hear Gary's voice in my head saying
"ARC early and ARC often". Although I don't think he means often
as in weekly/monthly, I can see the benefit in "early".
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
