Closed Bug 1432445 Opened 7 years ago Closed 4 years ago

Host Spidermonkey documentation in tree

Categories

(Core :: JavaScript Engine, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
Tracking Status
firefox60 --- affected

People

(Reporter: bbouvier, Unassigned)

References

Details

Just a reminder to myself that could be of interest to others too: https://firefox-source-docs.mozilla.org/index.html#managing-documentation TL;DR we can easily host documentation in tree, in js/src/docs directory for instance, then set SPHINX_TREES['spidermonkey'] = 'docs' in js/src/moz.build. Then the documentation should appear on https://firefox-source-docs.mozilla.org in a Spidermonkey area, and be rebuilt as soon as the source changes. We already have a doc/ directory under js/src/ that we could move to js/src/docs and rst formatting, as a nice start.
Priority: -- → P3
FWIW the MDN people are looking to move all Mozilla-specific docs off MDN to elsewhere, fairly soon -- got mail from Chris Mills about this recently. It sounds like there's probably going to be some docs from them on how one would go about doing this, wrt something like the URL in comment 0. (Although I think SpiderMonkey having its own separate docs-page, not embedded within the overall Firefox docs, is desirable to emphasize our status as an embeddable, standalone project not wholly subordinate to Firefox.) Also I vaguely remember someone poached a read-the-docs name for this, but I don't remember the name off the top of my head and *may* well be imagining that ever happened.
I registered http://spidermonkey.readthedocs.io (empty at the moment), just so we can keep the name. It's linked to a(n empty) git repository, which ownership I would be glad to give back to the mozilla org: https://github.com/bnjbvr/spidermonkey-docs
Flags: needinfo?(jorendorff)
Please let me know if I can be of any help from the MDN side of things.
Severity: normal → N/A
Flags: needinfo?(jorendorff)

The old opcode data on MDN is stale and while we do have a script to generate it, we don't keep it up to date as often as bytecode changes. Similarly the JSAPI is not exactly a stable API and the process to split it up continues to happen.

I think we can call the original objective here accomplished though.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.