Migrate `i18n_subsites` plugin

[frederik-elwert]

I have a site where I use the i18n_subsites plugin. For that purpose, I migrated it to the new-style format to enable auto-detection. I have my private copy now in a shape (updated/fixed tests, fixed linting errors, updated documentation) that I could share my copy. How would adding that migrated version to the pelican-plugins organization work?

[justinmayer]

Hi Frederik. Thank you for offering to assist with the migration of the i18n_subsites plugin. Regarding the process, which is listed in detail on the Migrating Plugins to New Organization post on the Pelican blog, you have already completed the first step, which is submitting an issue expressing your intention to assist with plugin migration.

As per the aforementioned guide’s Initial Setup (By Maintainer) section, the next few steps are undertaken by a Pelican maintainer, which I have already taken the liberty of completing. Ergo, I have created the new individual plugin repository, brought in the relevant commits from the legacy monolithic repository, and put them into the migrate branch.

The subsequent steps to be performed are listed in the Updating the Plugin section of that guide. You are a bit ahead of the process, so you may have to recreate the commits as per the instructions, but all the work you have done up until this point should be totally reusable.

If you would be so kind as to follow the guide, create the commits as per the instructions, push the new commits to the existing migrate branch, and then open a pull request for review, that would be greatly appreciated.

If you have any questions or need further clarification, please don’t hesitate to ask. Thanks again for your assistance with this migration! 😁

P.S.: Regarding your discussion post on the Pelican core repository… Pelican maintainers, myself included, only have a limited amount of time to dedicate to the project, so there can and will be times when we are unable to respond to every issue and pull request in the time-frame that we would otherwise prefer. We do the best we can.

[frederik-elwert]

Hi Justin. Thank you for the pointer to the blog post explaining the process, I had somehow missed that. I’ll follow the next steps accordingly.

And right, I went ahead because I needed that plugin for my own purpose, but I’m happy to retrace the steps in the official repo now.

Regarding that other post: I’m sorry about that, I did not mean to be pushy. I completely understand that time is limited, and I don’t mind waiting a while. I was starting to wonder about the process, but I should just have given it a bit more time.