Category Archives: community

Letters to an open source contributor: Leadership

Much of my work in WordPress over the past decade has involved coaching and training leaders working in open source, and as I wind down this part of my career, I find I have a lot to say on the topic! I’m going to try to follow my own advice and be brief here, but I do not promise.

If you’re just getting started hearing me talk about leadership, I recommend a previous post of mine: What happens when you won’t admit (or don’t realize) you’re a leader. That piece resonated with a large number of people I’ve worked with in WP, so I’m recommending it as supplemental reading for this article.

Oh! And the other important thing to know, going into the leadership advice I will share below, is that I firmly believe in leadership at any level of an organization. Open source embraces this idea, in that our organizations are usually less hierarchical and, because the work is accomplished by the people who show up at the time, more fluid when it comes to who we look to, when we’re navigating a problem.

So! With those ideas in mind, let’s dig into more advice for leaders in open source.

Don’t make yourself indispensable

One of the most powerful things I’ve learned from Josepha is that

If you can’t be replaced, then you can’t be promoted.

– Josepha Haden Chomphosy, Executive Director of WordPress

I know, I just told you that open source isn’t very hierarchical, and I wasn’t lying. This concept applies to flat/open source organizations more like this:

If you can’t be replaced, then you can’t ever work on cool new stuff. Because if you do, all the cool old stuff you built… will end, or break.

Teaching people how to do the work that you do? It’s time-consuming, and can be a real challenge. But the people who do this — who document their code, who design in public, who create a succession plan and train their replacements — those people get the best that open source has to offer. They get to create amazing new features, programs, events, etc… and then they get to see those things keep growing, even when they move on to the next thing.

Recruiting, training, and cultivating your successor will make you much freer and more nimble, in an organization. It’s also the best way to ensure your work has a lasting effect.

Love your beginners

Photo by Ron Lach on Pexels.com

If you want your project/initiative/coalition to grow, you need to welcome new people into it. One of the things about new people = they don’t know everything yet. Don’t fall into the trap of thinking that ignorance is the same as stupidity — answer questions (even the ones you answer a lot!) with warmth and grace.

Also, be aware that beginners are a rare and valuable resource. They see things with fewer preconceived notions than the people who’ve been around for a long time. They question things that tenured contributors don’t even notice anymore, or have given up complaining about but still dislike.

Beginners are also an endangered resource! If you can get them to stick around a while, and train them for a while, then guess what? They’re not beginners anymore! So be sure to engage with your new people while they’re still new, and can help you fill in some blind spots or clarify where your outreach or messaging is still confusing.

Open source your decisions and thought process

Working in public is one of the hardest things we do, in open source, but profoundly worthwhile. Transparent processes and work patterns result in well-documented decisions, which lead to higher-quality contributions in the future.

I had this realization a few years back, when I was complaining (not for change, btw) about how many suggestions my team got, that didn’t demonstrate an understanding of what our work was about, or why things were set up a certain way.

“Why don’t they understand that [thing that was obvious to me at the time]?!?,” I fumed. And then it hit me: BECAUSE I HAD NEVER TOLD THEM.

Me, about me.

When you keep your concerns, doubts, convictions, and theories private, then the people who show up to collaborate with you… are slower to connect with both you and the problems you’re trying to solve together. Maybe so slow that you never connect in the first place.

But thought leadership can scale pretty elegantly, if you are willing to work in the open and diligently share your goals, observations, reasoning, and philosophies. It’s not easy, but it works.

Play the long game

Things tend to move slowly in large organizations, even if you have all the power in the world. Groups with broad impact are powerful but tend not to be nimble. So you will run into a roadblock or traffic jam in something you’re trying to accomplish.

When this happens, try not to force it. Do your best to take the long view, and bide your time. I have accomplished a lot of things in WordPress that I wasn’t sure were possible, sometimes simply because I stuck around longer than the people who were blocking my progress.

Be patient, pace yourself, and keep a few ideas on the back burner, for when conditions might be right for them. The story only ends when you stop writing it.

Looking for more advice?

If you’re joining this open source advice series in progress, you might enjoy the other articles, too!

  1. Intro: Letters to an open source contributor
  2. Communication
  3. Collaboration
  4. Criticizing for change

I think I have a few more of these articles in me, so stay tuned!

Letters to an open source contributor: Criticizing for change

This post is subtitled “criticizing for change” because not every criticism is fueled by a desire for change. Some arise because someone is having a rotten day, looking to connect over a shared experience, or even declaring what they value. Treating all criticism equally is as big a mistake as ignoring all criticism.

But this post is for critics, not those being criticized. More specifically, this article is for those of you who see things that you think are wrong in open source, and want tips for sharing your critical feedback in ways that that are more likely to result in a change.

The bigger the change, the longer the game

Photo by Krivec Ales on Pexels.com

Organizational change takes time. Big-impact changes take time. Big-impact changes in large organizations take a LOT of time. Change advocacy can be tiring, so I recommend taking the long view and setting yourself smaller, more attainable goals that will pave the way toward your ultimate goal. If you can, if you are privileged enough to have the time and stamina, pace yourself.

Avoid personal attacks

Some open source projects like WordPress have fostered a deeply connected, engaged community of contributors. Open source is also deeply vulnerable to the Five Geek Social Fallacies, which can lead the group to close ranks around a community member if that person is criticized or attacked, even if that person has done bad things.

This doesn’t mean that you can’t say, “this person’s behavior was terrible.” You can. But if you lead with “this PERSON is terrible” and point to their behavior, you will lose a lot of people before you even get to your examples.

For better or worse, repetitive critiques of a particular person or people result in diminishing returns. The reason I encourage people to love their critics is because most people start ignoring messages from “a complainer” or “someone with a grudge,” after a time. If you’re playing the long game and working toward change, then remember to criticize the behavior, not the person.

