Making WordPress.org

Opened 4 weeks ago

Last modified 4 weeks ago

#8004 new feature request

Allow a `/here` notice to be scheduled in Slack

Reported by: desrosj's profile desrosj Owned by:
Milestone: Priority: normal
Component: Communication (Matrix, Slack, IRC) Keywords:
Cc:

Description

We proclaim that anyone can run a bug scrub or organize a component meeting, but that's not entirely accurate because @here pings are managed by a custom script that require the person to be on an allow list.

Receiving the ability to announce requires a contributor to show a track record of reliability and dependability. This standard is applied pretty liberally, but adding someone to the list relies on a Meta commit. Not having the ability to ping the room can limit the effectiveness of a given scrub or meeting. The contributor will have to ask around and hope that someone with @here capabilities will be around at the same time.

It would be great if there were a checkbox on meetings entered into .org to send a @here ping when the meeting is supposed to start. This would not only solve the issue where someone without announce privileges is running the meeting. But is also helpful for situations where those running the meeting loses track of time, and prevents misunderstandings caused by timezone or Day Light Savings Time changes.

Attachments (2)

Screenshot 2025-06-12 at 9.42.55 am.png (175.3 KB) - added by dd32 4 weeks ago.
Screenshot 2025-06-12 at 12.05.07 pm.png (78.6 KB) - added by dd32 4 weeks ago.

Download all attachments as: .zip

Change History (7)

This ticket was mentioned in Slack in #core by desrosj. View the logs.


4 weeks ago

#2 follow-up: @dd32
4 weeks ago

When I saw the title, I thought "Adding scheduling to the /here command is going to be challenging.." but when I read the ticket, adding an automated slack ping based on meeting schedules is totally achievable.

Would a UI similar to the above fulfil the needs?

Would customisability of the message be needed? What about the time? (I'm thinking scheduling it for 20 seconds prior to the specified time, to allow for unexpected cron lag)

#3 in reply to: ↑ 2 @desrosj
4 weeks ago

Replying to dd32:

Would a UI similar to the above fulfil the needs?

I think the UI above would be adequate. I don't think we need to allow the time or message to be modified. Something like @here <meeting> POST_TITLE should be fine. The person running the meeting can always add more context after the bot's message opens the meeting.

I also think it's fine for the message to be set for :00 (no need for a 20 second head start). It's perfectly fine to be 20 seconds late. Better to be posted a few seconds late but during the expected minute than a minute early to avoid any confusion.

I'm curious what the Link field above is used for. Could someone put a link to the meeting's agenda? If so, perhaps including that in the message could make sense. But only if there's no other purpose.

#4 @dd32
4 weeks ago

I don't think we need to allow the time or message to be modified.

Great!

@here <meeting> POST_TITLE

Easy enough, and true, additional information can be added in context in the channel. The announcement will often form part of mobile notifications, so that's probably better to be short and clear than customised output.

I also think it's fine for the message to be set for :00 (no need for a 20 second head start).

Fair enough, I was thinking it's better to be a few seconds early than have it appear a few seconds late :) Maybe just scheduling it to be a few seconds early and then sleep() until the correct time would remove any doubt.

I'm curious what the Link field above is used for. Could someone put a link to the meeting's agenda? If so, perhaps including that in the message could make sense. But only if there's no other purpose.

I had to go digging, it looks like the Link is not used much, but is often either a) A link to the slack channel b) A link to a tag archive on the make site. See the above image for where that field is used in the UI.

#5 @chaion07
4 weeks ago

I would love for this to happen. This can make the whole process so much better and accessible for hundreds of contributors out there who might find the '/here call' a blocker to success. Thank you for working on this.

Note: See TracTickets for help on using tickets.