Skip to content

Update plugin authors to performanceteam #2062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from

Conversation

jeffpaul
Copy link
Member

Summary

This pull request includes minor updates to the author information in two plugin files. The changes standardize the author name from "WordPress Performance Team" to "performanceteam."

Updated author information:

Relevant technical choices

Note that after updating these on WPORG that @felixarntz and @joemcgill will also need to follow the steps on https://developer.wordpress.org/plugins/wordpress-org/transferring-your-plugin-to-a-new-owner/ so that https://wordpress.org/plugins/view-transitions/ && https://wordpress.org/plugins/auto-sizes/ respectively get transferred to the performanceteam user and properly represented as "By WordPress Performance Team".

Copy link

github-actions bot commented Jun 20, 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 <[email protected]>
Co-authored-by: felixarntz <[email protected]>

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

Copy link

codecov bot commented Jun 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.03%. Comparing base (ff5cc68) to head (5913727).

Additional details and impacted files
@@           Coverage Diff           @@
##            trunk    #2062   +/-   ##
=======================================
  Coverage   68.03%   68.03%           
=======================================
  Files          92       92           
  Lines        7631     7631           
=======================================
  Hits         5192     5192           
  Misses       2439     2439           
Flag Coverage Δ
multisite 68.03% <ø> (ø)
single 37.02% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@felixarntz
Copy link
Member

@jeffpaul Is there documentation on this? Makes sense to change the ownership, but why change the plugin header author name to something less readable than before?

@jeffpaul
Copy link
Member Author

@jeffpaul Is there documentation on this? Makes sense to change the ownership, but why change the plugin header author name to something less readable than before?

I believe that's what https://developer.wordpress.org/plugins/wordpress-org/transferring-your-plugin-to-a-new-owner/ outlines, but these plugins might be something that are large enough that someone needs to email the Plugin Review Team to update directly.

@felixarntz
Copy link
Member

Thanks! In that case, we should probably reach out to plugins@ indeed. I see the mention of putting the username as an author, but that doesn't make any sense to me from a user-facing perspective. That author name is shown in WordPress, and it saying "performanceteam" instead of "WordPress Performance Team" is clearly worse.

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.

2 participants