04 May 2026
Drupal.org aggregator
Community Working Group posts: Before the Incident Report: How We Are Collaborative
At DrupalCon Chicago, the Driesnote included a visualization with "community" as one of the three pillars of Drupal, along with "platform" and "agencies." That framing felt memorable, and worth exploring further.
If you attended DrupalCon Chicago, you might have experienced a slightly differently shaped triangle. I don't know the attendance numbers, but I saw technical sessions with packed rooms, while community-focused sessions had plenty of empty seats. That's not new. It's been true for years. People care about community, but when the schedule forces a choice between a session on AI integration and one on community health, most folks choose the technical session. I understand why. Technical work feels concrete. Community work is generally not why employers send folks to a DrupalCon.
This raises a question: how can all of us work together to close that gap without having to attend community sessions at DrupalCon?
Consulting our Code of Conduct
I serve on the Community Working Group (CWG), specifically on the Community Health Team. A lot of people don't know there are two teams inside the CWG, so here's the short version:
- The Conflict Resolution Team handles incidents after they happen. If you file an incident report, they're the ones who review it.
- The Community Health Team works on everything that happens before an incident report, such as workshops, resources, and other preventive work. Our goal is to help the community build the kind of culture where fewer situations reach the reporting stage in the first place.
Both teams matter. And beyond the CWG, the DrupalCon Code of Conduct offers advice for all of us. It includes a section titled "We are collaborative," which says:
If and when misunderstandings occur, we encourage people to work things out between themselves where this is practical. Where support is beneficial to achieve this, participants agree to ask for help. People are encouraged to take responsibility for their words and actions and listen to constructively-presented criticism with an open mind, courtesy, and respect.
I suspect that many people read the harassment list and the reporting email and stop there. That's understandable. Those parts exist for a reason. But the passage above describes the wide middle ground where most friction in our community occurs.
The middle ground of community health
If the only two options we envision are "this is fine" and "file a report," we end up with a lot of buried resentment, a few dramatic blowups, and not much in between. Most day-to-day friction doesn't rise to the level of a Code of Conduct violation. It's tone. Assumption. Misread intent. A comment in an issue queue from someone who didn't scroll up to read what had already been said. A joke that came off differently than it was intended.
The Community Health Team's work is to strengthen the middle. That means helping people develop the habits and skills to address friction directly, kindly, and early, so it doesn't compound into something that needs the Conflict Resolution Team. The Code of Conduct invites everyone to do this work. Not just CWG members. Everyone.
Some ways we work things out
Here are four situations I've seen in the community, and in some cases been part of. None of these are scripts. They're illustrations. The point is that the Code of Conduct invites you to try, and that you're allowed to. You don't need permission.
- Late at night at a DrupalCon, after hours of sprinting and drinks in the hotel lobby, someone says something about another contributor that turns a few heads. That person might realize it the next day. The generous move, the one the Code asks for, is to find that person and say "I said something last night I want to walk back." Not a grand apology. Just a small, honest correction. Most of the time, that's the whole fix.
- Someone drops a comment in an issue queue without reading the full thread above. Their comment reads as dismissive of work that's already been done, or repeats a point that was already addressed, and it comes off as rude. They might not know that's how it came across. A direct message from someone in the thread ("hey, I think you may have missed a few comments, here's where we landed") can turn that into nothing. A pile-on in the issue turns it into something else.
- You witness an exchange between two people at DrupalCon that makes you wince. Maybe it's cultural. The Drupal community spans continents, and directness that comes across as rude in one country seems normal in another. Maybe it's a power dynamic, or a bad day, or both. Checking in with the person on the receiving end, just between the two of you ("I could not help but notice your conversation and I wanted to ask, are you doing okay?"), doesn't escalate anything. It lets them know they weren't invisible.
- Someone keeps doing something that just doesn't feel right. Not harmful, but grating. You can do your best to describe how it made you feel before it becomes a grudge you carry into every future interaction. "Hey, can I mention something? The way we're doing X did not sit well with me, and I want to figure out how to talk about it."
If you need help figuring out the best way to handle a situation like this, the Community Health Team is available. We can help you talk through a situation, decide whether a direct conversation is possible, or offer a second perspective. You can reach out at any time. We don't investigate, and we don't take sides. We think with you.
When it isn't practical
The Code says "where this is practical." Sometimes it isn't.
We live in a world with power differences. If the person on the other side holds significant authority over your ability to contribute, a direct conversation may not be safe for you. Ongoing patterns of behavior are different from single incidents. Safety concerns are different from style concerns. And if the other person has shown they aren't willing to engage in good faith, you are not obligated to keep trying.
Those are incidents for the Conflict Resolution Team. Those are the situations the people on that team signed up for, and you can reach them through the incident report form. Filing a report is not escalation for its own sake. It's using the right tool for the situation.
The three-pillar framing
Returning to the Driesnote, if community is one of three pillars holding up Drupal, then the pillar can't only be carried by the folks who show up to CWG sessions. The math doesn't work. Community health has to happen in the rooms with the technical sessions, on the Slack channels where the code review happens, or at the dinner table where someone just got interrupted for the third time.
Most of the work the Community Health Team cares about isn't work you need a whole session to learn. It's work you're already in a position to do. The next time something said in an issue queue doesn't feel right, you catch yourself venting about someone, or you see a newcomer get talked over, you have a chance to support Drupal's community.
Community is a pillar, which means it doesn't get held up by a small group of people with CWG in their session title. It gets held up, or it doesn't, by how we talk to each other on a Tuesday afternoon when no one's watching.
Drupal's Code of Conduct doesn't just give you a way to report harm. It also asks you to do the smaller, harder thing first. That's where most community health happens.
04 May 2026 9:04pm GMT
Talking Drupal: Talking Drupal #551 - Drupal Recording Initiative
Kevin Thull, who leads the Drupal Recording Initiative (DRI), joins us to discuss why DRI started, how it scaled from Kevin recording local camps to supporting many events, the hub-and-mentorship model for maintainers, differences between shipping kits vs onsite support, costs compared with traditional AV vendors, and challenges like aging capture hardware, audio/video troubleshooting, and sustainable funding.
For show notes visit: https://www.talkingDrupal.com/551
Topics
- Module of the Week TFA
- Why Recording Matters
- Early Events and Growing Pains
- Post Production and Gear Limits
- Recording DrupalCon vs Camps
- Costs and Value Breakdown
- Pittsburgh Turning Point
- Hubs and Mentoring New Recordists
- Beyond Drupal Events
- Hands Off Goals
- Impact and Adoption
- Workflow Pain Points
- Content First Recording
- Maintainers and Volunteers
- Volunteer Stress Factors
- Funding and Platforms
- Drupal TV Origins
- Roadmap and Growth
- Wrap Up and Contacts
Resources
MOTW - Two-factor Authentication (TFA) - https://www.drupal.org/project/tfa TFA Email OTP Plugin - https://www.drupal.org/project/tfa_email_otp National Institute for Standards and Technology's Special Publication 800-63B section 3.1.1.2 "Password Verifiers" - https://pages.nist.gov/800-63-4/sp800-63b.html#passwordver Drupal Recording Initiative - https://www.drupal.org/project/dri DrupalCon Chicago Playlist - https://www.youtube.com/playlist?list=PLpeDXSh4nHjQpb2cHv9rgQv4lvq1-ZkC3
Guests
Kevin Thull - Drupal Recording Initiative kthull
Guest Host
Bernardo Martinez - bernardm28
Hosts
Nic Laflin - nLighteneddevelopment.com nicxvan
Avi Schwab - froboy.org froboy
Module of the Week
with Avi Schwab- froboy.org froboy
Two Factor Authentication - Two-factor authentication for Drupal sites. Drupal provides authentication via something you know - a username and password while TFA module adds a second step of authentication with a check for something you have - such as a code sent to (or generated by) your mobile phone.
TFA is a base module for providing two-factor authentication for your Drupal site. As a base module, TFA handles the work of integrating with Drupal, providing flexible and well tested interfaces to enable your choice of various two-factor authentication solutions like Time-based One-Time Passwords (TOTP), SMS-delivered codes, pre-generated codes, or integrations with third-party services like Authy, Duo and others.
04 May 2026 6:00pm GMT
UI Suite Initiative website: Video series - #03 Display Builder for Drupal: Entity View Display Explained
A walkthrough of how Display Builder (by UI Suite) takes control of your entity displays - and plays nicely with the tools you already use.The Display Builder module continues to mature, and in his latest video, Pierre walks us through one of its most practical features: Entity View Display. If you've been following the series, this third installment builds directly on the foundations laid in the first two videos (component-based layouts and the plugin system). If you haven't seen those yet, this post should still give you a clear picture of what's possible.You can watch the full demo here: Entity View Display - Display Builder Beta
04 May 2026 1:00pm GMT
30 Apr 2026
W3C - Blog
Age-restrictions on the web and user privacy and safety
In this blog post, W3C CEO Seth Dobbs shares his thoughts about age-restrictions and user privacy on the web - a topic that was at the heart of the October W3C/IAB workshop on Age-Based Restrictions on Content, and recent W3C Members conversations.
30 Apr 2026 8:04pm GMT
14 Apr 2026
W3C - Blog
2026 Breakouts Day recap
Breakouts Day 2026 was the third edition of W3C's fully remote community driven information sharing event. In this post we summarize key aspects of the event.
14 Apr 2026 11:03am GMT
03 Apr 2026
W3C - Blog
The W3C TAG Meeting in London, March 2026
Earlier this month, the W3C Technical Architecture Group (TAG) gathered in London for a multi-day face-to-face meeting. While the TAG meets regularly online, these in-person sessions remain an important part of how the group builds shared understanding, tackles complex architectural questions, and welcomes new members into the work.
03 Apr 2026 12:00am GMT
18 Jan 2026
Official jQuery Blog
jQuery 4.0.0
On January 14, 2006, John Resig introduced a JavaScript library called jQuery at BarCamp in New York City. Now, 20 years later, the jQuery team is happy to announce the final release of jQuery 4.0.0. After a long development cycle and several pre-releases, jQuery 4.0.0 brings many improvements and modernizations. It is the first major … Continue reading
18 Jan 2026 12:29am GMT
11 Aug 2025
Official jQuery Blog
jQuery 4.0.0 Release Candidate 1
It's here! Almost. jQuery 4.0.0-rc.1 is now available. It's our way of saying, "we think this is ready; now poke it with many sticks". If nothing is found that requires a second release candidate, jQuery 4.0.0 final will follow. Please try out this release and let us know if you encounter any issues. A 4.0 … Continue reading
11 Aug 2025 5:35pm GMT
17 Jul 2024
Official jQuery Blog
Second Beta of jQuery 4.0.0
Last February, we released the first beta of jQuery 4.0.0. We're now ready to release a second, and we expect a release candidate to come soon™. This release comes with a major rewrite to jQuery's testing infrastructure, which removed all deprecated or under-supported dependencies. But the main change that warranted a second beta was a … Continue reading
17 Jul 2024 2:03pm GMT
29 May 2023
Smiley Cat: Christian Watson's Web Design Blog
7 Types of Article Headlines: Craft the Perfect Title Every Time
When it comes to crafting an article, the headline is crucial for grabbing the reader's attention and enticing them to read further. In this post, I'll explore the 7 types of article headlines and provide examples for each using the subjects of product management, user experience design, and search engine optimization. 1. The Know-it-All The […]
The post 7 Types of Article Headlines: Craft the Perfect Title Every Time first appeared on Smiley Cat.
29 May 2023 10:20pm GMT
09 Apr 2023
Smiley Cat: Christian Watson's Web Design Blog
5 Product Management Myths You Need to Stop Believing
Product management is one of the most exciting and rewarding careers in the tech world. But it's also one of the most misunderstood and misrepresented. There are many myths and misconceptions that cloud the reality of what product managers do, how they do it, and what skills they need to succeed. In this blog post, […]
The post 5 Product Management Myths You Need to Stop Believing first appeared on Smiley Cat.
09 Apr 2023 5:28pm GMT
11 Dec 2022
Smiley Cat: Christian Watson's Web Design Blog
The Key Strengths of the Best Product Managers
The role of a product manager is crucial to the success of any product. They are responsible for managing the entire product life cycle, from conceptualization to launch and beyond. A product manager must possess a unique blend of skills and qualities to be effective in their role. Strong strategic thinking A product manager must […]
The post The Key Strengths of the Best Product Managers first appeared on Smiley Cat.
11 Dec 2022 4:43pm GMT
01 Apr 2004
Planet PHP
ezSystems are classy folks
Last week I helped the folks at ezSystems debug some APC problems they were having. The problems ended up being a 64bit architecture problem (they have uber-fast Opterons) and the bug is now fixed in 2.0.3.
Today I received Python & XML from them (off my Amazon wishlist). Thanks guys!
On a side note, my wishlist seems borked. The list I get when I search on my email address or name is not the same one I can edit when I log into the site.
01 Apr 2004 6:53pm GMT
PHP april fools...
1st of April 2004 get's to it's end and I guess it's time, to summarize the recent April fools a bit. Not that I think anyone in the world believes in them, but some were quite funny:
1. Changes to case sensitivity in PHP.
Alan Knowles announced that PHP will change to the studlyCase API and therefor will get everything broken by changing established functions.
2. IBM takes over Zend.
Myself hacked a little article about IBM taking over Zend to make PHP a compete of Java.
3. The first PHP virus has been seen.
Wasn't there one last year, too?
4. PHP has been overtaken by Micro$oft.
Mhhh... a little bit unreliable, if they had been taken over by IBM this morning... Maybe one should first look, what others wrote...
5. And finally, PHP4 and 5 showed their real faces...
Take a look at a phpinfo() output!
I guess I missed some, so feel free to comment on this entry, if you found another!
01 Apr 2004 5:49pm GMT
PHP Virus Attacking Web Hosts
Symantec have a report of the virus here. I've yet to see any of the PHP news sites picking up on it but, using a virtual host account, managed to deliberately expose some PHP scripts to it. From examining the infected scripts, what's disturbing is once infected, every tim...
01 Apr 2004 12:19pm GMT