Improved version of the previously rejected deprecated API usage PR

Contributing GSoC
1

Hi,

I’ve been revisiting the idea from my previously closed PR on deprecated API usage after reading the review feedback more carefully.

I understand now that this repository is a data/metadata repository, so adding a static visualization/dashboard here was not the right approach.

Instead, I’m thinking of reworking it as a metadata transformation step:

  • take the deprecated API usage data from usage-in-plugins

  • transform it into a plugin-keyed JSON format

  • keep the contribution focused on metadata preparation/enrichment

  • not add any frontend or static website pieces to this repository

So the goal would be to prepare deprecated API usage data in a format that could be consumed more easily by the metadata pipeline later, rather than visualizing it here.

Before I continue, I wanted to check whether this revised direction sounds reasonable.

Mentors : @jonesbusy @krisstern @CodexRaunak

Would this approach be okay to continue with?

2

Hi, just following up on my previous message regarding the revised approach for the deprecated API usage PR.

I wanted to confirm whether working on a metadata-oriented transformation (instead of a visualization) based on the usage-in-plugins data would be a reasonable direction for this repository.

If this approach sounds okay, I’ll continue working on the implementation and share the proposed structure before opening a new PR.

Thanks!