[META] CWG - Community Health team - "Nudge" templates

Created on 21 April 2020, about 5 years ago
Updated 1 May 2025, 16 days ago

CWG - Community Health team - "Nudge" templates for Slack and Drupal.org issue queues

For more information and background: Encouraging healthy conversations in the Drupal community โ†’

The Community Health team is seeking feedback on the language of each of the nudges. Please comment in the individual issues.

TODO:
With each nudge include a link to the appropriate Drupal Value and Principle

  1. Completed:
  2. Define templates and solidify words
  3. Technical Implementation

Currently, we are having weekly, 30 minute meetings for this project using Google Hangout on Mondays at 1530UTC. If you'd like to attend, please contact drupal-cwg at drupal.org

๐Ÿ“Œ Task
Status

Active

Component

Initiatives

Created by

๐Ÿ‡บ๐Ÿ‡ธUnited States volkswagenchick San Francisco Bay Area

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States cmlara

    Has any post nudge surveying been done? I see there is an open issue for logging of nudges however it appears to never been moved forward.

    Would suggest data from those directly involved in the thread, and those who are observing the thread would be useful.

    Some questions that come across my mind:

    Do they actually defuse the situation or do they raise tensions in the threads?
    Does anyone feel that a CWG Nudge was used too soon in a discussion?
    Are contributors more aggressive out of concern a nudge will be given on a sensitive topic shutting down discussion before a point can be made?
    Are nudges used by 'less experienced' developers or only used by 'well established public figures' of the Drupal Community? (Are they being used to shut-down discussion creating a non-collaborative environment.)

    I'm sure others would have suggestions for questions that could be considered in a post incident survey (say 7 days after a nudge is delivered)

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States markie Albuquerque, NM

    Hi there,

    Thank you for reaching out.

    The Community Working Group's main goal is to make sure the Drupal Community is a welcoming and nurturing community. Though open for use by all, the Community Working Group most commonly posts nudges, and then it is after an incident report is sent and/or when the topic has become escalated or off topic. We use the nudges in hopes of preventing more intrusive interventions by the Conflict Resolution Team.

    After talking with the team, we are curious about the โ€œopen issue for logging of nudges.โ€ Can you provide a link?

    To answer some of your questions:

    • Do they actually defuse the situation, or do they raise tensions in the threads?
      • They intend to call out the negative behavior, as we know that, in the moment, the authors may not recognize what the community sees. We have not seen an incident where it raises tensions. It will generally defuse the situation. The only negative effect we have witnessed is that the thread goes silent.
    • Does anyone feel that a CWG Nudge was used too soon in a discussion?
      • We have not noticed this. Again, usually we consider a nudge after an incident report or if weโ€™ve noticed a particular rise in tensions. Assuming the nudge is applicable and can be applied.
    • Are contributors more aggressive out of concern a nudge will be given on a sensitive topic shutting down discussion before a point can be made?
      • The nudges are focused on bringing the conversation back on topic. Usually, the issue/thread has gone from discussing an issue to personal attacks or other escalating topics.
    • Are nudges used by 'less experienced' developers or only used by 'well-established public figures' of the Drupal Community? (Are they being used to shut down discussion, creating a non-collaborative environment?)
      • The nudges are commonly used by the CWG, however, they are available to all. Everyone in the community is welcome and encouraged to use them and contribute in the spirit of our open-source community. We are all here to mentor and collaborate and not call out experience level or notoriety as proxies for โ€˜being right' or 'wrongโ€™.

    We are happy to hop on a call with you and discuss this and other issues/threads where nudges were applied.

    Posted on behalf of the CWG

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States cmlara

    After talking with the team, we are curious about the โ€œopen issue for logging of nudges.โ€ Can you provide a link

    #3177770: Nudge reporting(?) โ†’ which already attached as a related issue.

    My suggestion would be without doing a proper post incident analysis of everyone involved (those warned, those requesting the warning, and those who only observed the warning) the CWG is missing out to understand if the nudges are actually having a positive effect.

    I only observe a fraction of the nudges, its possible a majority of the time they have a positive outcome, however without doing proper, data collection an analysis none of us truly know if these should continue in public, moved private, or just be discontinued.

    Anecdotal observations:
    I've seen a number of incidents where it does inflame the tensions, perhaps not in the thread itself, however every other thread after that will remember the incident. Humans hold grudges and those grudges will make every single discussion after that more tense.

    Worse than that, I recall an issue having been silent for an extended period of time when a nudge was posted, this added 'fuel to the fire' of an issue that was otherwise no longer being discussed. Had the nudge never been sent the issue would of likely been forgotten, with the nudge it was remembered much longer and not in a positive view (refer to humans hold grudges).

    ๐Ÿ“Œ Bulk LLM-generated module publishing by bigbabert Active may be an example of a 'too soon' nudge, and the chilling effect it may have. Never under estimate the damage of "the thread goes silent". I have observed too many times in my life where continuously internalizing problems has disrupted projects.

  • ๐Ÿ‡ฎ๐Ÿ‡นItaly bigbabert Milano, Italy

    Hi everyone,
    I'd like to respectfully ask for some clarification about how incident reports and moderation actions are typically handled within the community.

    Who is responsible for reviewing these reports, and how frequently does this happen?

    Are reports submitted by technically experienced or well-known community members considered with more weight?

    In this specific case, I noticed that a report about my actions was mentioned directly here in the issue. I was under the impression that the official process โ€” as described on drupal.org โ€” involves submitting a documented report via email and waiting for a response or action. Could you help me understand why this alternative approach was taken?

    For transparency: I had posted a link to a module on Slack, and as soon as I was told it wasnโ€™t appropriate for the channel, I removed it immediately. My intent was never to cause disruption or break any guidelines.
    Since this is volunteer work that I do in my free time for the benefit of the community, I simply shared a post in a community channel to get feedback โ€” and it was from that discussion that others decided to escalate the matter and open this issue.

    I may or may not appreciate seeing my name mentioned in the issue reported by @cmlara ( ๐Ÿ“Œ Bulk LLM-generated module publishing by bigbabert Active ), but I believe it would have been more respectful to contact me first to clarify my intentions and actions.

    Iโ€™m raising these points not to contest anything, but because I genuinely believe in a community culture based on fairness, clarity, and mutual respect. I remain open to feedback and committed to improving based on shared expectations.

    Thanks for your time and for all the effort put into maintaining a healthy and supportive community.

    Best regards
    Alberto

Production build 0.71.5 2024