Oliver Bertuch (Jan 16 2026 at 12:03): Oliver Bertuch (Jan 16 2026 at 12:03):I would like to start a discussion in the community of plugin authors how we want to shape the future of plugins.
Specifically, I put a lot of thought already into how our current approach to building plugins may lead into an abyss of compatibility issues that are hard to detect and potentially impact production instances using them.
For now, I've put all of this in writing at https://github.com/gdcc/dataverse-spi/compare/main...restructure. (@Philip Durbin 🚀 should we put this stuff in a Google Doc?)
There's probably more things to discuss I didn't think of yet.
Philip Durbin 🚀 (Jan 16 2026 at 12:17):Maybe. And then maybe in the guides, once we're happy with it?
Also, this is related: #docs > how to extend Dataverse
Oliver Bertuch (Jan 16 2026 at 12:39):I was thinking about having a distinct Github Page, so we can govern this stuff in the same repo. But we can at least crosslink! Another idea is to use a CI job to include the pages when building & shipping, so they appear also on guides.dataverse.org. (The process of shipping docs should probably be automated anyway...)
Philip Durbin 🚀 (Jan 16 2026 at 14:00):Yes, yes to crosslinking!
Oliver Bertuch (Apr 03 2026 at 00:50):Anyone visiting https://github.com/gdcc/dataverse-spi these days will see that exiting new things are around! The 2.1.0 release is going to be a game changer for the Dataverse Plugin Ecosystem, laying the groundwork for a solid foundation to build your plugins on.
Most important changes to come:
As of now, the SNAPSHOT preview of 2.1.0 is available on Maven Central, if anyone wants to try out the new toys!
Last updated: Apr 03 2026 at 06:08 UTC