How does PSARC take input from non-project communities?

[Garrett D'Amore]

John Plocher wrote:
> Rainer Heilke wrote:
>> John Plocher wrote:
>>>  The ARC is all about "us" reviewing
>>> "our" projects, and not "our" projects being beat up by "them" :-)
>>>   
>> Having said that, though, as Darren has pointed out earlier the 
>> sysadmin group hopes to influence other development groups ...
>>
>> Again, thank you both for this continued discussion and the resulting 
>> clarifications.
>
> There are several non-exclusive things that a group like sysadmin
> can do, each having its own set of pros and cons:
>
> o They can have their people become active members of the ARC,
>   where they read, mentor and review each project as it goes thru,
>
> o They can have their people be passive subscribers to the ARC
>   discussions, jumping in with comments and suggestions as desired,
>
> o They can, independent of the ARC, follow the creation of projects
>   and ARC cases, choose which ones to get involved with, and devote
>   time and resources making sure that those projects/cases do the
>   right thing,
>
> o They can develop a "policy document" that sets out the architectural
>   boundaries, requirements, etc that are relevant to the group, and
>   bring it to the ARC as a candidate to become an ARC policy which the
>   ARC will then expect future projects to honor,
>
> o ... etc ...
>
> Today, you can do all but the first bullet.  You can even get involved
> with the effort to make that first bullet an option (via the arc-discuss
> ARC community alias).

Why couldn't they do that today?  I thought pretty much anyone could 
request to be an ARC member (maybe only from engineering?)  I know that 
I was an ARC intern even when not a Sun employee.

The only problem right now, is that (for PSARC at least) the ARC process 
requires SWAN access.  But if there are member(s) of the sysadmin 
community on SWAN, then I don't see why they couldn't request to join 
ARC as an Intern.  (If there aren't any such members, why not?)

Now, full ARC membership is a different process, and I think it requires 
a vote of the other ARC members.  ARC membership is fairly technical, 
and probably requires an engineering background, but again, why can't be 
(if there aren't already) engineers who are also members of the sysadmin 
community?

    -- Garrett
>
>   -John