Making WordPress.org

Changes between Version 1 and Version 2 of Ticket #5093, comment 16


Ignore:
Timestamp:
03/17/2020 11:36:51 AM (5 years ago)
Author:
jonoaldersonwp
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5093, comment 16

    v1 v2  
    33If solving that impacts the resources/processes of our volunteers, then we need to change those resources/processes. We can't just immediately shut down any discussion of improvements which impact/alter our resourcing (volunteers/moderators or otherwise/beyond) as a dead-end, unless we've actively decided that WordPress' reputation and market share doesn't matter to (all of) us - which as far as I know, isn't the case. Instead, we need to find a way in which the needs can be met, within the constraints (or, to alter the constraints).
    44
     5Furthermore, a partial fix is better than no fix at all. Maintaining the status quo isn't an option when it's harming users.
     6
    57So... Let's try to be a bit more open and productive around how we explore this, maybe? If volunteer resourcing is the issue, then let's not conflate that with the utility or viability of the proposal, and let's work collaboratively to find a compromise. I think that, perhaps, we're all over-reacting on the amount of additional resource required to police this. We already police it, and, it's evidently a drain.
    68
    7 What if we just gave the moderators the tool to remove the link, as a test? Then nobody's doing any more / different work than at present, but we create some more happy, positive interactions, rather than making enemies of the community? If nobody dies, then we circle back around, regroup with some learnings and insight, and discuss next steps.r
     9What if we just gave the moderators the tool to remove the link, as a test? Then nobody's doing any more / different work than at present, but we create some more happy, positive interactions, rather than making enemies of the community? If nobody dies, then we circle back around, regroup with some learnings and insight, and discuss next steps.