Build coalitions

In open source — and probably everywhere — it’s easier to get people to listen if you are speaking as part of a group, instead of a lone voice of dissent. This doesn’t mean lone voices of dissent are any less correct, or that a group is guaranteed to be right. I’ve seen large groups of people who were wrong, in open source, and been part of groups that were wrong, myself. That’s just part of being human. (Unfortunately. I sure do love being right.)

That said, building a coalition is the most effective tactic I know, to successfully accomplish change in an organization. Convincing other people of your idea’s merit on a small scale demonstrates a plausible promise. That plausible promise helps more people take your idea seriously. As you continue to test the idea with more people, presumably the idea gets refined and improved, helping it fit better into the fabric of the project. Eventually, the idea builds enough momentum that it takes on a life of its own. By the time that happens, you can usually just sit back and let the organization grow into the change.

Optimism FTW

Open source contributors are optimistic — you don’t put the time into contributing to a project that’s bigger than you, unless you have hope that your work will have an impact. Our work is fueled by hope, and our hope fuels our work. In contrast, advocating for change can be discouraging, which can lead to cynical or despairing attitudes.

I hope this goes without saying, but I’ll say it anyway: you’re going to have a really rough time getting inherently optimistic people to want to work on a change that comes with the message that “we’re all doomed.” And if you believe, down deep, that nothing’s going to help, then you’re probably not criticizing for change in the first place.

Either way, “this idea could make us great!” is a much more motivating message than “this idea could make us less terrible!” Tap into that open source optimism, and let it give your idea wings.

Pragmatism is powerful

It may be that the change you’re suggesting is morally right. I hope it is! But remember that what’s considered morally right… varies between different cultures. And most open source projects include contributors from many different cultures — WordPress certainly does. So I recommend against relying on the argument that “it’s the right thing to do.”

Instead, focus how the change you seek will help the organization move closer toward its goals. Warning: this does require you to understand what the goals of the organization are! But if you don’t know that already, then pause until you learn them. You never know… what you identify as a bug, might actually be considered a feature!

What did I miss?

Any other tips for our change-makers? Does something I’m saying sound wrong to you? Share your advice or ask questions in a comment on this post!

Letters to an open source contributor: Collaboration

You don’t have to want to collaborate to use WordPress to do great things. You DO need to collaborate if you want to do great things in the WordPress open source project, though.

Collaboration isn’t always the fastest way to accomplish something, but I think it is the best way to accomplish things that have a huge impact. Most people are called to open source contribution because they are impact-driven and know that by working with lots of other people, they can grow their own skills and make better decisions/products/programs. Also, it’s fun!

So here’s some advice I find myself sharing semi-frequently, on collaboration in open source

Love your critics

Now don’t get me wrong — I don’t like being criticized; I hate being wrong, and I hate thinking that someone things I’m wrong even more. AND….

Don’t make the mistake of throwing away valuable feedback just because someone is angry or shares opinions you don’t agree with. You probably don’t know everything (and if you do, I wish you’d write it all down so I could, too!), so even mean feedback is data.

Photo by Anete Lusina on Pexels.com

If you accept the notion that good ideas can come from anywhere — a foundational idea in open source, fwiw — then it’s criminally stupid to decide to stop listening to someone, just because you don’t like what they’re saying.

Beyond avoiding dumb moves, sometimes critical feedback is immensely useful. You can use it to check in with fellow contributors to see who shares the same ideas but just hasn’t been brave enough to say anything. You can use it to learn how you might be mis-communicating or misleading people in your communication. You can use it to fill in your own blind spots.

All that to say, don’t write people off as trolls unless they’re abusive, making personal attacks, or inciting violence. In open source, as in many other places, resilience in the face of criticism will make you much more effective, longer.

Assume smart predecessors

This is a twist on “assume good intent,” which I probably should have included in my Communication article.

I often talk to open source contributors who have found an organizational dysfunction and are passionate about fixing it. They come at the problem from multiple angles, talk to all sorts of people about their ideas for making things better, and keep running into roadblocks. It might be that others see the problem and have learned to work around it, or that fixing the problem isn’t a high priority right now. It might be that people disagree there is a real problem. Regardless, it’s frustrating for all involved.

My advice: when you notice an inefficient or “broken” thing in an organization — whether you’re just getting started or moving deeper into the group — get curious and ask yourself a few things before acting:

  1. Am I the only person who notices this, and if so, why?
  2. Who else experiences this problem?
  3. Has anyone tried to address it in the past; if so, what did they try and why did it fail?
  4. Do I have the agency/authority/expertise to fix this? Who does?
  5. What does this “broken” thing fix, in the organization?

That last question is the most important one. Here is a truth: no organization tolerates broken processes unless those “broken” things are actually functional for some person or group. That doesn’t mean that anyone intentionally set it up that way — almost always not! — but if it’s persisted for a while, then this broken thing is fixing something, somewhere. And until you know who benefits from the inefficient process, you have at best a 10% chance of success, in changing it.

In your zeal to contribute, don’t assume you are the first smart or perceptive person to join an open source project. This doesn’t mean you don’t have the “right” answer! but do yourself the favor of learning from tenured contributors, and spending your energy wisely.

Start small and iterate

Mighty oaks from little acorns grow!

Photo by Eriks Abzinovs on Pexels.com

Open source is very friendly to new ideas and experiments. But when you work on a large scale, or in a large project, it can be hard to discern how and when to experiment. If you are still working on building trust with other contributors, the best way to try out a new idea is on a small scale at first, but in a way that can scale if your experiment is successful.

