The WordPress open source project relies heavily on its global contributor community. As educational institutions increasingly look for ways to bridge the gap between classroom theory and real-world software engineering, initiatives like WP Credits have emerged to validate student contributions. Following steady growth and proof that the underlying program model functions effectively, the Make WordPress Community team is actively working on the next evolution of the project: a dedicated developer track and an immediate pilot opportunity.
The Evolution of WP Credits in Academic Settings
WP Credits was established to recognize and formalize contributions made to the WordPress ecosystem, providing a structured pathway for learners to earn academic recognition or credentials. As the program matured, it became clear that a generalized approach did not fully meet the specialized needs of students pursuing technical degrees. While content creation, translation, and community support are vital, computer science and software engineering students require pathways focused strictly on code, version control, and core software development lifecycles.
The Upcoming US College Pilot Opportunity
A significant milestone for this evolution is an expression of interest from a college in the United States. This institution wants to integrate WordPress contributions into their curriculum but specifically requires a developer-focused track. This institutional demand provides an ideal real-world testing ground for a structured, code-centric curriculum. However, deploying this pilot successfully requires defining precise criteria for what constitutes a valid contribution within a developer context, broken down by skill level.
Defining the Developer Track Structure
To accommodate varying skill levels within a standard academic term, the community is structuring the developer track into a progressive two-to-three-level path, ranging from beginner to advanced tiers. Structuring these tiers requires mapping specific GitHub workflows, Trac ticket interactions, and patch creation tasks directly to student capabilities. The goal is to ensure that students build genuine, job-relevant engineering skills rather than performing superficial tasks.
Tier 1: Beginner Contributions and Onboarding
The immediate priority is defining Tier 1, with a strict deadline set for the end of August to meet the college’s academic calendar. Beginner contributions must focus on lowering the barrier to entry while introducing students to core project tools like GitHub, Git, and WordPress Trac. Typical Tier 1 tasks include identifying and reporting reproducible bugs, writing automated tests for existing features, triaging incoming issues, and submitting minor documentation fixes or code cleanups that do not require complex architectural decisions.
Tier 2 and Tier 3: Intermediate and Advanced Milestones
As students progress through the intermediate and advanced tiers of the pilot program, the complexity of their contributions scales upward. Tier 2 tasks naturally involve writing unit and integration tests, resolving straightforward bug fixes on Trac, and contributing to ongoing feature development under the guidance of core maintainers. Tier 3, reserved for advanced students, tackles complex code patches, architectural reviews, security hardening, and deep involvement in component maintenance. These advanced tiers mirror the day-to-day responsibilities of professional plugin and core developers.
Community Collaboration and How to Participate
Building an effective developer curriculum requires collective input from experienced developers, maintainers, and WordPress educators. The Make WordPress Community team cannot design this alone. Educators understand pedagogical pacing, while seasoned core contributors understand the realities of project maintenance. Combining these perspectives ensures the curriculum is both academically rigorous and aligned with the project’s contribution standards.
Practical Implementation and Next Steps
With the first tier deadline looming at the end of August, action is moving quickly. Contributors, developers, and teachers interested in shaping the rubrics, suggesting specific Trac tickets, or reviewing tier definitions can engage directly with the initiative. Discussions are actively taking place on the official GitHub issue tracking the developer track, as well as in the dedicated `#wpcredits` channel on the Make WordPress Slack workspace. Your direct experience in mentoring and developing for WordPress is critical to ensuring this pilot’s success.
Frequently asked questions
What is the WP Credits developer track?
The WP Credits developer track is a specialized, code-focused curriculum currently in development to help college students earn academic credit while contributing to the WordPress open source project.
Why is the developer track being created now?
A US college expressed interest in utilizing WP Credits but specifically required a developer-focused path for their computer science and engineering students, prompting the community to build a structured tier system.
When is the deadline for the Tier 1 definition?
The community needs at least the first tier of the developer track defined by the end of August to stay on track for the upcoming academic pilot.
How can developers and educators contribute to this initiative?
You can participate by joining the discussion on the official GitHub issue or by engaging in the #wpcredits channel on the Make WordPress Slack workspace.
Primary reference: Review the original announcement for exact release details. This article is an independent explanation and does not reproduce the source text.