Re: [w3ctag/spec-reviews] A spec style/structure checklist? (#136)

> On Sep 22, 2016, at 1:43 , Marcos Cáceres <notifications@github.com> wrote:
> 
> I'd love to have something rough to drop into: 
> https://github.com/WICG/starter-kit/blob/master/templates/explainer.md
> 
> Just simple/human things to put in there (i.e., keep this targeted at developers) - and maybe just some links to what we consider good examples of an explainer (e.g., the SW one).

Do we have an ‘empty skeleton’ or template that we maintain, that we can point people at?

Also, the AB is concerned that the /TR page is an un-navigable list (‘graveyard’ has been used). Templates or other work that help classify specs (some semantic tagging) might help.

I like templates, as they could include sections which are not uniformly present — how to report an issue and how to see reports of issues; security and privacy considerations; and so on


David Singer
Manager, Software Standards, Apple Inc.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/136#issuecomment-248922374