- From: Samuel Weiler <weiler@w3.org>
- Date: Tue, 12 Feb 2019 14:31:44 -0500
- To: Tom Ritter <tom@ritter.vg>
- Cc: public-web-security@w3.org
On 2/12/19 2:27 PM, Tom Ritter wrote: > I hope the specs will also be posted to the list - I can't > consistently commit to reviewing specs on-demand; but I watch the > mailing list and try to weigh in when I can find the bandwidth. Calls for review will remain public. At the moment, those come to this list - that may change over time, as W3C unifies tooling for requesting and tracking reviews. I encourage everyone to weigh in on those calls for review whenever you feel so moved. This "recruit a designated reviewer" is intended to supplement that. -- Sam > -tom > > On Tue, 12 Feb 2019 at 19:14, Samuel Weiler <weiler@w3.org> wrote: >> >> Would you be willing to review a W3C spec for general security concerns >> - likely a spec outside of your own specialty of expertise - on request, >> perhaps 2-4 times per year? If so, please drop me a short note. >> >> This is a great opportunity to learn more about work happening in other >> parts of W3C. >> >> I'm building a pool of reviewers, modeled on the IETF Security >> Directorate review process. The idea is to bring in a fresh set of eyes >> - someone who is relatively unfamiliar with the spec in question - to >> see how well the spec authors have identified and addressed security >> issues. I am hoping that by making specific requests of specific >> people, we can provide timely reviews to spec authors and working groups. >> >> -- Sam Weiler, W3C >>
Received on Tuesday, 12 February 2019 19:31:46 UTC