An RWS should have the option for more than one contact

[aselya]

Currently, the RWS implementation only allows for a single contact email. While the guidelines indicate that a group alias should be used if available, this is not currently being followed. This could cause issues if the email provided is no longer used or the contact provided is no longer associated with the organization behind the RWS.

I've thought of a few ways that we could change RWS to address the issue.

1. Allow an RWS to contain a list of contacts, similar to the list of associated sites.

{
    "contacts": [
         "group@example.com", 
         "email2@example.com",
         "email3@example.com"],
}

2. Allow an RWS to have a primary/organizational contact named and then an optional list of secondary contacts.

{
    "primary contact":"group@example.com",
    "secondary contacts": [
         "email2@example.com",
         "email3@example.com"],
}

3. Require an RWS to have an organization alias contact and a list of (at least one) individual contacts.

{
    "organization contact":"group@example.com",
    "secondary contacts": [
         "email2@example.com",
         "email3@example.com"],
}

[Vikidp]

group@example.com

[abo-L]

@aselya

[ghaforianmohamad45-bot]

1370 در تاریخ سه‌شنبه ۵ اوت ۲۰۲۵، ۴:۰۶ kaxhnet ***@***.***> نوشت:

…

*kaxhnet* left a comment (GoogleChrome/related-website-sets#472) <#472 (comment)> / — Reply to this email directly, view it on GitHub <#472 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BVJYHXNZNVOSPDRUTAQ2GN33L74BJAVCNFSM6AAAAAB63MEKJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNJSHA4DONJYGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>