Where to download all the XUL/XPCOM documentation?

NEW
Assigned to

Status

11 months ago
10 months ago

People

(Reporter: roestvrijstaal_1, Assigned: cmills)

Tracking

({in-triage})

Details

(Reporter)

Description

11 months ago
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:45.9) Gecko/20100101 Goanna/3.2 Firefox/45.9 PaleMoon/27.4.2
Build ID: 20170821181241

Steps to reproduce:

Search through MDN.


Actual results:

I sadfaced because I couldn't find it. And to make it worse WayBackMachine doesn't have every page archived.


Expected results:

A link to download a xzed tarball of all the XUL/XPCOM documentation. 

Because Mozilla has chosen to deprecate it, but forks of Firefox not. So its _very_ likely it will get removed this year and that will harm developers who want to maintain their addons targeting forks of Firefox.
Component: General → General
Product: Developer Documentation → Mozilla Developer Network
Hi there, and thank you for your submission.

To be clear here, we don't want to remove documentation knowing that people are still using it. We do want to streamline MDN and make it more specifically about Open Web Documentation, but documentation that does not fit into that category will not just be deleted. Instead, we will aim to find a new home for it, whether that is on our Github repo or somewhere else.

It is unfortunate that the tarball of all the docs is no longer available.

I will start creating a plan for how to proceed on this.
Assignee: nobody → cmills
Moving to Mozilla Platform

> It is unfortunate that the tarball of all the docs is no longer available.

:cmills, was there an issue with the all-docs tarball?
Status: UNCONFIRMED → NEW
Component: General → Mozilla Platform
Ever confirmed: true
Flags: needinfo?(cmills)
Keywords: in-triage
Product: Mozilla Developer Network → Developer Documentation

Comment 3

11 months ago
To be clear: we have not yet removed any previously-written XUL/XPCOM/Mozilla platform documentation. This will almost certainly happen at some point, but we will not *delete* it. It will be moved somewhere, and we won't make its new home a secret. :)

If you're searching MDN looking for XUL or XPCOM content, be sure to enable it in the filters -- by default. Mozilla internal documentation like this is not included in searches.

You can get to a search page that will include everything by adding "&none=none" to the end of your search query. I use a search keyword with the URL "https://developer.mozilla.org/en-US/search?q=%s&none=none", named "mdnall" so that I can just type "mdnall nsISupports" to find nsISupports stuff.
(In reply to Chris Mills (Mozilla, MDN editor) [:cmills] from comment #1)
> Hi there, and thank you for your submission.
> 
> To be clear here, we don't want to remove documentation knowing that people
> are still using it. We do want to streamline MDN and make it more
> specifically about Open Web Documentation, but documentation that does not
> fit into that category will not just be deleted. Instead, we will aim to
> find a new home for it, whether that is on our Github repo or somewhere else.
> 
> It is unfortunate that the tarball of all the docs is no longer available.
> 
> I will start creating a plan for how to proceed on this.

(In reply to John Whitlock [:jwhitlock] from comment #2)
> Moving to Mozilla Platform
> 
> > It is unfortunate that the tarball of all the docs is no longer available.
> 
> :cmills, was there an issue with the all-docs tarball?

I assumed there was because the reporter couldn't find it. Is it there somewhere?
Flags: needinfo?(cmills)
OK, I'll check the tarball later this month: https://developer.mozilla.org/en-US/docs/MDN/About#Downloading_content
Flags: needinfo?(jwhitlock)
After the AWS move, the tarball's new home is:

https://mdn-downloads.s3-us-west-2.amazonaws.com/developer.mozilla.org.tar.gz

It's an older copy, from February 5, 2017, but the XUL docs are in there, at developer.mozilla.org/en-US/docs/Mozilla/Tech/XUL.

I've opened bug 1410931 to coordinate moving the tarball to the new location.
Flags: needinfo?(jwhitlock)
You need to log in before you can comment on or make changes to this bug.