Skip to content

Where should you make your first open source contribution, and who decides it counts?

Compare projects before your first open source contribution. All twelve projects I compared list a first step without code. Who records that work is another matter, and my take is that work that is not code gets counted last.

Courtney
Nov 12, 202615 min read

ou’d compare two phone plans before you sign, so compare projects before your first open source contribution. In all twelve projects I compared, that first step can be something other than code. Whether it counts is a separate question. My take, which is only mine, is that work that isn’t code gets counted last, because work no tool logs waits for a person to record it, and much of that work isn’t code.

Disclosure first: I work at Pantheon, which hosts sites built on WordPress or Drupal. I used to work at GoDaddy and held WordPress team roles. The full list comes before the evidence.

Key takeaways

  • The big picture: All twelve open source projects compared here accept a first contribution that needs no code.
  • By the numbers: 50 of the 84 testers WordPress thanked for version 7.1 were new contributors with no Test Contributor badge yet.1
  • Why it matters: Tools log commits and issues on their own, plus some badges. But event help, mentoring and work done in Slack wait for a person.
  • Yes, but: Drupal and TYPO3 now count some work beyond code on purpose.
/* Zine treatment for the Yoast AI summary (2026-11-06). Uses theme tokens so dark mode follows. Move to courtneyr-child once approved. */ .wp-block-yoast-seo-ai-summarize{position:relative;background:var(--cr-surface-elevated);color:var(--cr-ink);border:var(--cr-border-thick);box-shadow:var(--cr-shadow-hard);padding:2.1rem 1.5rem 1rem;margin:2.75rem 0 2.25rem;counter-reset:cr-takeaway} .wp-block-yoast-seo-ai-summarize>h2{position:absolute;top:-.95rem;left:1rem;margin:0;padding:.25rem .95rem;background:var(--cr-tape);color:var(--cr-tape-ink);font-family:var(--cr-font-accent);font-size:var(--cr-text-sm);font-weight:700;letter-spacing:.12em;text-transform:uppercase;line-height:1.3;transform:rotate(var(--cr-rotate-1));box-shadow:1px 1px 0 var(--cr-border-strong)} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list{list-style:none;padding:0;margin:0} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li{counter-increment:cr-takeaway;position:relative;margin:0;padding:.75rem 0 .75rem 2.6rem;border-top:1px dashed var(--cr-paper-rule);font-size:1rem;line-height:1.5} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li:first-child{border-top:0;padding-top:.2rem} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li::before{content:counter(cr-takeaway,decimal-leading-zero)!important;display:block!important;position:absolute!important;left:0!important;top:.95rem!important;transform:none!important;font-family:var(--cr-font-mono);font-size:var(--cr-text-xs);font-weight:700;letter-spacing:.05em;color:var(--cr-ink-muted);background:none!important;width:auto!important;height:auto!important} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list>li:first-child::before{top:.4rem!important} .wp-block-yoast-seo-ai-summarize ul.yoast-ai-summarize-list strong{font-family:var(--cr-font-accent);font-weight:700;box-shadow:var(--cr-shadow-marker);-webkit-box-decoration-break:clone;box-decoration-break:clone;padding:0 .1em}

🎟️ Which was my first contribution, 2009 or 2014?

In May 2009, I volunteered at WordCamp Mid-Atlantic in Baltimore, a WordPress conference run by volunteers.2 My job was checking attendees in. Nothing recorded it that I know of: no badge, no credit list. So ask me for my first contribution, and I’ll say 2014.

On Friday, August 1, 2014, WordCamp NYC held a Contributor Day, a day of group work on the project, at New York University.3 There, I started a lesson module on post formats for the Training Team, which made WordPress teaching materials. Five days later, the team’s public recap listed it: “A new module created by Courtney Robertson added at WCNYC contribute day!”4 Today, WordPress lists event volunteering as a contribution path, and its guide says “No prior experience is required.”5 So by the 2026 guide, my first open source contribution was that 2009 shift. By the 2009 record, it never happened. The record starts in 2014.

!First open source contribution sketch: a volunteer at a CHECK IN desk, a table sign asking DOES THIS COUNT? [PNG, 1.40 MB]

