deprecating project

[willkg]

Edit by @hoodmane: Pyodide has taken over the project and it is now sort of maintained.

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?

[laymonage]

Hi, may I ask what the direction for this project's future is? I see that it's been transferred from the mozilla org to pyodide. Are there going to be further releases from pyodide, or is this project considered abandoned?

I'm considering the use of this package for wagtail, but there are issues like #80 that block us from doing so. I'd be happy to contribute patches, just wanted to make sure that they'd have a chance of getting merged and released. Thank you!

[hoodmane]

I still maintain this project for Pyodide. I am intending to release a version 5.0, but since I have a lot of stuff to maintain I need some external encouragement to do so. =)

On the main branch over here https://github.com/pyodide/sphinx-js-fork I've updated it to use typedoc 0.27. It seems that jsdoc is a lot more stable than typedoc, I'm not sure if there are any compatibility issues with jsdoc updates.

I'll start by merging sphinx-js-fork main branch into sphinx-js and then feel free to open PRs. I will do my best to review them.

[laymonage]

Thank you very much, looking forward to it!

[hoodmane]

I think #80 was already fixed by this:
pyodide#116

[hoodmane]

Okay, released sphinx-js 5.0.0:
https://pypi.org/project/sphinx-js/