这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@jeffpaul
Copy link
Member

This pull request updates the README.md to provide a clearer introduction, a more structured overview of the plugin's roadmap and features, and an improved documentation for contributors and developers. Additionally, it introduces a new ROADMAP.md file to outline detailed development milestones and future plans.

@jeffpaul jeffpaul added this to the WordPress 6.9 milestone Sep 17, 2025
@jeffpaul jeffpaul self-assigned this Sep 17, 2025
@github-actions
Copy link

github-actions bot commented Sep 17, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>
Co-authored-by: karmatosed <karmatosed@git.wordpress.org>
Co-authored-by: felixarntz <flixos90@git.wordpress.org>
Co-authored-by: swissspidy <swissspidy@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Copy link
Member

@karmatosed karmatosed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love to see this, thank you 🙌🏻

@t-hamano
Copy link
Contributor

Is it possible to manually apply a link to the issue number? Unlike GitHub comments, #{issue_number} does not seem to be automatically converted to a link in README files.

https://github.com/WordPress/ai/blob/96e4e8df9370a814ba77c6bf2004fd8b05ea58ae/ROADMAP.md

image

Co-authored-by: t-hamano <wildworks@git.wordpress.org>
@jeffpaul
Copy link
Member Author

@t-hamano good callout, I've added those in 13a3917.

@jeffpaul
Copy link
Member Author

@Jameswlepage @felixarntz @swissspidy any adjustments y'all want here before we merge this in and try to get folks aligned to the work needed?

Copy link
Member

@felixarntz felixarntz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeffpaul Overall LGTM, just one caveat. Tentatively approving though.

Co-authored-by: Felix Arntz <flixos90@gmail.com>
@jeffpaul
Copy link
Member Author

jeffpaul commented Oct 1, 2025

Confirming in synchronous Zoom discussion with @Jameswlepage that he's reviewed and is good with this, so I'm going to go ahead and merge this in so @karmatosed and I can continue with the feature definition/mockups and then getting the plugin scaffolded out with defined features off to engineers.

@jeffpaul jeffpaul merged commit f48779d into trunk Oct 1, 2025
1 check passed
@jeffpaul jeffpaul modified the milestones: WordPress 6.9, 0.1.0 Oct 6, 2025
@jeffpaul jeffpaul deleted the add/roadmap branch October 8, 2025 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants