Transfer repository to Pelican Plugins organization

[justinmayer]

As part of our vision for moving plugins to their own community-managed repositories under the Pelican Plugins organization, I wondered whether it might be best to re-locate this repository under the new organization so that it can benefit from maintenance and enhancements from the broader Pelican community.

Obviously we could just create a new repository under the new organization and push the commits there, but if amenable to the original plugin author, it would be preferable to re-locate this repository in order to preserve issues, pull requests, and any other repository-related history.

[justinmayer]

@liob: Hi Hinrich! Since @nandac was kind enough to add namespace plugin support and other enhancements to your plugin for use with Pelican 4.5+, we would like to effect the above-mentioned move so we can publish a new version of the plugin. To that end, would you be willing to help me move this repository under the Pelican Plugins organization? If so, could you add me as an admin to this repository so I can begin that step?

[justinmayer]

Hi Hinrich. Just following up on my proposal above. Would you please take a moment and let me know what you think? Thank you! 😊

[justinmayer]

Hey Hinrich. In the interest of not pestering you any further, I'll plan on creating a new repository tomorrow, the first of November, assuming I don't hear from you first.

If you would like to help me transfer this repository within the next 24 hours, would you please let me know?

[justinmayer]

There is now a modernized and maintained version of this plugin available at: https://github.com/pelican-plugins/pandoc-reader

@liob: Many thanks for your work on this plugin. Cheers! 😁