Should we add documentation for this to the Developer Guide on MDN? We
cover a lot of the development process there, so it may be wise to
include this information there, unless someone can think of a good
reason not to.
On Tue, Mar 31, 2015 at 9:08 PM, Jonas Sicking wrote:
> Ah, sorry, I misunder
Ah, sorry, I misunderstood the intent of the wiki page. I retract my concern.
/ Jonas
On Wed, Apr 1, 2015 at 12:41 AM, Tantek Çelik wrote:
> Having pages go out of date can certainly be a challenge, hence why
> this wiki page is descriptive (citing historical examples and other
> external resour
Having pages go out of date can certainly be a challenge, hence why
this wiki page is descriptive (citing historical examples and other
external resources), rather than prescriptive.
No additional risk of becoming out of date beyond that from already
existing pages. It's a general good practice to
Will someone be maintaining this page? I'm worried that having an
out-of-date page might create more confusion than information.
/ Jonas
On Tue, Mar 31, 2015 at 3:58 AM, Tantek Çelik wrote:
> Having followed the "Intent to implement" emails for a while, and
> noticing that there was already an e
4 matches
Mail list logo