Checking attendees in, 2009: no badge, no credit list. Illustration made with ChatGPT at my direction from the series cast.

🧭 How I checked, and where I stand

So on November 11, 2026, I read the contribute pages of twelve open source projects to see where a first contribution can start. Six build websites: Backdrop CMS, Drupal, Ghost, Joomla, TYPO3 and WordPress. MariaDB and MySQL are databases. Node.js runs JavaScript outside the browser, and PHP is the language WordPress is written in. W3C and WHATWG set web standards. My post on how I chose the projects explains the picks. I read each project’s own pages and didn’t interview anyone. (Both comparison tables live on the Merge Conflicts data page.)

🧷 My ties to open source contribution

My ties touch this count directly. I work at Pantheon, a WordPress and Drupal host that competes with WP Engine, another WordPress host. It also competes with WordPress VIP, the enterprise service from Automattic, the company behind WordPress.com. Pantheon is a platinum Drupal Certified Partner.6 At GoDaddy, I started and ran its Five for the Future program, which pledges staff time to WordPress, until July 2026.

Separately, I chose which groups GoDaddy funded:

  • The PHP Foundation, which pays developers to work on the PHP language.
  • OpenJS, the foundation behind Node.js and other JavaScript projects.
  • W3C, the World Wide Web Consortium, a web standards body.
  • PHP_CodeSniffer, a tool that checks code style.
  • The WPOCC, a WordPress community collective where I’m a co-founding board member.

I’m also an active member of the Technical Steering Committee for FAIR, the FAIR Package Manager, which distributes WordPress plugins and themes. It’s a Linux Foundation project; the Linux Foundation is a nonprofit that hosts open source projects.

🧷 Ties from contributing to WordPress

Three more ties are specific to this post. I was a faculty member and a team rep on the Training Team, whose badges are assigned by hand, and I’m not active on the team now.7 I helped write the 2023 proposal for WordPress’s mentorship pilot, which credits me as courane01.8 And I worked with the Sustainability Team on a dashboards project; a news report quotes me objecting to that team’s closure.9

I taught, wrote lesson plans and organized. In my experience, the counting arrived for commits first and for everything else later. (A commit is a saved change to a project’s code.)

🚪 Where a first contribution can start without code

Every project I read names a door that needs no code. You can triage one issue report in Drupal, which means sorting a new bug report. You can run PHP’s test suite on a release candidate, a nearly final test build, or review a draft standard at W3C, the web’s main standards body, and send comments.101112 WordPress sorts its starter guides by skill in a Contribution Pathways index, whose About page went up in March 2026.13 Its guides include answering a WordPress forum question, and that guide’s only setup note is to get your accounts ready.1415

The gates differ once you send code. MySQL needs the Oracle Contribution Agreement signed before Oracle takes your code.16 WHATWG, which writes the HTML standard, asks people who work in web technology to have their employer sign.17 For WordPress, I found no agreement to sign, and the same goes for PHP and Backdrop. WordPress’s licensing page says contributing licenses your work, but no page I read says “no agreement” in those words, so that part is my reading.18

So every open source project here has a door for a first contribution that needs no code. The doors for code have more locks. The harder question comes after you walk through one.

🏅 Who decides your open source contribution counts in WordPress

In WordPress, some work earns credit on its own, if a script can see it. One translated string or one published photo earns a profile badge.19 Docs, Training, Design, Accessibility, Test and Community badges come from a person instead. The handbook for Core, the team that builds WordPress’s main software, says design, writing, user testing and good bug reports deserve props, Core’s word for contributor credit, but a maintainer (someone who reviews and accepts changes) has to add them.20 The same page says work done in Slack isn’t compiled automatically.

Testers show where that line falls, because their work is partly logged. For WordPress 7.1, the Test Team, which tests each release, thanked 84 testers by username, and 50 of them had no Test Contributor badge yet.21 The badge has a bar. One path is five test reports on Trac or GitHub, then a request that a Test Team Rep, one of the team’s elected leads, reviews weekly.22 (Trac is WordPress’s ticket tracker, and GitHub is a site that hosts code and tracks issues.) The tracker behind the thank you post scans Trac. I can’t tell how many of the 50 already qualify.

