插件开发文档

将您的插件转让给新所有者

💡 云策文档标注

概述

本文档介绍了如何将WordPress插件转让给新所有者的流程,区分了用户数低于10,000和超过10,000(或为beta/特色插件)的情况。转让涉及添加提交者和使用高级选项卡或邮件申请等步骤。

关键要点

  • 插件在任何时候只能有一个官方所有者,类似于WordPress文章的作者。
  • 对于用户数低于10,000的插件:首先添加新用户为提交者并更新readme.txt,然后在高级选项卡的“危险区域”中选择新所有者进行转让。
  • 对于用户数超过10,000或为beta/特色插件:需要通过当前所有者的邮箱发送邮件至plugins@wordpress.org,提供转让原因、新所有者用户ID和状态变更信息。
  • 转让请求可能因插件重要性或验证问题被拒绝或延迟。

注意事项

  • 如果没有其他提交者,插件无法转让,必须先添加提交者。
  • 确保邮件来自当前所有者的邮箱,以避免请求无效。

📄 原文内容

While any plugin can have an unlimited number of committers and support reps, there is only one official owner of a plugin at any time. This is akin to how a post on WordPress can only have one official post author.

For Plugins With Under 10,000 Users

If you’re transferring your plugin to a new owner, there are two steps that must take place.

First, add the new user as a committer to the plugin:

  • go to https://wordpress.org/plugins/YOURPLUGIN/advanced and add their username in as a committer
  • update the readme.txt to add their userID as an author

Next, go to the Advanced tab and scroll down to the Danger Zone. There you will see a section for Transfer Your Plugin. Pick someone from the dropdown and click the button.

If there are no other committers, the plugin will not be available to be transferred, so you must do that first.

Transfer this plugin interface with a selector for the new owner and a "Please transfer -Plugin Name-" button

For Plugins with OVER 10,000 Users (or are beta/featured)

In order to prevent abuse, larger plugins and those officially recognized as featured/beta are restricted from these changes.

To transfer a plugin in this case, you will need to email plugins@wordpress.org from the CURRENT owner’s email the following information:

  1. A brief explanation of the reason for the transfer
  2. The user ID of the new owner
  3. If applicable, any changes to the status of being a featured/beta plugin

Most requests are processed without issue, however should a plugin be determined to be critical to the WordPress.org project, or should there be reason to believe the request was invalid (i.e. not sent from the current owner’s email, or an email address positively connected back to them), it may be denied or delayed.