[Migration] pelican-toc

[traits]

I would like to volunteer for the migration of pelican-toc. (check references here and here ) following the new procedure. So, what transfer process have you in mind (I'm not the current maintainer/author, but consent was given)?

Michael

[traits]

following the new procedure.

From there:

after which a Pelican maintainer will guide you through the process.

So, someone?

[justinmayer]

Hey Michael. Many thanks for volunteering. I’m having a busy couple of weeks but will endeavor to respond as quickly as I can!

[kdeldycke]

Hi @traits! 👋

I just stumble upon your discussion with the original plugin maintainer at https://github.com/ingwinlu/pelican-toc/issues/20 . Maybe we can ask him about moving the repository under the pelican-plugins umbrella organization?

[traits]

Eventually better than forking, sure (no later doubts about the "right" one) . But I/he have/has still to know about pelicans procedure to do this. As I said, I would take this on my own. The immediate fix is trivial, but a clean version has probably to take more into account.

[kdeldycke]

@traits I'm used to the process of migration and packaging. See for instance: https://github.com/pelican-plugins/similar-posts/issues/3 . I can guide both @ingwinlu and you to the process if you'd like to help! 😃