Phil Kuang

`[Contributors]` I can do a quick demo of my new proposed [playlist plugin](https://github.com/backstage/backstage/pull/12870)

I believe this can now leverage the new Atlassian auth provider https://github.com/backstage/backstage/pull/7570

Another possible implementation is to build out the backend service to make use of the built in `UrlReaders` and have the frontend proxy all requests through the backend instead (similar...

Hi, I was wondering if anyone has any updates on this? it looks like the current implementation only tracks each initial hit to the Backstage site but doesn't report hits...

https://github.com/backstage/backstage/issues/11611 is a relevant related effort here for extending plugin default APIs

hm https://github.com/backstage/backstage/pull/12484 has been merged so it may be possible to start experimenting there but the framework is still very much in alpha. cc: @Rugvip for his guidance here

Amazing proposal! I really like how it encapsulates much of the same pattern from the frontend system which provides integrators the same familiar interface and a consistent configuration experience throughout...

> Just a quick pass right now, but I'm wondering about the naming of the plugin. `playlist` is a bit ambiguous. Not sure 🤷 @backstage/maintainers? perhaps `entity-playlist` ?

@benjdlambert @Rugvip quick reminder that this is still here awaiting further feedback 😁

> @kuangp yep sorry, on my radar! It's a big one so needs a bigger chunk of time, which I haven't sliced out just yet 😅 no worries! just want...