Check your own WordPress.org profile and count the badges. Then ask which ones a person had to hand you.

🧮 Why I think commits got counted first

My guess is that code got counted first because software already reads it. A 2021 study compared All Contributors lists, which credit work beyond code, with GitHub’s data in 2,855 projects. The lists named more people than GitHub’s commit-based contributor panel in 29.5% of them. But GitHub’s full activity log named more people than the lists in over 90%.23 That log also records issues and comments. So automatic logs catch more people whether or not the work is code. The work that slips is the work no tool logs.

Still, people notice the gap from inside, because the logs miss so much. In 2021, Drupal’s project lead wrote about what its credit data misses, and the list included event organizers and speakers, plus translators.24 Drupal’s written policy credits triage, testing, design and mentoring. Even so, a maintainer still ticks each name.25 The PHP Foundation says it hires only for the core language. Documentation and translation sit outside its hiring.26

🗳️ When credit for a contribution turns into a vote

That order matters when credit turns into a vote. PHP’s policy gives a vote on proposals to people with php.net accounts who have contributed code, and those voters choose community representatives, such as lead developers of projects built on PHP.27 WordPress teams elect their reps, while commit access (the right to add changes to the main code yourself) takes a public nomination and the project lead’s approval.2829 (For who has held those rep seats, counted by employer, see my count of WordPress leadership seats.) In PHP and WordPress, then, the routes to a vote and to commit access run mostly through code, and team rep elections are the exception. Do translators hold fewer of those routes? Nothing I read measures it.

⏳ How long a first contribution waits for an answer

This is a different wait: for a reply, not for credit. What surprised me most was MariaDB. It answered 246 of 777 new pull requests, or proposed code changes, from January to June 2026, and 174 got no answer. The rest were drafts, or merged or closed by their authors.30 MariaDB is the only project I read that publishes both a target and its own numbers, and its target is a first response within “7 calendar days.”31 But the target page shows no publication date, so I can’t tell whether it applied to those months. The count also covers every pull request, not only a newcomer’s first one.

WordPress publishes unreplied tickets by component instead. On November 11, 2026, its Core components page showed tickets with no replies by component: Editor had 115, General 91, Taxonomy 50.32 In April 2026, a project post gave the stated reason for new onboarding work: “Teams want help, but we’re losing people at the door.”33 (Every project has a door. Fewer have a doorbell.)

One study helps here, at its own size. Across 111,094 pull requests in ten projects, newcomers who got a human reply within a day were more likely to open another.34 That’s an association, and it’s about code. It doesn’t prove a fast reply keeps a translator.

⚖️ The best case that work beyond code already counts

The best case against my claim is that several open source projects now count work beyond code on purpose. Drupal has credited issue work for years. In 2025, it moved that credit into a separate Contribution Records system for two reasons. Issues on GitLab, the code site Drupal moved to, couldn’t attribute credit. And many contributions need no code.35 TYPO3’s monthly numbers sit documentation and translation next to core patches. July 2026 listed 6,384 words translated on Crowdin, a translation platform.36 And in WordPress, one translated string earns a badge with no request at all.37

Those systems are real, and they can catch work that a commit log would miss. Still, much of the credit waits on a person: a Drupal maintainer ticks names, and a person grants many WordPress badges. CHAOSS, a project that publishes open source health metrics, suggests a dedicated log for work that isn’t code.38 A log is something a person has to keep. No study I found measures what share of open source work isn’t code. So “last” is my judgment, not a finding. (Nobody I found has measured it, which is its own small irony.)

🧮 What counting each contribution costs

Counting has a cost as well. Drupal’s credit page gives an event’s organizer 220 credits for a DrupalCon and 25 for a local meetup.39 (DrupalCon is Drupal’s main conference.) The page sits in Drupal’s Marketplace guidelines, and its title ties credit to “Impact on Ranking.” Organizations are ranked by their weighted credits.40 I’d expect that once a count feeds a ranking, people chase the count.

🔍 What I still can’t answer about who stays

What I still can’t answer is how many people stay after a first contribution to an open source project. WordPress’s 2023 mentorship proposal set two targets: at least 80% of the first cohort would graduate, and at least half would keep contributing three months later.41 Eleven of 13 graduated, above the 80% target.42 About four months later, a post said at least 7 of the 13 were still contributing, which is more than half.43 But no post I found reports the three month check itself. My name is on that proposal, and I don’t know whether the three month check ran. (I’d like to.)

