deprecating project

[willkg]

Issue #233 has taken over a year and I haven't seen any movement on it in some time. In the spirit of Volunteer Responsibility Amnesty Day, I don't want to keep sitting on this and it's time to shut it down. Over the next week or two, I'm going to:

1. do a clean up pass
   • update sphinx-js to work with current versions of python
   • update sphinx-js to work with current versions of sphinx (unless that's too hard)
   • go through pull requests and issues and land anything that is well documented, has tests, and is something in can reason about
2. do a final release
3. archive the project -- no more releases after that

[willkg]

@hoodmane I want to archive this repository at some point, but I don't want to make your fork harder to kick off. Do you want anything from the issues or pull requests? Are there other things that might be helpful to do before I archive this?

[hoodmane]

I'll look over it but I don't think anything you do here will cause us much trouble.

[hoodmane]

It would be nice if you could point out that we exist as an actively maintained successor project in the text sunsetting this project.

[willkg]

I did the sphinx-js v4.0.0 release after fixing a handful of things to get CI and some other stuff working. I'll wait until next year and then if everything is good and I don't have to do a follow-up quick fix release, I'll archive the project.

@hoodmane When you say "point out that we exist", have you settled on naming and a GitHub url for the forked project?