On 6/15/17 3:41 PM, Gregory Szorc wrote:
We already had fragmented Firefox build docs. We have things scattered between MDN, wiki.mozilla.org <http://wiki.mozilla.org>, in-tree Sphinx docs, and years of mailing list and blog posts (which sadly are the sole source of some useful info). With MDN pivoting towards the web and being hostile to non-web docs, I think the writing is clear that we should be moving Firefox build/development docs off MDN. Or at the very least we shouldn't continue to invest much effort in the MDN docs.
For whatever it's worth, I'm investigating how to move the MediaWiki-based Wikimo over to a non-MDN Kuma instance. I don't know whether or not this is feasible yet - "losing no history" is The Thing - but MDN is _so_ much easier to edit, and in principle maybe we don't need to actively support... four? five? however many different wikis we support.
"Correct the wiki" is a really low-friction way to contribute, and from a community member's first-contact perspective: learning how to submit a patch to fix an error in our patch submission documentation seems like a lot. I also don't know how well an in-codebase solution will play with localization or accessibility tools in comparison.
I agree that we should anoint a single point of authoritative truth for this, but I think that we want the prerequisites for accessing and changing our docs to be as low as possible, preferably as little as "human brain and keyboard".
- mhoye
_______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
