- From: Ryosuke Niwa <rniwa@apple.com>
- Date: Wed, 10 Sep 2014 19:00:54 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Arthur Barstow <art.barstow@gmail.com>, public-webapps <public-webapps@w3.org>
On Sep 4, 2014, at 6:46 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Thu, Sep 4, 2014 at 5:43 AM, Arthur Barstow <art.barstow@gmail.com> wrote: >> Hi Editors, All, >> >> Speaking of ED boilerplate data ... do we want to try to get some >> consistency regarding boilerplate data in our EDs? >> >> We have quite a bit of variation now. For example Clipboard and others are >> toward the more minimalist end of the spectrum: >> >> <http://dev.w3.org/2006/webapi/clipops/clipops.html> >> >> Whereas, the Manifest spec's boilerplate data is more thorough: >> >> <http://w3c.github.io/manifest/> >> >> I personally prefer the Manifest approach (especially a link to the spec's >> bugs/issues and the comment list). >> >> Should we try to get more consistency, and if so, what data should be the >> minimal recommended set? > > We've found in the CSSWG that linking to issue tracking is indeed > helpful, when the spec uses anything more than "email and inline > issues”. Yeah, links to specs & issues are very useful. I also find notes about the state of the current discussion very useful but I doubt many editors would have the time to keep those notes up-to-date... - R. Niwa
Received on Thursday, 11 September 2014 02:01:25 UTC