W3C home > Mailing lists > Public > public-webappsec@w3.org > September 2015

Re: Starting to create new repositories.

From: Deian Stefan <deian@cs.stanford.edu>
Date: Wed, 30 Sep 2015 07:29:22 -0700
To: Mike West <mkwst@google.com>, "public-webappsec\@w3.org" <public-webappsec@w3.org>
Cc: Wendy Seltzer <wseltzer@w3.org>, Dan Veditz <dveditz@mozilla.com>, Francois Marier <francois@mozilla.com>, Devdatta Akhawe <dev@dropbox.com>, David Ross <drx@google.com>, Frederik Braun <fbraun@mozilla.com>, Brad Hill <hillbrad@gmail.com>, Joel Weinberger <jww@google.com>, Yan Zhu <yan@eff.org>, Jochen Eisinger <eisinger@google.com>
Message-ID: <87si5w56bh.fsf@cs.stanford.edu>

Mike West <mkwst@google.com> writes:

> Hello editors and WebAppSecians!
> With Wendy's help, I've started separate repositories for three specs, as a
> demonstration of what I'd like to do with the rest of the documents the
> group is responsible for. We weren't able to create a new organization, as
> that would apparently break some upcoming magic that the W3C is interested
> in applying to all their repositories, so we ended up with the following:
> * https://github.com/w3c/webappsec-clear-site-data, published at
> https://w3c.github.io/webappsec-clear-site-data/
> * https://github.com/w3c/webappsec-epr, published at
> https://w3c.github.io/webappsec-epr/
> * https://github.com/w3c/webappsec-secure-contexts, published at
> https://w3c.github.io/webappsec-secure-contexts/
> These should contain the complete history of the relevant files, and no
> longer contain dependencies to files in the main webappsec repository.
> If there are no substantive objections, I'll go ahead and do the rest of
> the specifications, and start migrating issues over to the new
> repositories. Then we can talk to Wendy to get some secret tokens, and set
> up some exciting autopublication magic. :)

+1, thanks for doing this!

Received on Wednesday, 30 September 2015 14:29:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:52 UTC