- From: Robin Berjon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Mar 2022 15:10:06 +0000
- To: public-patcg@w3.org
>> we can clearly communicate the status of the document. > > This does not work in my experience. At all. Hence my objection. I am keenly aware of the problem you are describing, but I don't think that your solution to it works. There are two constituencies to consider. On the one hand are people who don't understand that discussing something is different from adopting. For that constituency, whether you say "This is only a proposal for discussion." at the top, or whether you store it at https://github.com/darobin-personal-account-go-away/personal-karaoke-notes/blob/dangerous-experimental-branch/stupider-ideas/DO-NOT-READ-THIS.md with a blinking marquee of capybaras at the top singing _Never got no con-sen-sus, Never gonna imp-le-ment_ it will _still_ get breathlessly described as "_The New York Times hates the Web, is going to lock up donkeys in the privacy sandbox._" Case in point: Topics is a Markdown file in a personal GitHub repo and it still got picked up as basically _fait accompli_ on the Web. The other constituency is folks who'll pay attention to the distinction. I think we should optimise for this group, not because they matter more but because we know how to solve this. -- GitHub Notification of comment by darobin Please view or discuss this issue at https://github.com/patcg/proposals/issues/4#issuecomment-1065201457 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 March 2022 15:10:08 UTC