New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 916837 link

Starred by 0 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Implement a PSA channel for all LUCI users

Project Member Reported by no...@chromium.org, Dec 20

Issue description

Now that LUCI is actively used outside of chromium, a PSA to chromium-dev is not enough, because e.g. Fuchsia devs might not see it.

We need to a PSA channel that
1) targets all LUCI users
2) can be used to share data publicly (outside of @google.com)

Context: go/chops-pm-110

efoo, may I ask your help with this?
 
however, maybe sending two emails (chromium-dev@chromium.org and chops-outages@google.com) might be sufficient. 
Cc: estaab@chromium.org
Actually Dirk and Eric mostly focused on chrome whereas chrome is the only LUCI user that doesn’t have problem.

Also chops-outages isn’t aligned with target audience (all LUCI users). Perhaps such PSAs should be sent to luci-announce
Actually luci-announce isn’t aligned either. Users aren’t interested in various non-outage infra PSAs
Maybe just luci-outages@google.com with chops-outages@ and other relevant team escalation lists as members?
Cc: nmulcahey@google.com athom@google.com
Nathan, Alexander, would luci-outages@ work for you?
Yes, luci-outages would work for us. I would add dart-engprod to that group for now.
SGTM. Let's limit it to fuchsia-build-notify@ on Fuchsia.
the mailing list is created, but i have trouble setting up forwarding from luci-outages to other MLs...
Owner: no...@chromium.org
Status: Started (was: Available)
Status: Fixed (was: Started)
https://groups.google.com/a/google.com/forum/#!topic/luci-outages/mGe6IicGBiU
got propagated to all the needed MLs

Sign in to add a comment