The best open source experiments start out by answering these questions:

  1. What problem are we trying to solve?
  2. What theory will we test in this experiment?
  3. How long will we test this theory?
  4. Who will participate in the experiment?
  5. Who needs to know about this experiment? Who needs to agree to it?
  6. How will we measure the outcome of our experiment, in a way that tells us whether we’ve solved the problem?
  7. If this causes an unforeseen problem, how will we gracefully end the experiment?
  8. Where will we communicate about this experiment?

You can limit the impact of an experiment’s failure (to the organization and other contributors) by offsetting risk and scope. If the impact of an experiment’s failure is likely to be low, then the scope of the experiment can be more broad. If the impact might be high, then the scope of the experiment should be more narrow. 

What did I miss?

Does this all make sense? Is there another tip for effective collaboration that you wish more people knew? Add your advice or questions in a comment on this post!

Letters to an open source contributor: Communication

Josepha likes to say, “all problems are, at their heart, communication problems,” and I couldn’t agree more. The most powerful tool in your open source toolbox is not an understanding of code or usability, but rather the ability to express yourself and understand what other people are trying to say.

Here are some qualities I have observed among highly successful contributors in open source:

Brevity

Avoid “walls of text,” long paragraphs, and complex sentences.

Inexperienced or insecure contributors sometimes try to establish credibility or persuade their audience by writing a LOT of words. This is a mistake. Verbose communication requires people to work extra-hard to understand what you think or want. By the time they think they understand you, they are likely irritated that they’ve had to work so hard, or they have untested assumptions about why you’re burying them in words.

This is not easy advice for me to follow, because I love words and complex sentences! So when I’m writing to communicate in open source, I make a first draft and then cut words and sentences as far as I can. I sometimes joke that most of my writing time is actually spent deleting!

In open source, time is short and information overload is constant. You appear aggressive and disrespectful when you only communicate in long, complex messages. Be kind; be brief.

Humility

Don’t try to establish credibility by trying to appear smarter than other people; it just makes you look like a jerk. No one wants to work with someone who brags about their skills or calls attention to other people’s ignorance.

Photo by Magda Ehlers on Pexels.com

No one was born knowing any computer language, or any fact, about open source or WordPress. Even if people were snotty to you as you were learning — remember how bad that felt, and don’t perpetuate the pattern. Rise above, and be kind to those who know less than you.

Showing off rarely makes you popular in open source, but humility and helpfulness nearly always do.

Consideration

Open source projects are, if they’re lucky, global organizations full of very different people. Working in the open, with lots of people who are very different from you, is a great way to build something extraordinary.

Photo by Dio Hasbi Saniskoro on Pexels.com

To communicate effectively in those conditions, you must consider how your messages will be received by people from many different backgrounds and cultures. This isn’t just about refraining from slurs, swearing, broad generalizations, and gendered language — though, please avoid all that too! Really, I mean it!

But considerate communication is also:

  • thinking about how to include more people into the conversation, regardless of time zone,
  • allowing enough time for people with different availability to join a discussion or project,
  • assuming positive intent,
  • using group Slack pings sparingly, and
  • thinking about how people will feel, when they read your message(s).

We also communicate considerately by focusing our criticism on the problem, rather than the people. Personal attacks won’t get you anywhere that you really want to be.

Over and above

For even more open source/WordPress communication tips, check out these lessons from the WordPress contributor training course!

What did I miss?

Hey, other experienced open source contributors, what else do you think people need to know, about communicating successfully in open source? Add your advice in a comment on this post!

Thanks for a great 10 years, WordPress!

My friends! After 10 years of working full-time on the WordPress open source project, I have some news: I have accepted a community-focused role at Reddit, and will be leaving Automattic in September.

I will take a break from contributing to WordPress until the end of the calendar year, if not permanently. I think the transition from a full-time, paid contributor to a part-time, volunteer contributor is made smoother with ample “reset” time.

Taken at WordCamp Toronto 2018

I was hired by Automattic in 2011 to implement a new WordCamp program, which had been designed and launched by Jen Mylo (Jane Wells at that time) and Matt Mullenweg. Helping WordPressers understand why it was necessary for them to follow rules/guidelines/expectations was… a challenge, I’m not going to lie! Looking back, I can clearly remember all of my mistakes, and only dimly remember my successes… but we’re all still here, so I guess we didn’t do too badly in the end.

Speakers, sponsors, volunteers, and attendees gather for the inaugural WordCamp US 2015 #wcus, https://www.flickr.com/photos/wordcampunitedstates/23801673750

Since starting that journey I’ve organized events large and small, advised/cajoled/cautioned/mentored/encouraged countless contributors, resolved and de-escalated conflicts, spoken at conferences, recruited innumerable contributors, and trained many, many leaders. I’ve helped onboard people and businesses all over the world to open source culture and philosophies, and helped bring people together to work on (and sometimes solve!) complex problems. I couldn’t be more proud of what we’ve all accomplished together!

The “silly” group photo from the WordPress Community Summit 2017, in Paris

I am so grateful to have spent the last 10 years working with WordPress contributors. I don’t think there’s a better place to learn about and grow open source, and it’s been my honor to collaborate with so many ambitious & independent optimists over the years, even if we didn’t all always agree! I absolutely *LOVE* to learn new things, and the WordPress ecosystem has never failed to bring me valuable lessons on the regular.

I know that I’m leaving the people of WordPress in excellent hands with Josepha and all the other clever, compassionate leaders that have joined us over the years. I hope that, if you’re a WordPresser and you have the energy to help, that you’ll take every opportunity to lead at any level, making WordPress a little more friendly and welcoming for others. If I’ve helped you in any way, the best way to thank me is by helping someone else. Maybe even more-than-one someone else. 🙂

