Deprecate this plugin

[nilsnolde]

I'm planning to move away from this plugin for our blog and instead go with mkdocs and deploying it via Github Actions, which I recently did for Valhalla and the experience super pleasant. That'll also be a bit less maintenance hassle and with all the open-source projects & open infrastructures I'm currently maintaining, any single bit less (literally) is very welcome.

Some people might depend on this plugin, even if it's likely just a few users. It also will surely run for a while to come without any modifications, but I didn't even get around to test WordPress v6.x yet. I created this plugin solely for our own purposes and open sourced it out of ideology. I learned though that it's not a good idea to attempt to maintain something that is of no use to oneself. And that will soon be the case.

So if anyone feels like this is valuable enough to preserve and wants to maintain it, I'm happy to transfer the repo. If not, I won't have a problem deprecating it either. Cc @danilopinotti @LuigiBella, in fact you're the only ones I know for sure, who at least used to use this plugin, so just letting you know explicitly:)

[LuigiBella]

Thank you @nilsnolde, for letting us know, and for developing this plugin and keeping it running well to this point.

We are still utilizing it on disasteraware.org with WordPress 6.1.1 and have been experiencing no issues, so even though I have limited (very limited) experience maintaining plugins, I'd love to try to keep this plugin maintained.

Please let me know what next steps I should take, and best of luck on your future ventures!

[nilsnolde]

Thanks for answering @LuigiBella and for offering to keep maintaining this plugin. If you're sure, we'd have to do the following:

• I can do a last release updating the compatibility to 6.1.1, so you won't be bothered for a few months and I can document the release flow a bit more in detail
• then transfer the repository to your Github account
• then transfer ownership on wordpress.org to you

Then it's the normal software development flow: release whenever you fixed some bug(s)/introduced/deprecated some feature(s) using subversion (annoyingly). There is some stuff documented around the release: https://github.com/gis-ops/wordpress-markdown-git/blob/master/README_dev.md, but I'll update that following the coming release in the next week or two. Also you can always tag me in your repo when you have a question, I'll try to help.

We are still utilizing it on disasteraware.org with WordPress 6.1.1

Well that's a relief for sure:)

[LuigiBella]

That sounds good! @nilsnolde let me know if there is any other info you need from me to move forward. Thank you again for all your work in creating this project!

[planetahuevo]

hi @nilsnolde
Thank you for the plugin all this time.
Do you have any link or doc to see how to do this with mkdocs and github actions?
It makes sense for us to do it that way as well.

Thank you to @LuigiBella for taking this over too!

[trainingcity]

Just tried out your plugin on a LearnDash LMS beta site. It is a great tool and runs without issue on current WP release (July 2023). Hopefully you can find a way to keep it maintained. I was even able to use it with a private GitHub repo using the new beta fine grained tokens and a Github org that has SAML SSO configured. All things that I thought would break your WP plugin.

For what it is worth, if you do choose to maintain the plugin, setting the parameters as variables would be amazing. It would be great to be able to maintain the fine grained token in one location and deploy it to many pages (LMS lessons, etc) that will use the shortcode.

[PrzemyslawKlys]

hi @nilsnolde, just wanted to warn you. While I understand your decision to give this plugin out for continuance, keep in mind that a lot of us actually still use it and benefit from it. If you do give it to a wrong person, those sites may end up getting hacked in the process. Hopefully you can somehow validate whoever you are giving power over this repo/over Wordpress repo to be valid member of the community and not someone who will take down a lot of sites in the process.