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

Re: Split the `w3c/webappsec` respository?

From: Joel Weinberger <jww@chromium.org>
Date: Wed, 09 Sep 2015 17:18:57 +0000
Message-ID: <CAHQV2K=bWzzSUmGdNvXxpXJO0e2PWGhkeLC6y3n0Tp0xhWFW6g@mail.gmail.com>
To: Mike West <mkwst@google.com>, Francois Marier <francois@mozilla.com>, Wendy Seltzer <wseltzer@w3.org>
Cc: "public-webappsec@w3.org" <public-webappsec@w3.org>
I lean against this decision, as the benefits seem relatively small to me,
and change scares me (or, more accurately, I fear unknown, unintended
consequences; the unknown unknowns, if you will). Most of the benefits, to
me, seem to be around GitHub notifications, and it seems like we could
probably fix this with better tagging in GitHub.

My objection is relatively minor, however. If we did do a split, then I
would support Dev's suggestion of using "webappsec-" prefixes, to make it
clear where to look for discussions.

On Tue, Sep 8, 2015 at 9:21 PM Mike West <mkwst@google.com> wrote:

> On Wed, Sep 9, 2015 at 12:12 AM, Francois Marier <francois@mozilla.com>
> wrote:
>> Can we keep the name "webappsec" in the repo name? Something like
>> "w3c/webappsec-sri" and "w3c/webappsec-cowl". That way it will be easy
>> to find / browse all of the repos related to our working group.
> It's not clear to me that that would help anyone who wasn't in this group.
> :)
> That said, the TAG has split off into w3ctag/*. Perhaps we could ask our
> wonderful staff contact if she could fork off a `webappsec` (or
> `w3c-webappsec`? `w3cwas`? since "webappsec" seems to be taken...)
> organization for our repositories? +Wendy
> -mike
Received on Wednesday, 9 September 2015 17:19:35 UTC

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