Or, as my slightly tired conference brain briefly renamed it: Contributor Contribution Day.
I know. It is not the official name. That is sort of the point.
This week at WordCamp Europe, I found myself thinking about Contributor Day. Not just what it is called, but what people understand it to be for. Because, for some teams at least, that purpose seems to have become a little muddled.
On one hand, Contributor Day is a brilliant opportunity for people to meet, talk, ask questions, and find their way into the wider WordPress project. For a project as large and sprawling as WordPress, that human connection matters.
It can be the difference between someone feeling like an outsider peering in through the window, and someone realising there might actually be a door.
But on the other hand, if the day becomes framed mainly as networking, chatting, and getting to know one another, then I think we need to be honest about what we are asking people to show up for. Because that is not quite the same thing as contributing.
The version I thought I knew
My understanding of Contributor Day has always been fairly simple. It is a day where people can:
- find out how the WordPress project works
- meet the different Make teams
- get onboarded into a team
- make a first contribution, however small
- and, ideally, know how to continue afterwards
Not a day where everyone is expected to arrive fully formed, magically understand Trac, GitHub, Slack, team workflows, project politics, and the exact shape of “useful contribution” before they have even had their second coffee.
But a starting point. A doorway. A way into this fantastic community and project.
The contribution itself does not have to be huge. In fact, for many people, it probably should not be. A first contribution might be asking a good question, joining the right channel, testing a patch, improving a sentence in the docs, triaging an issue, or understanding where their skills might be useful.
But there should be at least some sense of movement. Even if it is simply sparking an idea in someone to change, update, question, or improve something.
A person should be able to leave Contributor Day with more than a handful of nice conversations. They should leave with a thread they can follow, and a way to contribute further outside the day itself.
The rare thing about WordCamp Europe
At WordCamp Europe, something unusual happens.
Some of the smartest, most experienced, most invested people in the WordPress ecosystem end up in the same place, at the same time, for a very short window.
That is rare.
That is not just “nice community energy.” That is leverage.
You have people who understand the history of the project. People who know where things are stuck. People who can explain why something is more complicated than it looks. People who can unblock decisions, connect dots, point newcomers in the right direction, and help turn scattered interest into something useful.
For one day, the room contains an enormous amount of context.
And if the day does not create natural momentum for the project, we risk wasting one of the most valuable things open source has: aligned human attention.
So if we have all of that in one place, surely the question becomes:
What are we doing with it?
Are we using that moment to help people find pathways into contribution? Or are we mostly hoping that good conversations will somehow turn into momentum on their own?
Networking matters, but it is not the whole thing
I do not want this to sound like I am dismissing networking. I am not.
Networking, when it is done well, is not shallow. It is not just business cards, awkward small talk, and trying to remember someone’s name while staring directly at their lanyard. I am sorry if I have done this. Let’s just say the ADHD is not helping.
Good networking is trust-building.
It is people learning who they can ask for help. It is finding the person who can explain the bit of the project that previously felt impenetrable. It is turning “the WordPress project” from a vague, intimidating entity into actual humans sitting around a table with laptops, stickers, jet lag, and opinions.
That matters.
Especially in open source, where so much of the work depends on relationships, context, and trust. But networking should support contribution. It should not replace it.
Because if Contributor Day turns into something mainly about networking, then maybe we should call it that. Community Day. Networking Day. Meet the Teams Day. Something more honest, and more true to the intention.
But if we call it Contributor Day, people are allowed to expect a route into contributing.
There should also be clearly defined goals, focus areas, or starter tasks for the day. Ideally, these should be shared before the event so people know what they are turning up to.
A room full of people is not automatically momentum
This is the bit I keep coming back to. A room full of capable people is not automatically momentum. Momentum needs continual direction. And a roadmap.
You can put brilliant people in a room. You can give them team tables, Slack channels, handbooks, and good intentions. You can have warm conversations and thoughtful introductions and a genuinely welcoming atmosphere.
And still, some people can leave not really knowing what to do next. That is the gap. Not a lack of goodwill. Not a lack of smart people. Not a lack of care. A lack of pathway.
For a newcomer, the questions are often very basic:
- Where do I start?
- What does this team actually need?
- What counts as a contribution?
- Who can I ask without feeling like I am interrupting?
- What happens after today?
- How do I come back next week when I am no longer sitting in this room?
If those questions are not answered, contribution becomes fragile. It depends on confidence, persistence, luck, and whether someone happens to meet the right person at the right moment.
That might work for some people. But it is not a system.
This does not need to become a productivity contest
To be clear, I do not think Contributor Day should become some grim productivity sprint where everyone is measured by tickets closed, patches submitted, or commits made before lunch.
That would miss the point entirely.
People are tired. Conferences are intense. New contributors are often nervous. Long-time contributors are often stretched thin. And the last thing anyone needs is a day that turns contribution into performance.
But there is a middle ground between pressure and drift.
We can make space for conversation while still giving people direction to follow. We can welcome people warmly while still helping them do something real. We can value connection without pretending that connection alone is the same as contribution.
The point is not output for the sake of output. The point is continuity.
Maybe the success metric is wrong
Maybe the question is not:
What did we ship on Contributor Day?
Maybe the better question is:
How many people left knowing how to continue contributing tomorrow?
That feels like the real measure.
Not whether someone made a huge contribution on the day itself. Not whether every table produced something visible. And certainly not whether the room looked busy enough from the outside.
But whether people left with a clearer understanding of where they fit. Whether they knew the next step. Whether they had a reason to come back.
Because that is the difference between a moment and momentum.
What would make Contributor Day feel like a pathway?
I do not think this needs to be complicated. In fact, it probably should not be.
Contributor Day does not need more ceremony. It needs clearer routes in, through, and out of the day.
That could look like:
- each team sharing a short list of focus areas before the event
- beginner-friendly tasks that are clearly marked as suitable for first-time contributors
- a named person at each table whose role is to help newcomers get oriented
- a simple explanation of what counts as a contribution for that team
- a clear “what happens next” step for people who want to continue after the day
- follow-up links, Slack channels, or next meeting dates shared before people leave
Nothing huge. Nothing that turns the day into a factory. Just enough structure so that people are not relying entirely on confidence, luck, or already knowing the right person. Because a pathway does not have to be rigid. It just has to be visible.
So what is Contributor Day for?
I think it should be both. Connection and contribution. Belonging and direction. Conversation and movement.
But if we lean too far into “just chat amongst yourselves,” we risk wasting something genuinely rare: a room full of capable, invested people with shared context and a willingness to help move the project forward.
And if people are showing up because they want to contribute, even in small ways, then we owe them more than a networking-shaped day with a contributor-shaped name.
Maybe Contributor Contribution Day is a silly phrase.
Maybe it is just my tired brain making nonsense out of conference signage and Slack messages. Or maybe it points to something worth taking seriously.
Contributor Day does not need to become more intense. It does not need to become more formal. It does not need to become a productivity contest.
But it does need to help people leave with a clearer next step than the one they arrived with.
That might be the smallest useful measure of success:
- Did people leave knowing where they fit?
- Did they know what they could do next?
- Did the day make it easier for them to come back?
Because if the answer is yes, then Contributor Day has done something powerful. It has not just gathered contributors in a room. It has helped people become contributors.
Leave a Reply