Problem in Pelican 4.5.0

[traits]

@ingwinlu

I have a small plugin-related problem (getpelican/pelican#2793) in the new Pelican version 4.5.0. Is this something, you would still consider fixing/maintaining yourself? Otherwise, I would fork the project and include it into the new Pelican plugin workflow.

[ingwinlu]

Thanks for reaching out. While the fix would be easy I think it would be a good long term solution for you to fork as I currently have no interest in maintaining. Michael <notifications@github.com> schrieb am Sa., 22. Aug. 2020, 18:33:

…

@ingwinlu <https://github.com/ingwinlu> I have a small plugin-related problem (getpelican/pelican#2793 <getpelican/pelican#2793>) in the new Pelican version 4.5.0. Is this something, you would still consider fixing/maintaining yourself? Otherwise, I would fork the project and include it into the new Pelican plugin workflow <https://github.com/getpelican/pelican-plugins#pelican-plugins>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#20>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABB276VKA5AVK74754ETE4DSB7XMNANCNFSM4QIFSK5A> .

[kdeldycke]

Hi @ingwinlu ! 👋 I'm a member of the pelican-plugins umbrella organization. We're lucky to have @traits proposing some help about your plugin.

We can go further and transfer ownership of your repository to the pelican-plugins. That way you'll be free from the burden of maintaining it, while allowing newcomers and the community to contribute back to it. All the while keeping the commit history and associated issues and PRs intact.

I already proposed this transfer to other maintainers, so I'm used to the process and can guide you. See for example: pelican-plugins/similar-posts#3

What do you think?

[ingwinlu]

As mentioned in #20 (comment) -> whoever wants to step up in whatever way is fine by me. As long as the licensing is not violated.