It's also worth noting that you should feel free to add the dev-doc-needed
keyword to any bug you think even *might* affect developer documentation.
We would rather have false positives than miss something that should have
been updated.
As an example, perhaps you add code to improve the internal d
Yes, what sheppy said ;-)
Chris Mills
MDN content lead & writers' team manager || Mozilla
developer.mozilla.org || MDN Web Docs
cmi...@mozilla.com || @chrisdavidmills
> On 17 May 2018, at 05:27, Eric Shepherd (Sheppy)
> wrote:
>
> Yes. Always, you're welcome to make needed changes yourself. If
Yes. Always, you're welcome to make needed changes yourself. If you want a
writer to take a look after you're done, to be sure everything is in the
right place (or to double-check your grammar), that's certainly no problem.
On Wed, May 16, 2018 at 6:40 PM Martin Thomson wrote:
> Hi Chris,
>
> I
Hi Chris,
I assume that "just fix it" is still a viable alternative to the processes
you describe. For small things, that might be easier for all involved.
On Thu, May 17, 2018 at 5:39 AM Chris Mills wrote:
> Hi all,
> I am sending a mail around to explain how to request MDN documentation
for
Hi all,
I am sending a mail around to explain how to request MDN documentation for new
features you are working on (e.g. new web platform features, web extensions
features, devtools features), or report docs problems. We've had a fair few
people show a misunderstanding of how this process works
5 matches
Mail list logo