I plan to continue using this site to share my musings and learnings about community, open source, and leadership, as I discover what Reddit has to teach me. If you want to keep in touch, be sure to subscribe to this blog (in the footer), or come find me on Twitter or LinkedIn.

Thanks for all the fish, WordPress! It’s been a wonderful decade, and I can’t wait to see what you do next.

Blackfoot wisdom, Maslow’s hierarchy, and open source

In a fascinating recent article called Could the Blackfoot Wisdom that Inspired Maslow Guide Us Now?, Teju Ravilochan (along with contributing editors Vidya Ravilochan and Colette Kessler) shared that 

Maslow’s Hierarchy of Needs may have been inspired by the Siksika (Blackfoot) way of life… His time there upended some of his early hypotheses and possibly shaped his theories…. Whereas mainstream American narratives focus on the individual, the Blackfoot way of life offers an alternative resulting in a community that leaves no one behind.

– Teju Ravilochan, Could the Blackfoot Wisdom that Inspired Maslow Guide Us Now?
Image of the Siksicka Nation crest, with a stylized buffalo in the center of a circle, two feathers on the left and right side of the circle, and a pipe and hatchet at the bottom of the circle, crossed.
Photo by @AlbertaRhPAP, licensed under CC BY 2.0

According to Gitxsan, First Nation member, and University of Alberta Professor Cindy Blackstock, Maslow had been “stuck on his developmental theory” before visiting the Blackfoot Reserve, and found shape for his ideas in their teachings. In an article called Maslow’s hierarchy connected to Blackfoot beliefs, Karen Lincoln Michel recounts a presentation by Dr. Blackstock in which the familiar pyramid diagram of Maslow’s hierarchy* is compared to a First Nations perspective:

from Maslow’s hierarchy connected to Blackfoot beliefs by Karen Lincoln Michel

“First of all, the triangle is not a triangle. It’s a tipi,” Blackstock said. “And the tipis in the Blackfoot (tradition) always went up and reached up to the skies,” she said.

Another difference noted by Blackstock is that self-actualization is at the base of the tipi, not at the top where Maslow placed it. In the Blackfoot belief, self-actualization is the foundation on which community actualization is built. The highest form that a Blackfoot can attain is called “cultural perpetuity.”

from Maslow’s hierarchy connected to Blackfoot beliefs by Karen Lincoln Michel

* It’s worth mentioning that this pyramid diagram was not created by Maslow, and that Maslow himself “made it quite clear that we are always going back and forth in the hierarchy, and we can target multiple needs at the same time.”

OMG OSS

This diagram is exciting because when I think about successful open source communities, they look a lot like this First Nations model. In open source, we frequently discuss ways to avoid the tragedy of the commons, but — at least in my reading — spend less time talking about what we could aspire to. If we want open source to endure beyond the closed/proprietary platforms that it’s competing with, I think we should aspire to a model founded in Blackfoot beliefs.

The contrasting diagrams above illustrate a difference in worldview that often appears when welcoming newcomers into open source. Many people who come to free, open source software communities are dazzled by the freedom, because they see that freedom as a way to accelerate their own self-actualization. 

In the case of the WordPress community, they see opportunities to found businesses based on WordPress extensions (themes, plugins), WordPress site building, WordPress hosting, or WordPress training. They see opportunities to build their skills through code review and design feedback from world-class developers and designers. They see opportunities to build a following through speaking at WordPress events and leading WordPress communities. These people are not wrong, necessarily, but they might not be aware of the whole picture. 

Participating in the WordPress community only to further self-actualization could be crudely described as a “what’s in it for me,” or an opportunistic, approach. Opportunism is an anti-pattern in an open source organization for many reasons, not the least of which is how it limits someone’s growth in the community. When someone is primarily interested in what an open source project can do for them, regardless of how that affects the ongoing success of the project, then their circle of caring is limited, as is their influence in the group. 

The First Nations diagram helps illustrate this: open source works much more along the lines of the First Nations model, in which self-actualization exists in the base, supporting community actualization and cultural perpetuity.

While Maslow saw self-actualization as something to earn, the Blackfoot see it as innate. Relating to people as inherently wise involves trusting them and granting them space to express who they are (as perhaps manifested by the permissiveness with which the Siksika raise their children) rather than making them the best they can be. For many First Nations, therefore, self-actualization is not achieved; it is drawn out of an inherently sacred being who is imbued with a spark of divinity.

– Teju Ravilochan, Could the Blackfoot Wisdom that Inspired Maslow Guide Us Now?

“In the Blackfoot belief,” according to Blackstock, “self-actualization is the foundation on which community actualization is built. The highest form that a Blackfoot can attain is called “cultural perpetuity.” Community actualization is the communal responsibility of “meeting basic needs, ensuring safety, and creating the conditions for the expression of purpose” for individuals. 

In the WordPress community, community actualization occurs in SO many ways: when experienced WordPress enthusiasts help new WordPress-ers find the right plugin or configure their theme the way they want it. Community actualization happens through the work of our support forum volunteers, and in the work of community organizers who make space for new voices in WordPress to share their unique perspectives. We’re also supporting community actualization when we “call in” those whose behavior causes harm, showing that someone may need extra support in their own self-actualization. The work of core developers and designers to continually fix and improve WordPress through regular software releases, bringing new and refined features to 42% (and counting!) of the internet, is community actualization too. And of course, the community actualizes when we gather to share knowledge (and food!) at a WordCamp or meetup.

A group of conference attendees, sitting in a circle, with plates of food in their laps, in a grassy space.
Photo taken by Aaron Hockley at WCSF 2013

