- From: Wendy Seltzer <wseltzer@w3.org>
- Date: Wed, 19 Dec 2018 12:54:00 -0500
- To: Ian Clelland <iclelland@google.com>
- CC: Mike West <mkwst@google.com>,Web Application Security Working Group <public-webappsec@w3.org>
On December 19, 2018 12:27:12 PM EST, Ian Clelland <iclelland@google.com> wrote: >I think we just need to do the transfer, in two steps. Probably >transfer to >w3c/feature-policy, and then rename to w3c/webappsec-feature-policy -- >does >that make sense? Sure. > >The existing w3c/webappsec-feature-policy probably needs to get deleted >first, so that GitHub will perform the rename. (Sorry for the extra >work, I >hope it wasn't too much) No problem. > >As far as a FPWD goes, should I just make that a separate set of >HTML/CSS >files in a directory on the repo? Should work, thanks! Wendy ( >https://www.w3.org/Guide/transitions?profile=FPWD isn't super helpful, >at >least for answering the question "where do all of the documents go?") > >Thanks, >Ian > >On Wed, Dec 19, 2018 at 12:07 PM Wendy Seltzer <wseltzer@w3.org> wrote: > >> On 12/19/18 12:04, Ian Clelland wrote: >> > I'm going to remove the 'unstable' from the JS interface, and >probably >> add >> > a "Feature-Policy-Report-Only" header, but that's about it for a >FPWD, I >> > think >> > (and the second one is optional, could be added later) >> > >> > The only thing stopping me from publishing right now is the "where >do I >> put >> > it" question. >> >> What can I do to help with the transfer to >> github.com/w3c/webappsec-feature-policy ? >> >> --Wendy >> >> > >> > On Wed, Dec 19, 2018 at 11:51 AM Mike West <mkwst@google.com> >wrote: >> > >> >> We should, thanks for the PR! >> >> >> >> Which reminds me, +Ian Clelland <iclelland@google.com>, is there >> anything >> >> else you'd like to clean up in the spec before moving forward with >a >> CfC to >> >> publish a first working draft? >> >> >> >> -mike >> >> >> >> >> >> On Wed, Dec 19, 2018 at 5:42 PM Wendy Seltzer <wseltzer@w3.org> >wrote: >> >> >> >>> On 12/19/18 09:30, Mike West wrote: >> >>>> I should have sent this earlier, but my brain is already on >vacation. >> >>> I'll >> >>>> make up for it by keeping the meeting quite short: >> >>>> >> >>>> TOPIC: Charter for 2019. >> >>>> >> >>>> I've uploaded a draft 2019 charter >> >>>> ><https://w3c.github.io/webappsec/admin/webappsec-charter-2019.html>. >> >>> You >> >>>> can check out the diff to 2017's charter at >> >>>> >> >>> >> >https://github.com/w3c/webappsec/commit/1eb9873ac2e86d2156fba100db92cb3dd96fa342 >> >>> . >> >>>> I hope it's uncontrovercial, as it leaves the group's scope >untouched, >> >>> and >> >>>> only removes examples of specs we don't seem to be working on >(COWL >> and >> >>>> UISecurity). >> >>> >> >>> Thanks Mike! As we've agreed to adopt Feature Policy, shall we >add >> that >> >>> to the list? >> >>> >> >>> I sent a PR, https://github.com/w3c/webappsec/pull/539 >> >>> >> >>> Thanks, >> >>> --Wendy >> >>> >> >>>> >> >>>> Dial-in details for the webex calls are posted member-only >visible >> here: >> >>>> https://www.w3.org/2011/webappsec/webex.html >> >>>> >> >>>> Please join us on IRC and send "present+" for role-call: >#webappsec on >> >>>> irc.w3.org:6665 (https://irc.w3.org/?channels=webappsec) >> >>>> >> >>>> Thanks! >> >>>> >> >>>> -mike >> >>>> >> >>> >> >>> >> >>> -- >> >>> Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office) >> >>> Strategy Lead, World Wide Web Consortium (W3C) >> >>> https://wendy.seltzer.org/ +1.617.863.0613 (mobile) >> >>> >> >>> >> > >> >> >> -- >> Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office) >> Strategy Lead, World Wide Web Consortium (W3C) >> https://wendy.seltzer.org/ +1.617.863.0613 (mobile) >> >> -- Wendy Seltzer wseltzer@w3.org mobile +1.617.863.0613
Received on Wednesday, 19 December 2018 17:54:05 UTC