Hmm, can someone TLDR what this is supposed to be? I did read the article but I didn't understand what this is trying to do. It just mentions something about the "collective health of something".
I can try to clear this up (full disclosure: I work on the MDN team at Mozilla).
Last year our team was downsized by a little below 50%. Most of the losses were in the writer's team. We only lost one engineer.
As a result, our writing output was considerably smaller. To mitigate this, we did two things:
1. Mozilla hired some contractors to help keep the continuous web platform documentation updates happening, so MDN does not become out of date.
2. Mozilla plus Google, Microsoft, Samsung, W3C, Coil, and other supporters worked together to create Open Web Docs, which provides funding to hire more full-time writing staff to help MDN content keep getting better.
Step 1 was really just getting MDN out of trouble, and back to stability. Step 2 is about letting us go further and start evolving MDN's content.
MDN is staying inside Mozilla; we still contribute a lot to MDN in terms of engineering, infrastructure, and writing costs. It is just that we now have OWD contributing to writing costs as well, to help safeguard the content.
This is a good thing — it allows all the interested orgs to get together and agree on future content directions for MDN together, rather than just working away on it in our own little pockets. And we'll be developing a shared process to follow to make sure that all work is going in the right direction.
I didn’t get it either at first. But MDN Web Docs is Mozilla’s (very good, IMHO) web developer documentation site. Open Web Docs is apparently some kind of foundation/organization to collaborate on web documentation with other industry folks so it’s not held in just one company’s hands.
(Take this with a grain of salt. I’m still only half-sure I get it.)
ETA: hayksaakian succeeded in saying what I was trying but failing to say. :)
Last year our team was downsized by a little below 50%. Most of the losses were in the writer's team. We only lost one engineer.
As a result, our writing output was considerably smaller. To mitigate this, we did two things:
1. Mozilla hired some contractors to help keep the continuous web platform documentation updates happening, so MDN does not become out of date.
2. Mozilla plus Google, Microsoft, Samsung, W3C, Coil, and other supporters worked together to create Open Web Docs, which provides funding to hire more full-time writing staff to help MDN content keep getting better.
Step 1 was really just getting MDN out of trouble, and back to stability. Step 2 is about letting us go further and start evolving MDN's content.
MDN is staying inside Mozilla; we still contribute a lot to MDN in terms of engineering, infrastructure, and writing costs. It is just that we now have OWD contributing to writing costs as well, to help safeguard the content.
This is a good thing — it allows all the interested orgs to get together and agree on future content directions for MDN together, rather than just working away on it in our own little pockets. And we'll be developing a shared process to follow to make sure that all work is going in the right direction.