New issue
Advanced search Search tips

Issue 699334 link

Starred by 1 user
Status: Fixed
Owner:
zhangtiff@chromium.org
Closed: Mar 2017
Cc:
seanmccullough@chromium.org
martiniss@chromium.org
zhangtiff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

Rebrand Sheriff-o-Matic for troopers

Project Member Reported by zhangtiff@chromium.org, Mar 8 2017 
I think it's a bit of a mental block for troopers to use Sheriff-o-Matic at the moment. It definitely feels weird to go to a tool for sheriffs when we're troopers. 

I think maybe we should come up with a different name for the trooper page on Sheriff-o-Matic to help with this... Trooper-o-Matic is taken unfortunately. Maybe even register a separate Appspot app and have it redirect/alias to the Sheriff-o-Matic trooper page. Or maybe a go link would suffice.

Comment 1 by seanmccullough@chromium.org, Mar 8 2017 

We used to have a separate trooper-o-matic appspot app (showed CQ time series stats IIRC), but no one used it. And even if it's just a redirect, having a separate appengine deployment is counter to our goal of reducing the Ops surface area.

The trooper rotation is small enough that we can probably fix this in docs, or as you suggest, a go/ link.

Comment 2 by zhangtiff@chromium.org, Mar 8 2017 

Yeah, probably best to stick with go links. I'm imagining changing the trooper page for just this one use case to have a different name and such. Though perhaps having different names to refer to the same thing would just make things more confusing anyways. I can change go/som-trooper to redirect to the trooper page.

Comment 3 by seanmccullough@chromium.org, Mar 8 2017 

SGTM. And point go/som-trooper-design at the design doc?

Comment 4 by zhangtiff@chromium.org, Mar 8 2017

Status: Fixed (was: Assigned)
Done and done! :)
►

Sign in to add a comment