WordPress community actualization provides space for the self-actualization of millions: all WordPress users, of course, and all those who work or play in the WordPress open source project. And when we do it right, when we bring our generosity and patience to how we collaborate, remembering to holding space for others to feel welcome and join in, and acknowledging all the people who got us here, then we also further our cultural perpetuity.

As Karen Lincoln Michel describes it, cultural perpetuity is “an understanding that you will be forgotten, but you have a part in ensuring that your people’s important teachings live on.”

WordPress works toward cultural perpetuity when we work in public, where our work is archived (so future contributors can learn from us). We support cultural perpetuity when when we welcome and mentor new contributors, and when we hand off leadership roles to others. I also see us shoring up cultural perpetuity when WordPressers blog about how to succeed, and when we share what WordPress has done for us.

Open source = a better internet

A clockwork-style spiral, metallic, with roman numerals and with rays on the outside of the spiral
Perpetuity, by Ghetu Daniel, is licensed under CC BY 2.0

I love seeing WordPress grow, because I believe that open source makes the internet a better place. I also believe that welcoming people into thriving open source communities can help them find the kind of interdependent, mutually-beneficial society that is elusive in many parts of the globe. 

According to Blood and Heavy Head’s lectures (2007), 30-year-old Maslow arrived at Siksika along with Lucien Hanks and Jane Richardson Hanks. He intended to test the universality of his theory that social hierarchies are maintained by dominance of some people over others. However, he did not see the quest for dominance in Blackfoot society. Instead, he discovered astounding levels of cooperation, minimal inequality, restorative justice, full bellies, and high levels of life satisfaction. He estimated that “80–90% of the Blackfoot tribe had a quality of self-esteem that was only found in 5–10% of his own population” (video 7 out of 15, minutes 13:45–14:15). As Ryan Heavy Head shared with me on the phone, “Maslow saw a place where what he would later call self-actualization was the norm.” 

– Teju Ravilochan, Could the Blackfoot Wisdom that Inspired Maslow Guide Us Now?

This is the kind of idyllic state that I hope for, in the WordPress we are all building together. By continuing to support community actualization and cultural perpetuity, our dedicated contributors make this possible.

Thank you to all current contributors who make up this interdependent web of support. If you’re not already contributing to WordPress, check out our teams, and join us! There’s a seat for you at this table. 

Further reading

The other side of the coin: what people get out of contributing to WordPress

The first iteration of this article, The 4 “Gets” in WordPress Community Organizing, was written in 2019. In this update, I apply these ideas to all parts of the WordPress open source project.                     

People all over the world contribute to WordPress, in many, many ways. 

WordPress contributor handbooks have lots of public information about what each team does, and how or what they ask people to give when they contribute. However, there isn’t always a clear explanation of what contributors might expect to get, from or through their contribution. While many people know that WordPress is made possible through volunteer time, it’s sometimes less clear what kind of reciprocity exists in the project. But for everything that a contributor gives, there is almost always something that they receive.

Photo by Raphael Brasileiro on Pexels.com

Here’s an incomplete-but-good-starter list of some benefits that WordPress contributors might get, through contributing to WordPress:

Impact

As of early 2021, WordPress powers 40% of the web. That’s an enormous footprint for an open source project. The decisions made by Core designers and developers affect millions upon millions of users. Translators extend the power of WordPress to 75% of the world’s population that doesn’t speak English. WordPress community organizers bring together nearly half a million enthusiasts per year to talk about the software. Our documentation and support forum threads are viewed by millions of people every month. 

It’s hard to find another volunteer-based, open source organization that compares to WordPress, for reach and impact. 

Growth 

In WordPress, most volunteer opportunities are based on your interests, not your experience. WordPress community organizers aren’t required to have organized an event, or have managed a team, before taking on a leadership role in their local communities. No one reviews a developer’s resume, or a designer’s portfolio when considering whether to merge a patch to the WordPress core software. You don’t need to be a professional speaker or educator to create a workshop for learn.wordpress.org.

And yet, working in WordPress gives contributors a chance to develop a broad array of skills: leadership, communications, design, logistics, marketing, fundraising, management… the list goes on.  Every one of these skills can create opportunities in someone’s professional career or personal life — and generally can offer a safe place to experiment, where you’re not risking your career if your idea doesn’t work out. 

Training/Support

Most of what contributors need to know to get started, and become proficient, is publicly available. You don’t need anyone’s permission to submit a patch, share a solution in the support forums, or test a theme for accessibility.  Onboarding to many roles is unusually short, compared to many other global volunteer programs — even for roles with specialized skills/knowledge, like writing lesson plans or translating WordPress. 

Our training, documentation, best practices, and tools are produced by experienced contributors — many of whom do that kind of work professionally. And when contributors run into problems they don’t know how to handle, nearly every team has a group of experienced helpers available to give feedback. Through sharing feedback, contributors grow together as they work to meet the high standards that come with high-impact work.

Safety

Though this limited autonomy sometimes shows up as a “bug” for contributors (sometimes it sounds like “why are people getting in the way of my excellent & important idea?!”), I firmly believe this is a desirable feature. 

Nearly every contributor opportunity has checks and balances in place, which reduce risk when volunteers try out their bright ideas (either in theory or in practice), without endangering the success of any major WordPress components or initiatives. Code contributions are reviewed by world-class developers before being added to the core software. New event formats are discussed and refined before we try them out, are documented, and then iterated upon. Translations are reviewed and edited before they go “live.”

So! 

Those are some pretty great things you can expect when contributing to WordPress! AND… there are things that no one gets, or that only come with time or experience — and it’s important to call those out too.

What WordPress contributors don’t get (right away, and sometimes ever)

