Future/Roadmap for this package

[DanielBadura]

Initially we only played around how we could increase the DX even more for our library and we think that this a great tooling for that. But we also did not invest much time into this bundle and alot of thing changed in the meantime for example we have a new laravel integration.

We discussed already some outcomes for this package. We like the idea of the package itself and it will be maintained in the future. But we also discovered that it may not be the best naming for the goal of this package. I will list now from my PoV the paths we could go forward to.

1. Rename to event-sourcing-dashboard-bundle or something similiar. Why? Because the name right now, including the word admin, could be confusing for some people which for example have already worked with EasyAdminBundle or similar things. It's not really an administration tool. Instead this is more like a dashboard where a developer can see various things. The only administrativ part would be the subscriptions.
2. Split the package into a library part & a bundle part. Why? Then we could maybe re-use this for other framework like laravel. And the Bundle part could be integrated in the already existing bundle. The split however would be not so easy I suppose.
3. Keep it as it is right now: We have already enough topics at hand and the intergration of this dashboard is not likely happening in the near future by us without any contribution into this direction.

Feel free to add more options or opinions for my proposal here.