Page MenuHomePhabricator

Create a notice panel on phabricator homepage
Closed, DeclinedPublic

Description

Currently we are having a ci outrage T137265 but as most of the admins are offline we carn't update the dashbored with a notice.

That's why I'm asking could we create a panel at https://phabricator.wikimedia.org/dashboard/view/1/ please with a notice panel.

Please give editing rights to ops and releng.

Users who are not subscribed to get emails are creating tasks like T137276 wondering why they carn't test.

Phabricator will be the most likely place for users to find information.

The current problem is some users have not subscribed to getting emails from wikitech-i which is where the email was sent so only users subscribed will have noticed. Where as on the other hand users who are not subscribed doint.

I'm proposing we either update the create task panel with a notice above or create a panel for notices. But as you said most doint view the homepage so create task panel seems a much better place to put the notice.

The text could say

CI outrage please follow T137265

in red please.

Event Timeline

Seems we should create a new project that we lock down to only users can add only users instead of freely allowing joining. But could the releng and ops team be added please.

If they don't read the relevant mailing lists, what makes you think they will read the front page of phabricator?

I got to it to create a new ticket. Is there a way to add a notice above the create ticket form without being able to edit the rest of the form?

Since they have to create a task like T137276 did.

I'm not convinced that many people 1) have the default Phabricator dashboard and 2) ever go to the very frontpage of Phabricator.

You'd also have to propose an actual text which is missing here.

Please give editing rights to ops and releng.

That does not make sense. Both projects don't have join restrictions, and I'm not going to look up >20 separate Phabricator user names to add them.

Please fix the task summary as it does not describe a problem that you'd like to solve but only a potential solution to an unknown problem. Please read #4 in https://www.mediawiki.org/wiki/How_to_report_a_bug#Reporting_a_new_bug_or_feature_request - thanks.

@Paladox: We can and I am not going to abuse the Maniphest task creation dialog for making random broadcast announcements. Please see my previous comment and read all points that I wrote.

I'm not convinced that many people 1) have the default Phabricator dashboard and 2) ever go to the very frontpage of Phabricator.

  1. How many people know about the possibility to create new custom dashboard, when there is no direct path to it from the basic one?
  2. Since there is no permanent menu, the only way how to get to the other part of Phabricator is go through main page.

Please provide measurable sources for your statements, thank you.

Regarding the 1st bullet point you might be right.
I don't get the 2nd bullet point. What "other part"?

In any case, I do not consider the Phabricator frontpage (or task creation page) a venue to announce short-term infrastructure outages.

@Danny_B I doint think many will know and you can view all dashbords at https://phabricator.wikimedia.org/dashboard/ which doint look like many users have custom dashbords.

But maybe upstream could add a sitenotice like we do with mediawiki.

Regarding the 1st bullet point you might be right.

The link provided by @Paladox in the comment above is quite self-speaking. And you can run simple query in database to find out.

I don't get the 2nd bullet point. What "other part"?

I.e. I am in Maniphest (eg. now in this task). The only way how to get to Diffusion is to go to the main page and click Diffusion in the left App menu.

@Danny_B I doint think many will know and you can view all dashbords at https://phabricator.wikimedia.org/dashboard/ which doint look like many users have custom dashbords.

I know, that's why I pointed it out... It was rather rhetorical question...

But maybe upstream could add a sitenotice like we do with mediawiki.

Feel free to open new task for that.

It wouldn't be that hard to include the last few lines from the RelEng and Operations SAL in a notice on the 'new task' form. That might prevent a few unnecessary tasks. Getting people to read before they submit might be futile though.