Photo by Tim Gouw on Pexels.com
  1. Complete autonomy. As mentioned above, contributors can make a lot of powerful choices when helping to build, maintain, extend, and promote WordPress — but that doesn’t mean they can make just any choice. If you accept a position of responsibility as a WordPress contributor despite disagreeing with some parts of the role, you’re still expected to do the things that everyone in that role is asked to do — they’re part of the job.
  2. Commit-level access. WordPress contributors are full of bright ideas, which is a lot of what makes this project so great. Not every bright idea meshes well with WordPress project values or works on a broad scale, though. The WordPress open source project is open source, but it’s not open commit*. Even if you are certain that your idea is a good one, it still might not work as part of WordPress core software, or in the WordPress community. Commit-level access (and similar levels of responsibility on other WordPress contributor teams) can be earned over time, of course. 
  3. And other things.  There are other things, too, which are detailed in contributor handbooks or other kinds of contributor training or resources. (For the Community team, they’re outlined in the 5 Good Faith Rules for meetups, plus Should You Be An Organizer? and Representing WordPress docs in the WordCamp organizer handbook.) To summarize, it’s best not to try to establish a leadership position in WordPress for self-serving purposes. Likewise, if your leadership approach includes hateful or very controlling behavior, WordPress probably won’t be a good fit for you.

Share your thoughts

What do you think about this list of “get”s and “don’t get”s — does it accurately describe the kinds of personal return that contributors can reasonably expect for the time they invest in contributing to WordPress? Follow-up question: what did you expect you’d get out of contributing to WordPress, and what did you actually get?

*An ”open commit” project allows anyone, no matter their level of familiarity or expertise, to commit their code to the core code base. 

Some reflections on Dotorg dilution, and how to combat it

When I started working in WordPress, about 10 years ago, Jen Mylo warned me about about something pretty early.

At some point, you start seeing all the things that aren’t working, and you will want to fix them all, all at once. Don’t let yourself get distracted. You’re here to work on certain things, and you can’t do that if you’re working on all the things.

— something like what Jen told me, probably back in early 2011

Let’s call it Dotorg dilution.* This experience — being overwhelmed by the many places and people needing help, and taking on so many things that you suddenly find yourself spread too thin to accomplish much of anything at all — hits nearly everyone who gets involved in the WordPress open source project beyond a surface level. WordPress tends to attract helpful people (luckily for us!). The organization is vast. There’s a lot to do, and not a lot of people to do it.

I’ve seen this affect contributors differently, depending on whether they are paid or volunteers, so I’ll address both cases separately.

Volunteer Contributors

Dotorg dilution generally hits a volunteer/unpaid contributor in the Engaging or Producing stage, and it can block or slow someone’s progression on the contributor ladder. I usually notice because suddenly that person is everywhere, taking part in every new project, initiative, or experiment that comes along. Burnout is a danger at that point, and a number of enthusiastic people cycle out of volunteering every year because the dilution makes them feel (rightly) that they aren’t making a difference. Here’s my advice for avoiding that:

Stop and drop

If you’re struggling with this problem, I recommend you pause and spend some time thinking about what excites you most about contributing to WordPress. Then, identify how much time in a typical week or month you might have available for volunteer time, both in the short- and long-term. It might be someone can help in the support forums or translations while their local WordCamp isn’t in active planning, but during the 3 months of pre-WordCamp intensity, they have to step back from contributing in another area. Once you figure out what you realistically have time for, start cutting back on your commitments.

It’s OK to step away

Once you’ve decided how much time you plan to put into your WordPress contributions, communicate proactively if you need to change your role, reduce your commitments, or take a break. Very, very few contributor roles require long-term, fixed time commitments (which is great for flexibility). In the case of work that includes fixed time commitments or specialized skills/knowledge, such as WordCamp lead organizing or a role on a WordPress core release, it’s important to communicate as early as possible if you think you’ll need to step back, for a time or permanently. Nearly every contributor has had to make a tough decision about priorities in their WordPress work, so messages like “I really wanted to do this, but I’ve found that I just don’t have the time” are nearly always met with understanding and grace.

Fight FOMO with long-term thinking

For better or worse, many things move slowly in WordPress. Just because there’s a lot of energy around an idea or initiative right now, doesn’t mean you need to drop everything else to focus on a new project. Many, many (most?) projects go slower than expected, or will need a new influx of contributors in a few months or next year — in fact, that’s when they’ll need help even more! Large-scale organizations like WordPress frequently need help with sustainability even more than they do with new initiatives.

Come back anytime

Finally, I hope all volunteers remember that WordPress is a safe and welcoming place to step away from and back to. If we haven’t seen you around in a while, we probably miss you! Come on back, as soon as you’re ready or have time for a new challenge.

Paid Contributors

Dotorg dilution can affect paid contributors differently, due to a few factors:

  1. We’re here to do a job. Companies don’t just send employees into WordPress to do “y’know, whatever looks important.” We’re all on teams that have set goals — ambitious ones, at that! — and if we don’t work on the things we’re asked to work on, there will be employment-level consequences. That said, we all have some autonomy in our work, and we’re all very performant. It’s easy to think, “I’ll just take this on in my free time. All of those people are working on this in *their* free time, why not me too?”
  2. We have more time than most. Compared to most volunteers, paid contributors have an embarrassment of hours to work on things. Not offering to spend time on something can sometimes feel awkward if you’re the only person in the meeting or group who’s being paid to contribute, or contributing full-time.
  3. We can lend legitimacy. If an initiative or project has paid contributors working on it, that will sometimes give people the impression that it’s “sanctioned” or prioritized by project leadership (which is not always true). Volunteer contributors who consciously or unconsciously recognize this, might put extra effort into recruiting paid contributors for their passion projects/ideas.

Avoiding Dotorg dilution as a paid contributor isn’t complicated, but it’s also not easy. Here are some tactics that have worked for me and others I know:

