Problem/Motivation

I presented a session in Vienna (https://youtu.be/Vjwoa0SvVSY?si=rU-SYcOl1PuBxM8p) proposing a 'Code of Care' to enhance the support frameworks in place for community members. I will be presenting a follow-up to that session in Chicago and want to gather as much feedback as possible to establish:

  • Is this the right direction/ initiative
  • What would be in scope for a code of care
  • The key components of a code of care

Request for Input

I would love to get as much feedback as possible on my session at Vienna, thoughts on the idea of a code of care and input on what it should include. Please comment on the issue, or if you prefer, you can contact me privately on Slack (Zoocha Will).

Thank you :)

Issue fork drupal_cwg-3559925

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

  • main Comparecompare
About issue forks

Comments

zoocha will created an issue. See original summary.

zoocha will’s picture

zoocha will commented
Issue summary: View changes

adpocalyptic made their first commit to this issue’s fork.

volkswagenchick’s picture

volkswagenchick
she/her
Primary language English
Location San Francisco Bay Area
commented

Hi Will!!

Just saw this issue. Will post the link in the CWG channel for visibility.

andypost’s picture

andypost
he/him
Primary language Russian
commented

Would be great if someone can sum up the session details into summary as everyone can get it different way

zoocha will’s picture

zoocha will commented
Issue summary: View changes
zoocha will’s picture

zoocha will commented

Thanks for the feedback so far - I have added more detail in the description to enable easier feedback without needing to watch the Vienna session.

My aim for Chicago is to present a more fully drafted proposed code of care, so please do feedback either here or privately via slack :)

rachel_norfolk’s picture

rachel_norfolk
Primary language English
Location UK
commented

Tagging myself in this as a way to remind myself to take a closer look.

I probably need to renew my Mental Health First Aid qualification soon, too.

zoocha will’s picture

zoocha will commented
Issue summary: View changes
adamb’s picture

adamb commented

This is great Will.
Clearly developed and moved on from the session you presented in Vienna, where we exchanged some thoughts in the Q&A.

mxr576’s picture

mxr576
Primary language Hungarian
Location Hungary
commented
Issue summary: View changes
Related issues: +#3487509: Rethink weighing of contrib projects and credits

I also had a BoF with related content at Vienna: https://events.drupal.org/vienna2025/session/contrib-care-program-buildi....

This is the recap that I have shared inside Pronovix after Vienna:

At DrupalCon Vienna 2025, I hosted a 'Birds of a Feather' (BoF) session titled, "Contrib care program: Building a sustainable future for Drupal's essential modules".

This topic isn't just academic for me; it was born from the real challenges we face with essential modules like Webform and SimpleSAML PHP, highlighting the risks of maintainer burnout and uncertain project futures.

While I originally aimed for an informal discussion, I wanted to ground it in data. In preparation, I extended my Drupal Dependency Quality Gate tool to scan and report on how many modules and themes have stable releases with the latest Drupal 10/11 core from the entire contrib ecosystem.

I was thrilled that over 10 people showed up, including Gábor Hojtsi (@gábor-hojtsy), for a very active conversation. A major highlight was having Kristiaan Van den Eynde (@kristiaanvandeneynde, maintainer of the 'Group' module) join us online.

We dove into several critical challenges:

  • The immense pressure on maintainers of modules included in initiatives like Drupal CMS.
  • The lack of precise data to identify which modules are most critical to the ecosystem.
  • The difficulty in finding viable funding models for ongoing maintenance.

Kristiaan provided a powerful insight regarding the current reward structure: despite the Group module's immense financial impact on enterprise projects, contributions to it often yield fewer issue credits than simple fixes to smaller modules included in the 'Drupal CMS' initiative.

The discussion also uncovered that we aren't the first to face this; I learned about a previous unknown attempt to improve ecosystem sustainability which provide important context.

We didn't solve this complex problem in one hour, but we all agreed on the importance of community action, from contributing time to convincing clients to allocate budgets for the open-source tools they depend on.

sikofitt’s picture

sikofitt
he/him
commented

@zoocha-will I was at your session in Chicago. Let me know what help I can provide. I think having some type of Drupal Code of Care would be extremely beneficial for the community.