Deprecate and archive the repo?

[jtpio]

FPS was initially used as a base for https://github.com/jupyter-server/jupyverse.

However jupyverse then switched to Asphalt: jupyter-server/jupyverse#277

Is FPS still used somewhere? mamba repoquery whoneeds fps only lists the jupyverse packages. Not sure if there is a package published on PyPI who depends on it.

So the question is: if FPS is not maintained anymore, and no one depends on it, should the repo be archived?

Related to jupyter-server/jupyverse#444

[davidbrochart]

Asphalt is great and I've been working with the author on the upcoming version 5, but it's been a long process and it's still not done. Also, even if I'm a member of the Asphalt framework organization, I don't have the freedom to do whatever I want, so that's a risk.
On the other hand, I've been experimenting with my own implementation in FastAIO, very much inspired by Asphalt v5 but maybe simpler. I was thinking that it could be the next version of FPS, instead of deprecating and archiving it, and that Jupyverse could use it instead of Asphalt.
I agree that this would be a completely new project, incompatible with the current FPS, but I think it would make sense since the current project is dead anyway. Also, Asphalt v5 is incompatible with v4, so from Jupyverse's point of view it's a breaking change in both cases.