Make all WordPress work = work

This is one of my preferred tactics: I don’t contribute to WordPress in my non-work time. I might volunteer for other organizations in my free time, and I might even help them with a WordPress site as part of that volunteer work (woe be unto them, I’m not very helpful). But if I do WordPress work after-hours, then I’m working after-hours — no exceptions.

Check in with your lead or colleagues

If an initiative seems really compelling to you and seems to need people badly, but also seems like it’ll interfere with your assigned/identified high-priority work, check in with your colleagues to see if the work fits into someone else’s work scope. If you think your list needs to be re-prioritized, definitely talk to your lead about that before you go too deep on a “new, shiny.”

Remember that challenging problems can lead to growth

WordPress is an organization that fosters growth for volunteers with many backgrounds and skill sets. We’re an incredibly supportive bunch, too. If you’re not able to help this time, or this year, that doesn’t mean an initiative is guaranteed to fail — and if it does fail, that failure may be more beneficial than you expect. Failed experiments can teach just as much as successful ones.

Share your challenges or pro-tips!

If this resonates with you, or if you have questions or wisdom to share, please comment below!

*This was originally described to me as “dotorg disease,” but I’m renaming it because…. well, pandemics.

Doing business in WordPress: missed opportunities

If you’re new to WordPress-based business, welcome! There’s never been a better time to help people achieve their goals with WordPress. The ecosystem is vast, and we’re a welcoming community.

An image of three people smiling, with arms around each other, at a conference.
Don’t we look welcoming? Here I am at WordCamp US 2016, with fellow WordPress enthusiasts Cory Miller (left) and Bob Dunn (right). I’m can’t quite make out who’s photobombing us in the background there. This photo was swiped from Bob’s social media.

I’ve worked with WordPress contributors and business owners, full time, since 2011. Anytime I meet someone who’s decided to build a business that depends on open source, I find myself hoping they’ve researched open source and its complexities. If this is you, and you’re not sure you’ve done that research, I hope this article is helpful to you!

Here are some things I think WordPress-based businesses need to know:

WordPress is Free and Powerful

Sometimes I wonder if WordPress-based businesses understand the incredible advantage that WordPress’ (lack of) price and open source foundation bring. The fact that WordPress is low-risk to try, and practically limitless to build on, has directly contributed to its ubiquity on the web. WordPress is a stable platform that can be used for nearly every purpose, which means WordPress-based businesses have an enormous built-in market.

What people often miss:

I frequently see WordPress-based businesses limit their potential by restricting how people use their theme or plugin. This effort requires a lot of work for a mediocre net return, which directly conflicts with the things that make WordPress appeal to so many people. The GPL makes WordPress possible, and it makes WordPress successful. When you try to limit your users’ rights with a non-GPL license, you’re limiting your work’s ability to grow with WordPress. Don’t work against the “selling points” of WordPress; support them and build on them, just like you do WordPress itself.

WordPress Changes

The software available at WordPress.org is stable, but ever-changing. This is great because it means that a lot of people are working to keep WordPress relevant, secure, and easy to work with. Anyone whose product or business depends on WordPress needs to keep up with the 3 or so releases per year, to know how and whether they will affect your business. It’s smart to notify your customers about upcoming changes to Core WordPress that will affect them, as well. Since you’re not in control of the Core roadmap, then your smartest move is to stay informed about how it will affect you.

What people often miss:

Remember, the unique solution that your business brings to WordPress (if it’s code-based at least) could be added to Core WordPress and available to all WordPress users, at any time. For this reason, it’s particularly important that your business not monetize access to the software. To have a truly resilient and successful WordPress-based company, monetize something that makes the software more powerful for your customers. What you’re selling should be so valuable that your customers would still pay you for it, even if your plugin or theme were merged into Core.

WordPress is Growing

This diagram shows the percentages of websites using various content management systems.
A snapshot from today’s W3techs.com page on content management statistics.

As of February 2021, WordPress powers 40% of the web. I believe that this growth is rooted in the power of open source, and that the road that brought us here was paved by the work of thousands of global WordPress enthusiasts. The opportunity to help WordPress grow is open to all, regardless of experience or background. The work of helping WordPress grow — by translating, writing documentation, organizing events, helping in the support forums, publishing videos, creating great training content, and so much more — helps everyone who uses WordPress and whose livelihoods depend on WordPress. This results in a culture and a community that understands that “a rising tide lifts all boats.” The WordPress financial ecosystem is one of the most friendly, collaborative, and welcoming that you’ll find.

What people often miss:

Companies that make brash, unsubstantiated business claims and regularly trash-talk competitors… do not flourish in WordPress. We don’t succeed here by trying to steal each other’s customers or features. We also help WordPress avoid the tragedy of the commons by giving back to the project. In WordPress, the most successful companies focus on growing the whole pie of the WordPress market (which then grows their slice as well).

Don’t miss your chance!

I firmly believe that WordPress is a great place to grow: as a person, as a leader, and as a business. If you haven’t considered getting involved in WordPress before, I encourage you to check out all the different ways to join us as a contributor. If you’re brand new to this WordPress thing, check out my list of resources for new and experienced WordPress enthusiasts. There’s lots to learn, but don’t worry, you’ve got time — we’re not going anywhere but up. 😉

What did I miss?

What other important things should businesses and people know about the WordPress ecosystem? Tell me about them in the comments!

Many thanks to Jonathan Wold for his feedback on this article!

What happens when you won’t admit (or don’t realize) you’re a leader

Hello, my name is Andrea, and I’m a recovering leader-in-denial.

I’ve spent much of my life stepping (usually reluctantly) into leadership roles, while also eagerly looking for someone else who could lead better than me — so I could stop being in charge! And that rarely happened, much to my surprise and chagrin, but only recently did I realize that was because… I am actually gifted at leadership.

“I smell imposter syndrome!” you’ll say — and you are correct! But having my own imposter syndrome pointed out to me… was not the thing that helped me get past it. The lightning bolt for me, was when I realized that my unwillingness to embrace a leadership role was causing me to screw up the actual work of leading.

Read on for my observations on how leading without admitting or realizing that you’re in charge… is really inefficient and hard!

  1. You’ll probably avoid doing *all* of the job. Many times I have stepped into a leadership role because I was in a group of people who had no direction. I would wait for someone to step up and take charge, and wait some more, and wait some MORE, and finally it was too much for me. So I would speak up and say, “Hey everyone, let’s go this way!” and then shut up again. Little bursts of leadership and strategy are usually better than nothing, but having a consistent and engaged leader is WAY more effective.
  2. You are more likely to undermine yourself and confuse others. If you think you shouldn’t be doing something, you are more likely to do that thing in a half-hearted or apologetic manner. Alternately, you might act passive aggressively, resenting that you’re in a position that you find uncomfortable. I don’t endorse an authoritarian approach to leadership, but you can lead collaboratively without apologizing for holding people accountable or setting limits.
  3. You probably think you’re failing if everyone isn’t happy all the time. Now, I like making people happy, and I think that leaders should care about the health and welfare of the people on their team. As a leader, you have a duty of care, but that duty does not always extend to “please all of the people, all of the time.” Leaders have to make choices, and some choices aren’t crowd-pleasers. Reluctant leaders or leaders-in-denial tend to stay in reaction mode — which is frequently conflict- and tough-decision averse.
  4. You are more likely to get in the way of your people. There’s a leadership adage that says, “when the conductor picks up an instrument, the orchestra falls apart.” The conductor doesn’t grab the violin when it’s time for the solo, or when the violinist is off key. If you’re laboring under the assumption that your primary value to the group is not that of leading, then you’re going to be looking for any excuse to put down that work and go back to individual contribution, sometimes by taking over the work of someone who might just need a little (or a lot of) support to do a better job.
  5. You won’t work on improving your skills. Good leadership is learned behavior, and learned behavior benefits from study and practice. By rejecting the fact that you’re a leader, you immediately cut yourself off from opportunities to get better at leadership in an intentional way. And when you do something badly, then you reinforce the idea that you’re not well-suited for it…. it’s a catch-22!
  6. You exempt yourself as a role model. People from marginalized groups don’t have a long list of excellent leaders to model ourselves after. That might even be one of the reasons you don’t see yourself as a leader — because you don’t look/sound/work like many of the leaders you saw while growing up. When people from traditionally marginalized groups courageously inhabit a leadership role despite all their misgivings, they change the very face of leadership.

I’ve learned a lot about myself on this leadership journey so far, which I love to do. I may have started out by accident — and I won’t say it’s the easiest thing I’ve ever done — but it’s a lot easier and more rewarding now that I’m bringing intent and awareness to the work. If any of this resonates with you, I’d love to hear about it! 

CMX Global online conference

It was a pleasure to present my conflict de-escalation workshop at today’s CMX Global online conference. If you signed up for the conference but missed my session, I think all sessions will be available to anyone who registered. If you didn’t register but are interested in the topic, I have published the script, bibliography and slides on this site. Enjoy!

The event used a platform called Hopin, which was quite interesting to try out. There is a “green room” tool that worked pretty well, and an “Expo” menu item, which allowed the event to offer online “sponsor booths” of a sort. There is also a Networking feature, which is straight-up video call roulette. While the one networking chat I did was quite pleasant, I can’t see myself using that feature very extensively in the future. It was anxiety-producing, not knowing who I was going to be dropped into conversation with. Unfortunately, the tool doesn’t seem to be accessible to keyboard-only users, so it’s not something we would seriously consider for online WordCamps.

The conference organizers tried a LOT of cool ideas, including live demos, networking, lunchtime stretching, an after-party DJ session, and after-conference mixology class. I’m sad I missed the Calligraphy 101 session at the end; that showed a lot of imagination.

It was great to participate both as a speaker and attendee, seeing people try out things I wouldn’t have attempted or hadn’t thought of. Kudos to the CMX team for carefully crafting this event, and to Beth McIntyre and Ann Marie Pawlicki for their attentive care of speakers! If you are looking to polish up your community organizing/management game, I recommend checking out CMX — they have some great resources (both free and behind the membership paywall) and plenty of helpful people.

The lost city of Bayocean

If you enjoy watching short documentaries, and you’re interested in learning more about Oregon, you might check out the Oregon Public Broadcasting show called Oregon Field Guide.

Tonight I watched a really interesting and very sad episode about the lost city of Bayocean, Oregon. Apparently in 1907, a family of real estate developers founded a resort town on a spit in Tillamook Bay, which they marketed as “The Atlantic City of the West.” The town was built, lots were sold and things were thriving… until a single jetty was built on the north side of the bay entrance. Because a southern jetty was not built, ocean currents immediately began eroding the land that Bayocean was built on, until eventually the town had to be abandoned. Everyone who had invested in the town or bought their retirement home there… lost everything.

Stories like this always make me so hungry for more detailed background on how these civil engineering decisions were made, and what motivated the people who made the final calls that basically condemned an entire resort development. (Not that I think it was necessarily the wrong decision; just because something is built doesn’t mean it has the right to exist or should be prioritized over other things that have also been built, or y’know, people.) 

Seemingly simple decisions can result in so many unforeseen consequences, and can affect people who weren’t considered when the decision was being made. I wonder what the relevant Army Corps of Engineers leadership regrets about Bayocean, if anything. (Maybe nothing at all!)