Outside WordPress, a study of 367 students in Google Summer of Code, Google’s paid summer program for student developers, found about 15% still committing code a year later.44 If you know where a project counts who stays, send me the page. I’ll add it.

🧭 Questions to ask before your first contribution

For your first contribution, pick an open source project that says who records your work. Open two contribute pages and ask these of each:

  1. What’s the first step that needs no code?
  2. What do I sign, and does my employer sign too?
  3. Does the project publish how long a first reply takes?
  4. Who records this work, and is it automatic?

If a page doesn’t say who credits your work, that’s your first finding.

🙋 Frequently asked questions

✍️ Does Node.js need my legal name?

No. It asks you to sign off on every commit with one line, and it doesn’t require a legal name.45

📜 Does a W3C typo fix need a patent promise?

No. W3C asks outsiders for a patent commitment on substantive changes, and typo fixes pass without one.46

💬 How many forum replies earn the WordPress Support badge?

The contribution guide says 50.47 The Support Team’s handbook, updated in July 2025, still lists more than 400.48 When you make your first open source contribution, who will write your name down?

Footnotes (48)
  1. Make WordPress Test. “Thank You to the WordPress 7.1 Test Contributors.” make.wordpress.org. 2026-09-18. https://make.wordpress.org/test/2026/09/18/thank-you-to-the-wordpress-7-1-test-contributors/. Accessed 2026-11-11. ↩︎
  2. WebDevStudios. “WordCamp Mid-Atlantic 2009 Recap.” webdevstudios.com. 2009-05-18. https://webdevstudios.com/2009/05/18/wordcamp-mid-atlantic-2009-recap/. Accessed 2026-11-11. ↩︎
  3. WordCamp NYC 2014. “Schedule.” nyc.wordcamp.org. 2014. https://nyc.wordcamp.org/2014/schedule/. Accessed 2026-11-11. ↩︎
  4. Make WordPress Training. “Recap of August 5 2014 Meeting.” make.wordpress.org. 2014-08-06. https://make.wordpress.org/training/2014/08/06/recap-of-august-5-2014-meeting-status-of/. Accessed 2026-10-28. ↩︎
  5. Make WordPress. “Volunteer at a WordPress Event.” make.wordpress.org. Updated 2026-10-14. https://make.wordpress.org/handbook/pathways/organize/volunteer-at-a-wordpress-event/. Accessed 2026-11-11. ↩︎
  6. Drupal Association. “Drupal Certified Partners.” Drupal.org. https://new.drupal.org/drupal-services. Accessed 2026-11-20. ↩︎
  7. Make WordPress Meta. “Profile Badges.” make.wordpress.org. Updated 2026-10-20. https://make.wordpress.org/meta/handbook/documentation/profile-badges/. Accessed 2026-11-11. ↩︎
  8. Hari Shanker R. “WordPress Contributor Mentorship Program: Pilot Program Proposal.” Make WordPress Project. 2023-05-17. https://make.wordpress.org/project/2023/05/17/wordpress-contributor-mentorship-program-pilot-program-proposal/. Accessed 2026-11-11. ↩︎
  9. Morey, Rae. “Mullenweg Shuts Down WordPress Sustainability Team, Igniting Backlash.” The Repository. 2025-01-10. https://www.therepository.email/mullenweg-shuts-down-wordpress-sustainability-team-igniting-backlash. Accessed 2026-11-11. ↩︎
  10. Drupal. “Getting started contributing.” drupal.org. Updated 2025-10-16. https://www.drupal.org/community/contributor-guide/reference-information/quick-info/getting-started-contributing. Accessed 2026-11-11. ↩︎
  11. PHP. “Get Involved.” php.net. No date shown. https://www.php.net/get-involved.php. Accessed 2026-11-11. ↩︎
  12. W3C. “Get involved.” w3.org. No date shown. https://www.w3.org/get-involved/. Accessed 2026-11-11. ↩︎
  13. Make WordPress. “About Pathways.” make.wordpress.org. 2026-03-26. https://make.wordpress.org/handbook/pathways/about/. Accessed 2026-11-11. ↩︎
  14. Make WordPress. “Contribution Pathways.” make.wordpress.org. Updated 2026-10-14. https://make.wordpress.org/handbook/pathways/. Accessed 2026-11-11. ↩︎
  15. Make WordPress. “Answer WordPress Support Questions.” make.wordpress.org. Updated 2026-10-26. https://make.wordpress.org/handbook/pathways/write/answer-wordpress-questions/. Accessed 2026-11-11. ↩︎
  16. Oracle. “Contributing to MySQL.” dev.mysql.com. 2026. https://dev.mysql.com/community/contributing/. Accessed 2026-11-11. ↩︎
  17. WHATWG. “Participant Agreement.” participate.whatwg.org. No date shown. https://participate.whatwg.org/agreement. Accessed 2026-11-11. ↩︎
  18. Make WordPress. “Licensing.” make.wordpress.org. 2026-10-26. https://make.wordpress.org/handbook/licensing/. Accessed 2026-11-11. ↩︎
  19. Make WordPress Meta. “Profile Badges.” make.wordpress.org. Updated 2026-10-20. https://make.wordpress.org/meta/handbook/documentation/profile-badges/. Accessed 2026-11-11. ↩︎
  20. Make WordPress Core. “Contributor Attribution (Props).” make.wordpress.org. Updated 2025-12-22. https://make.wordpress.org/core/handbook/best-practices/contributor-attribution-props/. Accessed 2026-11-11. ↩︎
  21. Make WordPress Test. “Thank You to the WordPress 7.1 Test Contributors.” make.wordpress.org. 2026-09-18. https://make.wordpress.org/test/2026/09/18/thank-you-to-the-wordpress-7-1-test-contributors/. Accessed 2026-11-11. ↩︎
  22. Make WordPress Test. “Test Team Profile Badges.” make.wordpress.org. Updated 2026-10-14. https://make.wordpress.org/test/handbook/test-team-profile-badges/. Accessed 2026-11-12. ↩︎
  23. Young, J.-G., Casari, A., McLaughlin, K., Trujillo, M. Z., Hébert-Dufresne, L., Bagrow, J. P. “Which contributions count? Analysis of attribution in open source.” MSR 2021. 2021. https://ar5iv.labs.arxiv.org/html/2103.11007. Accessed 2026-11-11. ↩︎
  24. Buytaert, Dries. “Who sponsors Drupal development? (2020-2021 edition).” dri.es. 2021. https://dri.es/who-sponsors-drupal-development-2021. Accessed 2026-11-11. ↩︎
  25. Drupal. “Granting credit to issue contributors.” drupal.org. Updated 2026-10-29. https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquette/granting-credit-to-issue-contributors. Accessed 2026-11-11. ↩︎
  26. The PHP Foundation. “2027 Applications for Contractors are Open.” thephp.foundation. 2026-09-30. https://thephp.foundation/blog/2026/09/30/applications-for-2027-are-open/. Accessed 2026-11-11. ↩︎
  27. PHP. “Feature Proposals policy.” github.com. No date shown. https://raw.githubusercontent.com/php/policies/main/feature-proposals.rst. Accessed 2026-11-11. ↩︎
  28. Make WordPress. “Team Reps.” make.wordpress.org. Updated 2026-09-28. https://make.wordpress.org/updates/team-reps/. Accessed 2026-11-11. ↩︎
  29. Desrosiers, Jonathan. “Aligning Committer-Level Access Across the Code Base.” Make WordPress Core. 2024-07-22. https://make.wordpress.org/core/2024/07/22/aligning-committer-level-access-across-the-code-base/. Accessed 2026-11-11. ↩︎
  30. MariaDB Foundation. “MariaDB Contribution Statistics, January to June 2026.” mariadb.org. 2026-08-25. https://mariadb.org/mariadb-contribution-statistics-january-june-2026/. Accessed 2026-11-11. ↩︎
  31. MariaDB Foundation. “Response Times.” mariadb.org. No date shown. https://mariadb.org/governance/governance-response-times/. Accessed 2026-11-11. ↩︎
  32. Make WordPress Core. “Components.” make.wordpress.org. No date shown. https://make.wordpress.org/core/components/. Accessed 2026-11-11. ↩︎
  33. Velda. “Help us help others contribute to WordPress.” Make WordPress Project. 2026-04-23. https://make.wordpress.org/project/2026/04/23/help-us-help-others-contribute-to-wordpress/. Accessed 2026-11-11. ↩︎
  34. Hasan, K. A., Macedo, M., Tian, Y., Adams, B., Ding, S. “Understanding the Time to First Response in GitHub Pull Requests.” arXiv. 2023-04. https://ar5iv.labs.arxiv.org/html/2304.08426. Accessed 2026-11-11. ↩︎
  35. García-Linares, Fran. “The new Contribution Records system.” drupal.org. 2025-07-28. https://www.drupal.org/node/3537881. Accessed 2026-11-12. ↩︎
  36. TYPO3. “TYPO3 Contribution in Numbers: July 2026.” news.typo3.com. 2026. https://news.typo3.com/article/typo3-contribution-in-numbers-july-2026. Accessed 2026-11-11. ↩︎
  37. Make WordPress Meta. “Profile Badges.” make.wordpress.org. Updated 2026-10-20. https://make.wordpress.org/meta/handbook/documentation/profile-badges/. Accessed 2026-11-11. ↩︎
  38. CHAOSS. “Types of Contributions.” chaoss.community. Updated 2024-11-27. https://chaoss.community/kb/metric-types-of-contributions/. Accessed 2026-11-12. ↩︎
  39. Drupal. “Contribution Credit Weight and Impact on Ranking.” drupal.org. Updated 2026-07-23. https://drupal.org/contribution-credit. Accessed 2026-11-12. ↩︎
  40. Drupal. “Contribution Credit Weight and Impact on Ranking.” drupal.org. Updated 2026-07-23. https://drupal.org/contribution-credit. Accessed 2026-11-12. ↩︎
  41. Hari Shanker R. “WordPress Contributor Mentorship Program: Pilot Program Proposal.” Make WordPress Project. 2023-05-17. https://make.wordpress.org/project/2023/05/17/wordpress-contributor-mentorship-program-pilot-program-proposal/. Accessed 2026-11-11. ↩︎
  42. Hari Shanker R. “The Inaugural Cohort of the WordPress Contributor Mentorship Program has Concluded.” Make WordPress Project. 2023-08-11. https://make.wordpress.org/project/2023/08/11/the-inaugural-cohort-of-the-wordpress-contributor-mentorship-program-has-concluded/. Accessed 2026-11-11. ↩︎
  43. Make WordPress Project. “WordPress End of Year Celebrations.” make.wordpress.org. 2023-12-22. https://make.wordpress.org/project/2023/12/22/wordpress-end-of-year-celebrations/. Accessed 2026-11-11. ↩︎
  44. Silva, J. O., Wiese, I. S., Steinmacher, I., Gerosa, M. A. “Students’ Engagement in Open Source Projects: An Analysis of Google Summer of Code.” SBES ’17. 2017. https://doi.org/10.1145/3131151.3131156. Accessed 2026-11-11. ↩︎
  45. Node.js. “Pull requests.” github.com. No date shown. https://raw.githubusercontent.com/nodejs/node/main/doc/contributing/pull-requests.md. Accessed 2026-11-11. ↩︎
  46. W3C. “W3C Process Document, section 6.2.7.” w3.org. 2025-08-18. https://www.w3.org/policies/process/#contributor-license. Accessed 2026-11-11. ↩︎
  47. Make WordPress. “Answer WordPress Support Questions.” make.wordpress.org. Updated 2026-10-26. https://make.wordpress.org/handbook/pathways/write/answer-wordpress-questions/. Accessed 2026-11-11. ↩︎
  48. Make WordPress Support. “Volunteering in the forums.” make.wordpress.org. Updated 2025-07-30. https://make.wordpress.org/support/handbook/contributing-to-the-wordpress-forums/volunteering-in-the-forums/. Accessed 2026-11-12. ↩︎

Did you enjoy this article?

Recommend it — Standard Reader surfaces well-loved writing to more readers across the network.

Across the AtmosphereDiscussions