Alan Coopersmith wrote:
> Is there any reason beyond "that's the way it's always been" to create
> separate sub-aliases to be used as membership 
> rosters/member-class-designators
> instead of just keeping the roster on a web page?

It would be much much better if there were a supported structured way to 
keep such a set of lists; if it existed, we would simply have the email 
system use it in the course of sending email, and the web pages could 
automatically include the list on the leaders page.

I am making this proposal because such a structured mechanism does not 
exist and parsing an html page is not a viable option.  I would be happy 
if the result of this discussion was that the OS.o web app was extended 
to provide such a mechanism.

We could redefine the ARC community to be the Review Body itself, 
instead of a community that is focused on the care and feeding of the 
ARC process.  This would let us try and correlate the community roles 
with the ARC ones:

        Community Leader        = ARC web support
        Core Community Member   = ARC member
        Community Member        = ARC Intern
        ??                      = ARC Licensee
        Observer                = ARC Interest
        Community Announcements = ARC Agenda Interest
        ??                      = ARC Agenda Request Mechanism

This begs the questions of if/when the opensolaris web/email software 
will support these roles, and if/when the web observer feature will ever 
be integrated into the email system.


> If it's not ever going to get mail, why have it be a mailing list?

These roster lists will get email, just not directly from users.  If 
they _were_ used directly, we would be splitting the community into 
silos, something we don't really want to do.  Members would see one 
email stream, interns another, and interested observers a third.  No thanks!

The intent is to have one set of public email aliases that everyone uses:

     opensolaris-arc@           General case discussions
     opensolaris-arc-discuss@   Non-case focused discussions
     opensolaris-arc-record@    Archival without discussion

                These three could be combined - they are
                in the proposal because that was "how we
                always did it".

     opensolaris-arc-agenda-request@

     (I still need to add a few more workflow support aliases (not
     this project...) like opensolaris-arc-onepager-submission@ and
     opensolaris-arc-fasttrack-submission@)

   -John








Reply via email to