-
Notifications
You must be signed in to change notification settings - Fork 844
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Migration] pelican-toc #1294
Comments
From there:
So, someone? |
Hey Michael. Many thanks for volunteering. I’m having a busy couple of weeks but will endeavor to respond as quickly as I can!
|
Hi @traits! 👋 I just stumble upon your discussion with the original plugin maintainer at ingwinlu/pelican-toc#20 . Maybe we can ask him about moving the repository under the |
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. |
@traits I'm used to the process of migration and packaging. See for instance: pelican-plugins/similar-posts#3 . I can guide both @ingwinlu and you to the process if you'd like to help! 😃 |
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
The text was updated successfully, but these errors were encountered: