Skip to content
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

Plugin overlap survey #1295

Open
2 of 13 tasks
kdeldycke opened this issue Aug 31, 2020 · 1 comment
Open
2 of 13 tasks

Plugin overlap survey #1295

kdeldycke opened this issue Aug 31, 2020 · 1 comment

Comments

@kdeldycke
Copy link
Contributor

kdeldycke commented Aug 31, 2020

In the context of the general migration of this mono-repo into a collection of independently packaged plugins, and to speed-up the final archival of this repository, here is a proposal to mark some plugins hosted here as deprecated. My intention here is to bootstrap the discussion on which plugins we can safely mark as abandoned, unmaintained, unused, deprecated or overlapping.

Here is a couple of observations I gathered while updating the plugin inventory and their migration status:

@logological
Copy link
Contributor

joachimneu/pelican-md-metayaml appears to be abandoned; there have been no commits since 2017 and it doesn't work with Pelican 4. pR0Ps/pelican-yaml-metadata (which is not a submodule of the current repository) seems to be an actively maintained, drop-in replacement that actually works.

I am having difficulty understanding what noirbizarre/pelican-frontmark actually does because the documentation is nonsensical in places. (I gather the author may not be a fluent speaker of English.) If it does anything in addition to allowing YAML in the front-matter metadata, then I wouldn't consider it a replacement for joachimneu/pelican-md-metayaml. (I generally want my plugins to follow the Unix philosophy of "do one thing and do it well", not mixing and matching various functionalities that I don't necessarily want or need.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants