This week’s AI contributor meeting focused on initial strategy and timelines for the upcoming WordPress 7.1 release cycle, the deployment of a new minor release for the AI plugin, and structural maintenance across the PHP AI Client and MCP repositories. The group also held an extensive discussion around ecosystem contribution metrics, programmatic encryption experiments, and the standardization of settings fields layout within the Connectors API interface.
Announcements & WordPress 7.1 Timeline
- WordPress 7.0 Feedback: Following the successful launch of WordPress 7.0 last week, active installations and usage of the companion plugin have seen a significant initial increase. The support channels on WordPress.org and GitHub remain stable and manageable.
- WordPress 7.1 Schedule: @jeffpaul shared a tentative schedule for the 7.1 cycle, targeting July 15 for Beta 1 and August 19 for the final release during WordCamp US.
- Release Squad Nominations: Core release squad nominations remain open through the end of next week. @jeffpaul is actively reviewing submissions to coordinate the squad selection alongside @4thhubbard. Any critical AI enhancements intended for core must be finalized before the six-week window closes at Beta 1.
WordCamp Europe (WCEU) Contributor Day Preps
- Documentation Progress: @gajendrasingh has compiled a comprehensive contributor day reference playbook based on data from previous events.
- In-Person Adjustments: @justlevine noted that while the foundational context is excellent, the documentation should be slightly condensed for in-person attendees. The final prerequisites will be adjusted once the specific target testing sprint items are finalized.
- Local Onboarding Instructions: Due to notorious local venue Wi-Fi constraints, the table will heavily emphasize local environments. The squad will issue proactive recommendations for contributors to download and configure software dependencies, such as Ollama packages, prior to arriving at the conference.
AI Plugin Releases & Encryption Experiments
- Release Cadence Shift: A 1.0.1 minor plugin release containing bug fixes and structural polish is scheduled to deploy today. Moving forward, the plugin development cycle will shift from a bi-weekly cadence to monthly milestones, with version 1.1.0 slated for late June and version 1.2.0 targeted for late July.
- API Key Encryption PR: The group reviewed an experimental PR by @dkotter introducing programmatic key encryption based on background implementation mechanics from @ericmann.
- Gathering Real-World Feedback: Addressing ecosystem panic regarding plaintext API storage, @justlevine recommended merging the current experiment to gather immediate real-world testing data. The team noted that community feedback typically arrives much faster post-release, and the code can easily be refactored or rolled back to a dedicated encryptor class inside the plugin if needed prior to the 7.1 core freeze.
PHP AI Client Maintenance & Blockers
- Feature Gaps: Essential feature updates, including streaming data support, sound generation, and native embeddings infrastructure, remain high-priority requirements for the 7.1 cycle.
- Maintainership Bottlenecks: With @flixos90 stepping back and @jason_the_adams holding elevated structural responsibilities at Automattic, the repositories are facing a deficit in active maintainership.
- Unblocking Repositories: @jeffpaul clarified that contributors should feel empowered to aggressively test and review PRs within the PHP repository. Merging reviewed work does not trigger a deployment until a release version is formally tagged. If a green button needs to be pressed on a validated community PR, @jeffpaul will assist in sourcing an available committer to ensure development does not stall due to bureaucracy. Team will pause for @jason_the_adams or @flixos90 approval on releases, but otherwise will proceed with merging PRs.
Contributor Pledges & Metric Weights
- Revamped Profile Scoreboards: The team evaluated an active request from the Meta squad regarding data sets, weighted values, and scoring metrics for individual team pledge scoreboards on profiles.wordpress.org (core example, empty AI page).
- Beyond Code Contributions: @karmatosed raised a critical flag that the AI team relies heavily on a “Swiss Army knife” contributor model. Metrics that rely purely on trackable GitHub PRs or code commits fail to recognize vital non-dev contributions such as documentation audits, outreach, leading event tables, public presentations, and UI design workflows.
- Prior Art Modeling: @justlevine suggested checking in with the Performance team to see how they balanced plugin-to-core code metrics with documentation tracking. @jeffpaul noted that since Core and Meta are the only groups with established metric criteria, the AI team will temporarily mirror Core tracking mechanisms while iterating to account for unique non-code contributor tracks.
Connectors API Settings Fields Registry
- Custom Metadata Fields: @andrei_lupu created an issue on the Gutenberg repository exploring how individual connector providers can safely register custom metadata fields beyond the standard URL and API key inputs. This infrastructure is particularly necessary for local or self-hosted configurations like Llama.
- A Declarative PHP Approach: While custom layouts can technically be injected using heavy React components, @andrei_lupu argued that the vast majority of WordPress plugin developers need a declarative, server-side PHP registry class to register standard elements (text fields, selectors, radios) without needing a complex JavaScript build setup.
- The “Fields API” Forcing Function: The group discussed how the unified Connectors configuration interface has inadvertently become a forcing function for an option fields utility. @justlevineand and @nikmclaughlin noted that building a standard, secure programmatic registry within Connectors provides a safer path toward core settings standardization in 7.1, preventing plugins from dangerously hijacking core interfaces with unvalidated custom scripts.
Model Context Protocol (MCP)
- Bumping Minimum Dependencies: @justlevine confirmed that the ongoing MCP adapter integration is progressing steadily. Later today, the repository will officially merge a PR elevating the minimum environment requirement to WordPress 6.9.
- Forward-Compatible Pathways: Bumping the requirement allows the adapter to drop older library dependencies and natively rely on static analysis tools and the core Abilities API framework. The repository remains open for documentation contributions, and a forward-compatible migration pathway will be provided for legacy library integrations.
Next Steps
- Deploy today’s minor bug-fix release for the AI plugin.
- Review, test, and provide technical feedback on the active Encryption PR.
- Coordinate with @andrei_lupu on the Connectors custom fields registry issue within the Gutenberg repository.
- Finalize and distribute the WCEU Contributor Day preparation checklists for local environments.
Upcoming Meetings
- Contributors are welcome to join every Wednesday at 1700 UTC via Google Meet. In-meeting notes are captured live in a Slack Canvas and paired with aggregate transcription data to generate this meeting summary post. All team meeting schedules are published directly to the WordPress Meeting Calendar.
- AI Team Office Hours (Slack): Thursday, 28 May 2026. Facilitator @jeffpaul.
- Weekly AI Contributor Call (Google Meet): Wednesday, 3 June 2026.
Props to @jeffpaul for pre-publish review.