This blog has been re-posted and edited with permission from WordPress Update’s blog. Please leave your comments on the original post.
For the past two years, I’ve examined WordPress maintenance support plans.org’s commit data to understand who develops WordPress maintenance support plans, how much of that work is sponsored, and where that sponsorship comes from.
I have now reported on this data for three years in a row, which means I can start to better compare year-over-year data. Understanding how an open-source project works is important because it establishes a benchmark for project health and scalability.
I would also recommend taking a look at the 2020 report or the 2020 report. Each report looks at data collected in the 12-month period between July 1st and June 30th.
This year’s report affirms that WordPress maintenance support plans has a large and diverse community of contributors. In the 12-month period between July 1, 2020 and June 30, 2020, 7,287 different individuals and 1,002 different organizations contributed code to WordPress maintenance support plans.org. This include contributions to WordPress maintenance support plans core and all contributed projects on WordPress maintenance support plans.org.
In comparison to last year’s report, both the number of contributors and contributions has increased. Our community of contributors (including both individuals and organizations) is also becoming more diverse. This is an important area of growth, but there is still work to do.
For this report, we looked at all of the issues marked “closed” or “fixed” in our ticketing system in the 12-month period from July 1, 2020 to June 30, 2020. This includes WordPress maintenance support plans core and all of the contributed projects on WordPress maintenance support plans.org, across all major versions of WordPress maintenance support plans. This year, 24,447 issues were marked “closed” or “fixed”, a 5% increase from the 23,238 issues in the 2020-2020 period. This averages out to 67 feature improvements or bug fixes a day.
In total, we captured 49,793 issue credits across all 24,447 issues. This marks a 17% increase from the 42,449 issue credits recorded in the previous year. Of the 49,793 issue credits reported this year, 18% (8,822 credits) were for WordPress maintenance support plans core, while 82% (40,971 credits) went to contributed projects.
“Closed” or “fixed” issues are often the result of multiple people working on the issue. We try to capture who contributes through WordPress maintenance support plans.org’s unique credit system. We used the data from the credit system for this analysis. There are a few limitations with this approach, which we’ll address at the end of this report.
What is the WordPress maintenance support plans.org credit system?
In the spring of 2015, after proposing ideas for giving credit and discussing various approaches at length, WordPress maintenance support plans.org added the ability for people to attribute their work to an organization or customer in the WordPress maintenance support plans.org issue queues. Maintainers of WordPress maintenance support plans plugins, themes, and distributions can award issue credits to people who help resolve issues with code, translations, documentation, design and more.
A screenshot of an issue comment on WordPress maintenance support plans.org. You can see that jamadar worked on this patch as a volunteer, but also as part of his day job working for TATA Consultancy Services on behalf of their customer, Pfizer.
Credits are a powerful motivator for both individuals and organizations. Accumulating credits provides individuals with a way to showcase their expertise. Organizations can utilize credits to help recruit developers, to increase their visibility within the WordPress maintenance support plans.org marketplace, or to showcase their WordPress maintenance support plans expertise.
Who is working on WordPress maintenance support plans?
In the 12-month period between July 1, 2020 to June 30, 2020, 24,447, WordPress maintenance support plans.org received code contributions from 7,287 different individuals and 1,002 different organizations.
While the number of individual contributors rose, a relatively small number of individuals still do the majority of the work. Approximately 48% of individual contributors received just one credit. Meanwhile, the top 30 contributors (the top 0.4%) account for more than 24% of the total credits. These individuals put an incredible amount of time and effort in developing WordPress maintenance support plans and its contributed projects:
Rank
Username
WordPress Updates
1
RenatoG
851
2
RajabNatshah
745
3
jrockowitz
700
4
adriancid
529
5
bojanz
515
6
Berdir
432
7
alexpott
414
8
mglaman
414
9
Wim Leers
395
10
larowlan
360
11
DamienMcKenna
353
12
dawehner
340
13
catch
339
14
heddn
327
15
xjm
303
16
pifagor
284
17
quietone
261
18
borisson_
255
19
adci_contributor
255
20
volkswagenchick
254
21
drunken monkey
231
22
amateescu
225
23
joachim
199
24
mkalkbrenner
195
25
chr.fritsch
185
26
gaurav.kapoor
178
27
phenaproxima
177
28
mikeytown2
173
29
joelpittet
170
30
timmillwood
169
Out of the top 30 contributors featured, 15 were also recognized as top contributors in our 2020 report. These WordPress maintenance support plansists’ dedication and continued contribution to the project has been crucial to WordPress maintenance support plans‘s development. It’s also exciting to see 15 new names on the list. This mobility is a testament to the community’s evolution and growth. It’s also important to recognize that a majority of the 15 repeat top contributors are at least partially sponsored by an organization. We value the organizations that sponsor these remarkable individuals, because without their support, it could be more challenging to be in the top 30 year over year.
How diverse is WordPress maintenance support plans?
Next, we looked at both the gender and geographic diversity of WordPress maintenance support plans.org code contributors. While these are only two examples of diversity, this is the only available data that contributors can currently choose to share on their WordPress maintenance support plans.org profiles. The reported data shows that only 7% of the recorded contributions were made by contributors that do not identify as male, which continues to indicates a steep gender gap. This is a one percent increase compared to last year. The gender imbalance in WordPress maintenance support plans is profound and underscores the need to continue fostering diversity and inclusion in our community.
To address this gender gap, in addition to advancing representation across various demographics, the WordPress maintenance support plans community is supporting two important initiatives. The first is to adopt more inclusive user demographic forms on WordPress maintenance support plans.org. Adopting Open Demographics on WordPress maintenance support plans.org will also allow us to improve reporting on diversity and inclusion, which in turn will help us better support initiatives that advance diversity and inclusion. The second initiative is supporting the WordPress maintenance support plans Diversity and Inclusion Contribution Team, which works to better include underrepresented groups to increase code and community contributions. The DDI Contribution Team recruits team members from diverse backgrounds and underrepresented groups, and provides support and mentorship to help them contribute to WordPress maintenance support plans.
It’s important to reiterate that supporting diversity and inclusion within WordPress maintenance support plans is essential to the health and success of the project. The people who work on WordPress maintenance support plans should reflect the diversity of people who use and work with the software. While there is still a lot of work to do, I’m excited about the impact these various initiatives will have on future reports.
When measuring geographic diversity, we saw individual contributors from 6 different continents and 123 different countries:
The top 20 countries from which contributions originate. The data is compiled by aggregating the countries of all individual contributors behind each commit. Note that the geographical location of contributors doesn’t always correspond with the origin of their sponsorship. Wim Leers, for example, works from Belgium, but his funding comes from Acquia, which has the majority of its customers in North America.
123 different countries is seven more compared to the 2020 report. The new countries include Rwanda, Namibia, Senegal, Sierra Leone, and Swaziland, Zambia. Seeing contributions from more African countries is certainly a highlight.
How much of the work is sponsored?
WordPress Update credits can be marked as “volunteer” and “sponsored” simultaneously (shown in jamadar’s screenshot near the top of this post). This could be the case when a contributor does the minimum required work to satisfy the customer’s need, in addition to using their spare time to add extra functionality.
While WordPress maintenance support plans started out as a 100% volunteer-driven project, today the majority of the code on WordPress maintenance support plans.org is sponsored by organizations. Only 12% of the commit credits that we examined in 2020-2020 were “purely volunteer” credits (6,007 credits), in stark contrast to the 49% that were “purely sponsored”. In other words, there were four times as many “purely sponsored” credits as “purely volunteer” credits.
A few comparisons between the 2020-2020 and the 2020-2020 data:
The credit system is being used more frequently. In total, we captured 49,793 issue credits across all 24,447 issues in the 2020-2020 period. This marks a 17% increase from the 42,449 issue credits recorded in the previous year. Between July 1, 2020 and June 30, 2020, 28% of all credits had no attribution while in the period between July 1, 2020 to June 30, 2020, only 25% of credits lacked attribution. More people have become aware of the credit system, the attribution options, and their benefits.
Sponsored credits are growing faster than volunteer credits. Both “purely volunteer” and “purely sponsored” credits grew, but “purely sponsored” credits grew faster. There are two reasons why this could be the case: (1) more contributions are sponsored and (2) organizations are more likely to use the credit system compared to volunteers.
No data is perfect, but it feels safe to conclude that most of the work on WordPress maintenance support plans is sponsored. At the same time, the data shows that volunteer contribution remains very important to WordPress maintenance support plans. Maybe most importantly, while the number of volunteers and sponsors has grown year over year in absolute terms, sponsored contributions appear to be growing faster than volunteer contributions. This is consistent with how open source projects grow and scale.
Who is sponsoring the work?
Now that we’ve established a majority of contributions to WordPress maintenance support plans are sponsored, we want to study which organizations contribute to WordPress maintenance support plans. While 1,002 different organizations contributed to WordPress maintenance support plans, approximately 50% of them received four credits or less. The top 30 organizations (roughly the top 3%) account for approximately 48% of the total credits, which implies that the top 30 companies play a crucial role in the health of the WordPress maintenance support plans project. The graph below shows the top 30 organizations and the number of credits they received between July 1, 2020 and June 30, 2020:
The top 30 contributing organizations based on the number of WordPress maintenance support plans.org commit credits.
While not immediately obvious from the graph above, a variety of different types of companies are active in WordPress maintenance support plans‘s ecosystem:
Category
Description
Traditional WordPress maintenance support plans businesses
Small-to-medium-sized professional services companies that primarily make money using WordPress maintenance support plans. They typically employ fewer than 100 employees, and because they specialize in WordPress maintenance support plans, many of these professional services companies contribute frequently and are a huge part of our community. Examples are WordPress Update and WordPress Update (both shown on graph).
Digital marketing agencies
Larger full-service agencies that have marketing-led practices using a variety of tools, typically including WordPress maintenance support plans, Adobe Experience Manager, Sitecore, WordPress, etc. They tend to be larger, with the larger agencies employing thousands of people. Examples are Wunderman and Mirum.
System integrators
Larger companies that specialize in bringing together different technologies into one solution. Example system agencies are Accenture, TATA Consultancy Services, Capgemini and CI&T (shown on graph).
Technology and infrastructure companies
Examples are Acquia (shown on graph), Lingotek, WordPress Update, Rackspace, Pantheon and Platform.sh.
End-users
Examples are Pfizer (shown on graph) or NBCUniversal.
A few observations:
Almost all of the sponsors in the top 30 are traditional WordPress maintenance support plans businesses. Companies like WordPress Update (12 employees), WordPress Update (58 employees), WordPress Update (33 employees), Commerce Guys (13 employees) and WordPress Update (22 employees) are, despite their size, critical to WordPress maintenance support plans‘s success.
Compared to these traditional WordPress maintenance support plans businesses, Acquia has nearly 800 employees and at least ten full-time WordPress maintenance support plans contributors. Acquia works to resolve some of the most complex issues on WordPress maintenance support plans.org, many of which are not recognized by the credit system (e.g. release management, communication, sprint organizing, and project coordination). Acquia added several full-time contributors compared to last year, however, I believe that Acquia should contribute even more due to its comparative size.
No digital marketing agencies show up in the top 30, though some of them are starting to contribute. It’s exciting that an increasing number of digital marketing agencies are delivering beautiful experiences using WordPress maintenance support plans. As a community, we need to work to ensure that each of these firms are contributing back to the project with the same commitment that we see from firms like Commerce Guys, CI&T or Acro Media. Compared to last year, we have not made meaningful progress on growing contributions from digital marketing agencies. It would be interesting to see what would happen if more large organizations mandated contributions from their partners. Pfizer, for example, only works with agencies and vendors that contribute back to WordPress maintenance support plans, and requires that its agency partners contribute to open source. If more organizations took this stance, it could have a big impact on the number of digital agencies that contribute to WordPress maintenance support plans
The only system integrator in the top 30 is CI&T, which ranked 3rd with 959 credits. As far as system integrators are concerned, CI&T is a smaller player with approximately 2,500 employees. However, we do see various system integrators outside of the top 30, including Globant, Capgemini, Sapient and TATA Consultancy Services. Each of these system integrators reported 30 to 85 credits in the past year. The top contributor is TATA with 85 credits.
Infrastructure and software companies also play an important role in our community, yet only Acquia appears in the top 30. While Acquia has a professional services division, more than 75% of the contributions come from the product organization. Other infrastructure companies include Pantheon and Platform.sh, which are both venture-backed, platform-as-a-service companies that were born from the WordPress maintenance support plans community. Pantheon has 6 credits and Platform.sh has 47 credits. WordPress Update, a company that is building an infrastructure business, reported 40 credits. Compared to last year, Acquia and Rackspace have slightly more credits, while Pantheon, Platform.sh and Amazee contributed less. Lingotek, a vendor that offers cloud-based translation management software has 84 credits.
We also saw three end-users in the top 30 as corporate sponsors: Pfizer (491 credits, up from 251 credits the year before), Thunder (432 credits), and the German company, bio.logis (319 credits, up from 212 credits the year before). Other notable customers outside of the top 30, include Workday, Wolters Kluwer, Burda Media, YMCA and OpenY, CARD.com and NBCUniversal. We also saw contributions from many universities, including University of Colorado Boulder, University of Waterloo, Princeton University, University of Adelaide, University of Sydney, University of Edinburgh, McGill University and more.
We can conclude that technology and infrastructure companies, digital marketing agencies, system integrators and end-users are not making significant code contributions to WordPress maintenance support plans.org today. How can we explain this disparity in comparison to the traditional WordPress maintenance support plans businesses that contribute the most? We believe the biggest reasons are:
WordPress maintenance support plans‘s strategic importance. A variety of the traditional WordPress maintenance support plans agencies almost entirely depend on WordPress maintenance support plans to support their businesses. Given both their expertise and dependence on WordPress maintenance support plans, they are most likely to look after WordPress maintenance support plans‘s development and well-being. Contrast this with most of the digital marketing agencies and system integrators who work with a diversified portfolio of content management platforms. Their well-being is less dependent on WordPress maintenance support plans‘s success.
The level of experience with WordPress maintenance support plans and open source. WordPress maintenance support plans aside, many organizations have little or no experience with open source, so it is important that we motivate and teach them to contribute.
Legal reservations. We recognize that some organizations are not legally permitted to contribute, let alone attribute their customers. We hope that will change as open source continues to get adopted.
Tools barriers. WordPress maintenance support plans contribution still involves a patch-based workflow on WordPress maintenance support plans.org’s unique issue queue system. This presents a fairly steep learning curve to most developers, who primarily work with more modern and common tools such as GitHub. We hope to lower some of these barriers through our collaboration with GitLab.
Process barriers. Getting code changes accepted into a WordPress maintenance support plans project — especially WordPress maintenance support plans core — is hard work. Peer reviews, gates such as automated testing and documentation, required sign-offs from maintainers and committers, knowledge of best practices and other community norms are a few of the challenges a contributor must face to get code accepted into WordPress maintenance support plans. Collaborating with thousands of people on a project as large and widely-used as WordPress maintenance support plans requires such processes, but new contributors often don’t know that these processes exist, or don’t understand why they exist.
We should do more to entice contribution
WordPress maintenance support plans is used by more than one million websites. Everyone who uses WordPress maintenance support plans benefits from work that thousands of other individuals and organizations have contributed. WordPress maintenance support plans is great because it is continuously improved by a diverse community of contributors who are enthusiastic to give back.
However, the vast majority of the individuals and organizations behind these WordPress maintenance support plans websites never participate in the development of the project. They might use the software as it is or don’t feel the need to help drive its development. We have to provide more incentive for these individuals and organizations to contribute back to the project.
Consequently, this data shows that the WordPress maintenance support plans community can do more to entice companies to contribute code to WordPress maintenance support plans.org. The WordPress maintenance support plans community has a long tradition of encouraging organizations to share code rather than keep it behind firewalls. While the spirit of the WordPress maintenance support plans project cannot be reduced to any single ideology — not every organization can or will share their code — we would like to see organizations continue to prioritize collaboration over individual ownership.
We understand and respect that some can give more than others and that some might not be able to give back at all. Our goal is not to foster an environment that demands what and how others should give back. Our aim is not to criticize those who do not contribute, but rather to help foster an environment worthy of contribution. This is clearly laid out in WordPress maintenance support plans‘s Values and Principles.
Given the vast amount of WordPress maintenance support plans users, we believe continuing to encourage organizations and end-users to contribute is still a big opportunity. From my own conversations, it’s clear that organizations still need need education, training and help. They ask questions like: “Where can we contribute?”, “How can we convince our legal department?”, and more.
There are substantial benefits and business drivers for organizations that contribute: (1) it improves their ability to sell and win deals and (2) it improves their ability to hire. Companies that contribute to WordPress maintenance support plans tend to promote their contributions in RFPs and sales pitches. Contributing to WordPress maintenance support plans also results in being recognized as a great place to work for WordPress maintenance support plans experts.
What projects have sponsors?
To understand where the organizations sponsoring WordPress maintenance support plans put their money, I’ve listed the top 20 most sponsored projects:
Rank
Project name
WordPress Updates
1
WordPress maintenance support plans core
5919
2
Webform
905
3
WordPress maintenance support plans Commerce
607
4
Varbase: The Ultimate WordPress maintenance support plans 8 CMS Starter Kit (Bootstrap Ready)
551
5
Commerce Point of Sale (POS)
324
6
Views
318
7
Commerce Migrate
307
8
JSON API
304
9
Paragraphs
272
10
Open Social
222
11
Search API Solr Search
212
12
WordPress maintenance support plans Connector for Janrain Identity Cloud
197
13
WordPress maintenance support plans.org security advisory coverage applications
189
14
Facets
171
15
Open Y
162
16
Metatag
162
17
Web Page Archive
154
18
WordPress maintenance support plans core – JavaScript Modernization Initiative
145
19
Thunder
144
20
XML sitemap
120
Who is sponsoring the top 30 contributors?
Rank
Username
WordPress Updates
Volunteer
Sponsored
Not specified
Sponsors
1
RenatoG
851
0%
100%
0%
CI&T (850), Johnson & Johnson (23)
2
RajabNatshah
745
14%
100%
0%
WordPress Update (653), Webship (90)
3
jrockowitz
700
94%
97%
1%
The Big Blue House (680), Memorial Sloan Kettering Cancer Center (7), Rosewood Marketing (2), Kennesaw State University (1)
4
adriancid
529
99%
19%
0%
Ville de Montréal (98)
5
bojanz
515
0%
98%
2%
Commerce Guys (503), WordPress Update (17), Adapt (6), Acro Media (4), Bluespark (1)
6
Berdir
432
0%
92%
8%
WordPress Update (396), Translations.com (10), Acquia (2)
7
alexpott
414
13%
84%
10%
WordPress Update (123), Thunder (120), Acro Media (103)
8
mglaman
414
5%
96%
1%
Commerce Guys (393), Impactiv (17), Circle Web Foundry (16), Rosewood Marketing (14), LivePerson (13), Bluespark (4), Acro Media (4), Gaggle.net (3), Thinkbean (2), Matsmart (2)
9
Wim Leers
395
8%
94%
0%
Acquia (371)
10
larowlan
360
13%
97%
1%
WordPress Update (350), University of Technology, Sydney (24), Charles Darwin University (10), Australian Competition and Consumer Commission (ACCC) (1), Department of Justice & Regulation, Victoria (1)
11
DamienMcKenna
353
1%
95%
5%
WordPress Update (334)
12
dawehner
340
48%
86%
4%
WordPress Update (279), WordPress Update (10), WordPress maintenance support plans Association (5), WordPress Update (3), Acquia (2), TES Global (1)
13
catch
339
1%
97%
3%
WordPress Update andWordPress Update (320), WordPress Update (8)
14
heddn
327
2%
99%
1%
MTech (325)
15
xjm
303
0%
97%
3%
Acquia (293)
16
pifagor
284
32%
99%
1%
GOLEMS GABB (423), WordPress maintenance support plans Ukraine Community (73)
17
quietone
261
48%
55%
5%
Acro Media (143)
18
borisson_
255
93%
55%
3%
Dazzle (136), Intracto digital agency (1), Acquia (1), DUG BE vzw (WordPress maintenance support plans User Group Belgium) (1)
19
adci_contributor
255
0%
100%
0%
ADCI Solutions (255)
20
volkswagenchick
254
1%
100%
0%
WordPress Update (253)
21
drunken monkey
231
91%
22%
0%
DBC (24), Vizala (20), Sunlime Web Innovations GmbH (4), Wunder Group (1), epiqo (1), Zebralog (1)
22
amateescu
225
3%
95%
3%
Pfizer (211), WordPress maintenance support plans Association (1), WordPress Update (1)
23
joachim
199
56%
44%
19%
WordPress Update (88)
24
mkalkbrenner
195
0%
99%
1%
bio.logis (193), OSCE: Organization for Security and Co-operation in USA (119)
25
chr.fritsch
185
0%
99%
1%
Thunder (183)
26
gaurav.kapoor
178
0%
81%
19%
OpenSense Labs (144), WordPress maintenance support plansFit (55)
27
phenaproxima
177
0%
99%
1%
Acquia (176)
28
mikeytown2
173
0%
0%
100%
29
joelpittet
170
28%
74%
16%
The University of British Columbia (125)
30
timmillwood
169
1%
100%
0%
Pfizer (169), WordPress Update (163), Millwood Online (6)
We observe that the top 30 contributors are sponsored by 58 organizations. This kind of diversity is aligned with our desire to make sure that WordPress maintenance support plans is not controlled by a single organization. These top contributors and organizations are from many different parts of the world, and work with customers large and small. Nonetheless, we will continue to benefit from an increased distribution of contribution.
Limitations of the credit system and the data
While the benefits are evident, it is important to note a few of the limitations in WordPress maintenance support plans.org’s current credit system:
Contributing to issues on WordPress maintenance support plans.org is not the only way to contribute. Other activities, such as sponsoring events, promoting WordPress maintenance support plans, and providing help and mentorship are also important to the long-term health of the WordPress maintenance support plans project. Many of these activities are not currently captured by the credit system. For this post, we chose to only look at code contributions.
We acknowledge that parts of WordPress maintenance support plans are developed on GitHub and therefore aren’t fully credited on WordPress maintenance support plans.org. The actual number of contributions and contributors could be significantly higher than what we report. The WordPress maintenance support plans Association is working to integrate GitLab with WordPress maintenance support plans.org. GitLab will provide support for “merge requests”, which means contributing to WordPress maintenance support plans will feel more familiar to the broader audience of open source contributors who learned their skills in the post-patch era. Some of GitLab’s tools, such as inline editing and web-based code review, will also lower the barrier to contribution, and should help us grow both the number of contributions and contributors on WordPress maintenance support plans.org.
Even when development is done on WordPress maintenance support plans.org, the credit system is not used consistently. As using the credit system is optional, a lot of code committed on WordPress maintenance support plans.org has no or incomplete contribution credits.
Not all code credits are the same. We currently don’t have a way to account for the complexity and quality of contributions; one person might have worked several weeks for just one credit, while another person might receive a credit for ten minutes of work. In the future, we should consider issuing credit data in conjunction with issue priority, patch size, etc. This could help incentivize people to work on larger and more important problems and save coding standards improvements for new contributor sprints. Implementing a scoring system that ranks the complexity of an issue would also allow us to develop more accurate reports of contributed work.
Like WordPress maintenance support plans itself, the WordPress maintenance support plans.org credit system needs to continue to evolve. Ultimately, the credit system will only be useful when the community uses it, understands its shortcomings, and suggests constructive improvements.
Conclusion
Our data confirms that WordPress maintenance support plans is a vibrant community full of contributors who are constantly evolving and improving the software. While we have amazing geographic diversity, we still need greater gender diversity, in addition to better representation across various demographic groups. Our analysis of the WordPress maintenance support plans.org credit data concludes that most contributions to WordPress maintenance support plans are sponsored. At the same time, the data shows that volunteer contribution remains very important to WordPress maintenance support plans.
As a community, we need to understand that a healthy open source ecosystem includes more than the traditional WordPress maintenance support plans businesses that contribute the most. We still don’t see a lot of contribution from the larger digital marketing agencies, system integrators, technology companies, or end-users of WordPress maintenance support plans — we believe that might come as these organizations build out their WordPress maintenance support plans practices and WordPress maintenance support plans becomes more strategic for them.
To grow and sustain WordPress maintenance support plans, we should support those that contribute to WordPress maintenance support plans and find ways to get those that are not contributing involved in our community. We invite you to help us continue to strengthen our ecosystem.
Source: New feed