Folks, thinking about how we can better prioritize which plugins to build or migrate to v2. I'm working on two features for the plugin registry: 1. An upvote system so the community can vote on which plugins they actually need. 2. A gap analysis page that cross-references download stats from PyPI and npm with what Flyte already covers. For example, Polars has 30M+ downloads/month and there's no Flyte plugin for it. That kind of signal helps us focus effort where it matters most. Would love to hear what you all think. Or if you have any other smart suggestions

Something to add is that there are a few orgs that use the omegaconf plugin pretty seriously for creating our own hydra plugins. This area might have the most friction and be worth prioritising just to ensure V2 adoption from these orgs

+1 to the upvoting system 🙂

@broad-monitor-993 Upvote system heating up. Built an automated discovery pipeline that scans PyPI + GitHub to surface integration gaps, so the list stays fresh without manual curation. Planning to add community voting next so we can prioritize what to build based on actual demand.