How does PSARC take input from non-project communities?

[Darren.Reed at sun.com]

While PSARC is looking over projects and ensuring that all
of the projects provide correctly architected solutions, how
does this play with communities that aren't related to the
architecture but would like to have some sort of voice in
how the final product works?

For example, if the system administration group manifests
itself into a proper community and then comes to OpenSolaris
with some input on direction that potentially conflicts with
the established direction, is there scope within the way in
which PSARC functions to respond to that?

Or to put it more simply, if the "userbase" doesn't like the
architecture PSARC is pushing, how does PSARC respond?
Does it require projects to act as a vehicle for that response?

The system administration community is a special case as
it is not one that is likely to own or be responsible for any
particular set of projects to use as a vehicle as the means
for interaction with PSARC.  Are there other communities
like this?  Possibly...

Or is the correct way to include communities such as this
in the process to ask various projects proffered by other
communities (such as SMF) to have the approval of the
system administration community before approaching
PSARC?  (as a further example.)

Darren