During the migration phase from Rack 0.5 to Rack 0.6, the community assisted authors of open-source Rack plugins with migration in the form of GitHub Pull Requests.
This worked great and allowed a very efficient transition and successful launch of Rack 0.6 with the majority of open-source plugins available in the Plugin Manager upon release.
For Rack 1.0, the Rack Library Team is again coordinating the open-source plugin migration effort on GitHub.
Here is a few ways that the migration can work:
- Plugin author migrates plugin herself, then submits an issue in the Library Repository. The Library Team will review the plugin code and integrate into the Library Repository if the acceptance criteria are met.
- Plugin author needs help migrating plugin. A community member volunteer will provide a GitHub Pull Request to the author with the necessary changes to update to
v1of the Rack API. The author then submits an issue in the Library Repository. The Library Team will review the plugin code and integrate into the Library Repository if the acceptance criteria are met.
General Notes: The migration of all plugins will be tracked in a GitHub Project Board. This project board page contains an overview of the Acceptance Criteria the plugin has to meet to move through the different stages of the process. Every plugin must have 1 (one) issue in the Library Repository on GitHub that is used for communicating plugin status to the Library Team. Notify the Library Team that your plugin is ready for migration to Rack 1.0 in that issue on GitHub and the team will update the Project Board status of the plugin.
Plugin Authors: If you need help from the community migrating your plugin to the
v1 API, please let me know in this topic. I will update the GitHub Project Board to reflect the need for help and community members can volunteer and work with you to provide a PR against your plugin.
Community Members: If you are willing to help migrating plugins to the
v1 API, please also let me know in this topic. The Library Team will provide a list of plugins that need migration help on GitHub and will assign one to you. You will then work with the plugin author via their GitHub repository to get the plugin updated to the
IMPORTANT: Please do NOT just start randomly updating other people’s plugins to the
v1 API. We had a lot of success last time around with a coordinated effort that eliminated a lot of duplication of work. If the authors want help, they are encouraged to ask for it here. Otherwise we assume that she is updating the plugin herself.
For reference, here is a link to the official
v1 migration guide.
Let me know if you have any questions.
(This will be cross-posted in the Facebook Plugin Developer group).