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

Re: Split the `w3c/webappsec` respository?

From: Neil Matatall <oreoshake@github.com>
Date: Wed, 9 Sep 2015 08:57:07 -1000
Message-ID: <CAASU7Q5CO5pLW6KoM5d4wpRcrS19nuKi0OsZAuqqrQ6yDkVFUw@mail.gmail.com>
To: Eric Mill <eric@konklone.com>
Cc: "Oda, Terri" <terri.oda@intel.com>, Mike West <mkwst@google.com>, Francois Marier <francois@mozilla.com>, Wendy Seltzer <wseltzer@w3.org>, "public-webappsec@w3.org" <public-webappsec@w3.org>
I think w3c-webappsec/<spec-name> is a good route.

On Wed, Sep 9, 2015 at 8:40 AM, Eric Mill <eric@konklone.com> wrote:
> You can probably write GitHub and request they transfer
> https://github.com/webappsec to you. They're pretty quick and good about
> doing that if the account is truly idle.
>
> On Wed, Sep 9, 2015 at 2:29 PM, Oda, Terri <terri.oda@intel.com> wrote:
>>
>>
>>
>> On Tue, Sep 8, 2015 at 9:18 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. :)
>>>
>>
>> Actually, I think that does have the potential to be helpful in that it'll
>> make it easier for people to figure out which mailing list to take comments
>> to if they don't want to use github issues.  This could equally be achieved
>> with good readme files, of course, but there's something to be said for
>> making it clear that there's a w3c working group behind the ideas.
>>
>>  Terri
>
>
>
>
> --
> konklone.com | @konklone
Received on Wednesday, 9 September 2015 18:57:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:15 UTC