| R |
| A |
| C |
| I |
Task Description
Extend community consultation frameworks and norms for New Readers work. Analyze and document what worked and didn't from this fiscal year, iterate on RACI, and develop plan for upcoming fiscal year.
Acceptance Criteria
Description
Description
Related Objects
Related Objects
- Duplicates Merged Here
- T190888: Revisit community consultation principles
Event Timeline
Comment Actions
(Re-adding New-Readers as I don't see why that was removed.)
@AMuigai: Could you please explain what/who exactly this task is stalled on ("If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on")? Thanks for clarification!
Comment Actions
@Aklapper The New Readers Program was closed and the work the program started was distributed among several teams. I changed it to "Stalled" as the initial writer of this task left the Foundation and it does not appear that it will be acted upon. For that reason, I removed the New Readers tag. I added my team's tag instead as this is something we need to think about, and could learn from what the New Readers program originally did. We can close this ticket, and I can create a new one for my team if that's better.
Comment Actions
@AMuigai: Whatever works best for you (and I highly appreciate that you go through New-Readers tickets!). I just want to avoid "stalled" tickets when nobody knows who or what exactly the ticket is stalled on, because that usually translates to "nobody looks at the ticket anymore because it looks blocked but is not".
Comment Actions
The ticket was in the context of New-Readers and New-Readers existed, hence New-Readers should stay on the ticket. :)
If noone will act on this ticket then its status should be set to "declined", I'd say.