Add support to TBPL for sheriffs.mozilla.org (if we start using a set sheriff schedule)

RESOLVED WONTFIX

Status

Tree Management Graveyard
TBPL
RESOLVED WONTFIX
7 years ago
3 years ago

People

(Reporter: philor, Unassigned)

Tracking

Details

(Reporter)

Description

7 years ago
A nit-picker would point out that since https://sheriffs.mozilla.org/ doesn't have any actual users or any schedule, it would seem premature to switch to it.

In fact, it isn't. The Google calendar has been abandoned for months, so it's a rotation of people who are no longer with MoCo, people who are no longer with the project, people who haven't actually done anything when they are sheriff for years, and a few people who are still around and might sheriff, except they don't even remember when they are scheduled, and the poor bastards who are scheduled on a Monday, and are now reported by the calendar as being sheriff on Saturday, Sunday, and Monday.

When https://sheriffs.mozilla.org/api/v1/today/?format=json says the sheriff is ""objects": []", it is the most accurate and current and forward-looking information we can present, since the calendar will never again be touched or followed, but someday in the foreseeable future sheriffs.m.o will give us an actual object with an actual user. We might as well start looking forward to it now.
Blocks: 764801

Comment 1

6 years ago
ewong just asked me about this on IRC.

I guess we could switch early, but it seems a bit wasteful to continually ping the site when we don't know if it will be used for months (long list of things we need to change [ask if you want the excerpts from emails], but wasn't deemed the most critical sheriff related a-team goal, so punted for now). 

Instead, we should either:

a) Strip out the sheriff duty line completely. Any removed code will still be retrievable from the repo, so no harm in just removing functionality for now.

or

b) Have it point to https://wiki.mozilla.org/Tree_Rules/Inbound#Meet_the_Sheriffs for inbound, but leave blank (or put "self-sheriffing" / something to remind them that they should be starring their own stuff) for the rest.

CCing a few sheriffs to find their preference.

Would be good to find out if we can get rid of the buildduty field at the same time & remove the external https://www.google.com/jsapi dependency.
or

c) Point it to #developers (like the Thunderbird ones currently point to #maildev)

There's code for this already, although you could implement b) using that code as well.

(In reply to Ed Morley [:edmorley] from comment #1)
> Would be good to find out if we can get rid of the buildduty field at the
> same time & remove the external https://www.google.com/jsapi dependency.

AFAIK this is still used, as I'm pretty sure that's up to date most of the time I look at it.

Updated

6 years ago
No longer blocks: 764801

Comment 3

6 years ago
Bug 822596 is removing Google calendar integration.

Morphing this bug to be about adding sheriffs.mozilla.org integration, should we at some point in the future decide that a set sheriffs schedule is going to actually be used.
Summary: Use sheriffs.mozilla.org instead of the Google calendar to get the sheriff's name → Add support to TBPL for sheriffs.mozilla.org (if we start using a set sheriff schedule)

Comment 4

5 years ago
WONTFIX given bug 907190.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
(Assignee)

Updated

4 years ago
Product: Webtools → Tree Management
(Assignee)

Updated

3 years ago
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.