[wp-trac] [WordPress Trac] #64749: Proposal: AI Pathfinding Assistant for WordPress Contributors

[WordPress Trac]

#64749: Proposal: AI Pathfinding Assistant for WordPress Contributors
-------------------------+-----------------------------
 Reporter:  Marc4        |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  AI           |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 I propose the creation of an AI-powered tool integrated into the WordPress
 ecosystem (Trac/GitHub) to act as a navigator for contributors. The goal
 is to remove the "entry barrier" of locating specific files or triage
 components within the massive WordPress codebase, saving countless hours
 of manual review and repetitive administrative tasks.

 == 1. The Problem: The "Repository Wall"
 For the majority of people who are unfamiliar with the intricate structure
 of WordPress repositories, contributing presents a logistical challenge
 before a technical one:

 1. Code Vastness: Locating where a specific function or style resides
 among thousands of files is daunting.

 2. Triage Burden: Maintainers spend valuable time moving tickets to the
 correct component or redirecting Pull Requests (PRs) submitted to the
 wrong repository.

 3. Contributor Friction: The fear of "doing it wrong" or the frustration
 of searching unsuccessfully for the right file actively discourages new
 contributions.

 == 2. The Solution: AI Locator & Component Suggester
 Implementing a Natural Language Interface (LLM) trained on the WordPress
 repository structure in GitHub and the Trac component hierarchy.

 Primary Use Cases:

 1. File Localization:

 User: "I've found a styling issue with the 'Publish' button in the
 editor."

 AI Response: "That file is located at wp-admin/js/editor.js within the
 WordPress/gutenberg repository."

 2. Component Suggestion:
 User: "I found a bug in how images are displayed in the theme gallery."

 AI Response: "You should open this ticket under the 'Media' or 'Themes'
 component."

 == 3. Key Benefits
 1. Team Efficiency: Dramatically reduces the time spent manually triaging
 and moving tickets.

 2. Democratizing Contribution: Empowers non-technical profiles—or
 developers unfamiliar with the vast file structure—to find exactly where
 to propose changes or suggestions.

 3. Accelerated "Time-to-PR": The transition from an idea to the first
 commit becomes nearly instantaneous.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64749>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform