On Mon, Nov 28, 2022 at 6:06 PM 'David Adrian' via blink-dev <
[email protected]> wrote:

> The Google Doc is the same as the explainer. The documentation is public.
> The Google Doc is not public because it is not a Chromium-organization doc,
> it is a Google owned document.
>

Apologies, I should've caught that during the review, but can you render
the document's contents public? (e.g. copy them over to a Chromium doc)
Skimming through the doc, it doesn't seem to contain any non-public
information.


> On Mon, Nov 28, 2022 at 4:57 AM ayumi hamasaki <[email protected]>
> wrote:
>
>> Hi,
>>
>> Why is the  Documentation link blocked to the public?
>>
>> Steps to repeat issue:
>>
>> 1. Go to link: https://chromestatus.com/feature/5124606246518784
>> 2. Under Documentation Tab
>>
>>    -
>>    
>> https://docs.google.com/document/d/1NIeWj_xFE3p7Q2IxVjnztO4_Aqih3VAskHlLYqDFjvk/edit?resourcekey=0-FCsdas1l23L830egKOun4A
>>
>> 3. Access denied
>>
>> This is the first time I've ever seen a documentation being blocked to
>> the public, can Googlers not go down that route please! Can you make all
>> Documentation links public so we can see more information about this issue!
>>
>> p.s. The explainer found here:
>> https://github.com/dadrian/clienthello-randomization/blob/main/EXPLAINER.md
>>
>> Adds little extra information with regards to the issue, hence why I
>> have bated breath hoping to open the google docs link to understand more
>> about this issue!
>>
>> Many Thanks.
>>
>> On Wednesday, 23 November 2022 at 15:41:37 UTC Daniel Bratell wrote:
>>
>>> LGTM3
>>>
>>> /Daniel
>>> On 2022-11-23 04:53, Yoav Weiss wrote:
>>>
>>> LGTM2
>>>
>>> On Tue, Nov 22, 2022 at 5:14 PM Mike West <[email protected]> wrote:
>>>
>>>> LGTM1, modulo surprises in the standards positions feedback.
>>>>
>>>> This is clearly a security-positive change, insofar as it preserves our
>>>> ability to make changes to TLS over time. I expect you'll need a careful
>>>> rollout (and that middleboxes will cause problems), but I also expect you
>>>> know that already. :)
>>>>
>>>> Good luck!
>>>>
>>>> -mike
>>>>
>>>> On Friday, November 18, 2022 at 10:12:21 PM UTC+1 Yoav Weiss wrote:
>>>>
>>>>> No worries :) thanks for filling out those requests for positions
>>>>>
>>>>> On Fri, Nov 18, 2022, 21:04 David Adrian <[email protected]> wrote:
>>>>>
>>>>>> Apologies---this is my first time going through the Blink process,
>>>>>> but I should have caught the formal signal step.
>>>>>>
>>>>>> I've filed requests for positions from Mozilla [1] and WebKit [2].
>>>>>>
>>>>>> [1] https://github.com/mozilla/standards-positions/issues/709
>>>>>> [2] https://github.com/WebKit/standards-positions/issues/92
>>>>>>
>>>>>> On Thu, Nov 17, 2022 at 7:15 PM Yoav Weiss <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Nov 18, 2022 at 1:28 AM Martin Thomson <[email protected]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Nov 18, 2022 at 10:15 AM 'David Adrian' via blink-dev <
>>>>>>>> [email protected]> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> *Gecko*: Positive (
>>>>>>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/zdmNs2rTyVI/m/MAiQwQkwCAAJ
>>>>>>>>> ) https://bugzilla.mozilla.org/show_bug.cgi?id=1789436
>>>>>>>>>
>>>>>>>>
>>>>>>>> To be clear, though we are supportive of this change, we ask that
>>>>>>>> you ask using https://github.com/mozilla/standards-positions
>>>>>>>> rather than use inferences (even obvious ones) based on mailing list
>>>>>>>> posts.  Dennis is the authority here, so no big deal, but this process
>>>>>>>> exists to avoid miscommunication.
>>>>>>>>
>>>>>>>
>>>>>>> What Martin said + can you ask for a signal from WebKit folks?
>>>>>>>
>>>>>>>> --
>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>> Groups "blink-dev" group.
>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>> send an email to [email protected].
>>>>>>>> To view this discussion on the web visit
>>>>>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPLxc%3DVRR-R%2B1tDJELZvqDPENxcT%2Bi-OZntifmqsZOHkyGzHOg%40mail.gmail.com
>>>>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPLxc%3DVRR-R%2B1tDJELZvqDPENxcT%2Bi-OZntifmqsZOHkyGzHOg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>>>>> .
>>>>>>>>
>>>>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "blink-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfU5Kde%2B_%3DgHOBUKm2a%3DqB6ju4u9zDfjWo-YLSGsjgRNWA%40mail.gmail.com
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfU5Kde%2B_%3DgHOBUKm2a%3DqB6ju4u9zDfjWo-YLSGsjgRNWA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGkh42LXjeC%2BP-LpNNjD-TtvetSPn22H0b%2BwbwtRC8p8aopt8A%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGkh42LXjeC%2BP-LpNNjD-TtvetSPn22H0b%2BwbwtRC8p8aopt8A%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXChKgEkDotF9L6ovZ8yKU6SttcioDVGdunxDVj4By90g%40mail.gmail.com.

Reply via email to