action #177895
closedCome up with ideas to make moderation more fun and more accessible instead of a hard-coded list of moderators size:S
0%
Description
Motivation¶
@mkittler removed himself from the moderation list in https://progress.opensuse.org/projects/qa/wiki/Tools/525/diff meaning if @livdywan and @okurz are not available there will be guaranteed awkward silence. What should we do?
- AC1: One or multiple of the suggestions have been discussed and implemented or are reflected in follow-up tickets
Suggestions¶
- Consider the "weekly moderation duty" we had
- Rotate the list of moderators by priority explicitly (rather than asking)
- Clarify how the duty works. Maybe that was not clear in the first place
- Make the list a specific "fallback" list
- Mention the current priority in the Slack topic (otherwise nobody will remember)
- Lead a conversation on Slack or a call to find out how people feel about moderation in general
- Ask what prompted the change of mind
- Clarify if the list of moderators stops others from taking over
- Collect moderation points. Once you achieve 10 points you win a "next" ticket
- @okurz suggests to consider that some people like moderation more, some less
- Practice moderation to make it easier
- Remember to give people feedback so they can learn
- Add something to the docs, like key phrases to use or best practice e.g. letting others speak first
Updated by tinita about 2 months ago
- Subject changed from weekly moderation duty - version 2025 to Come up with ideas to make moderation more fun and more accessible instead of a hard-coded list of moderators
- Description updated (diff)
Updated by livdywan about 2 months ago
- Tags changed from reactive work, organisational to reactive work, organisational, retro
- Status changed from New to Workable
- Assignee set to livdywan
This also came up in the retro again. There seems to be some consensus that we had a lot of meta discussion at this point and it's time to try out some of those ideas.
Updated by tinita about 1 month ago
- Subject changed from Come up with ideas to make moderation more fun and more accessible instead of a hard-coded list of moderators to Come up with ideas to make moderation more fun and more accessible instead of a hard-coded list of moderators size:S
- Description updated (diff)
Updated by livdywan 14 days ago
- Status changed from In Progress to Feedback
- Consider the "weekly moderation duty" we had
- Rotate the list of moderators by priority explicitly (rather than asking)
- Clarify how the duty works. Maybe that was not clear in the first place
- Make the list a specific "fallback" list
- Mention the current priority in the Slack topic (otherwise nobody will remember)
I updated the wiki (diff) in an attempt to highlight key points and make it easier to follow, much like alert duty.
Also dropping the checking of availability of people who didn't participate in the call. This is specific to the daily calls and makes moderation duty more complex. For alert duty we don't require resolving alerts either.
- Lead a conversation on Slack or a call to find out how people feel about moderation in general
https://suse.slack.com/archives/C02AJ1E568M/p1744141724738839
Updated by livdywan 13 days ago
I added a couple points with regard to estimations:
- Consider going by priority and status i.e. start with immediate/urgent/high and otherwise feedback/progress
- If a ticket is in feedback, check if it needs more discussion or can be resolved
Updated by livdywan 12 days ago
- Due date set to 2025-04-14
- Make the list a specific "fallback" list
- Mention the current priority in the Slack topic (otherwise nobody will remember)
Tina reminded me in the daily to clarify this point. I was also looking to discuss it a little more on a call but maybe we have enough topics going this week 🙃
My idea really was for the person on moderation duty to lead calls, or ask if somebody else does. For example, let's estimate tickets, who is reading tickets, who is saving tickets, and optionally taking an active role themselves
So for the purposes of AC1 I'd like to confirm who would be happy to moderate calls, and if the advice we have in the wiki now and how we conduct calls is giving people the confidence to lead a call.
Or maybe it is worth considering a different scope. Maybe somebody feels more comfortable moderating infra calls for example, or collaborative sessions?
Will bring it up early on Monday, and then decide if there is interest either direction or if we should leave it for the moment.
Updated by livdywan 8 days ago
- Due date changed from 2025-04-14 to 2025-04-18
livdywan wrote in #note-10:
- Make the list a specific "fallback" list
- Mention the current priority in the Slack topic (otherwise nobody will remember)
Tina reminded me in the daily to clarify this point. I was also looking to discuss it a little more on a call but maybe we have enough topics going this week 🙃
My idea really was for the person on moderation duty to lead calls, or ask if somebody else does. For example, let's estimate tickets, who is reading tickets, who is saving tickets, and optionally taking an active role themselvesSo for the purposes of AC1 I'd like to confirm who would be happy to moderate calls, and if the advice we have in the wiki now and how we conduct calls is giving people the confidence to lead a call.
Or maybe it is worth considering a different scope. Maybe somebody feels more comfortable moderating infra calls for example, or collaborative sessions?
Will bring it up early on Monday, and then decide if there is interest either direction or if we should leave it for the moment.
Got some positive feedback 🥰 Didn't follow up as of yet due to other issues coming up in the day. Will bring it up in the next few days.
Updated by livdywan 8 days ago · Edited
- Status changed from Feedback to Resolved
Will bring it up early on Monday, and then decide if there is interest either direction or if we should leave it for the moment.
@gpathak, @gpuliti, @mkittler, @emiler and @robert.richardson agreed to be fallback moderators rotated on a weekly basis. I added according remarks in the wiki.