zlacker

The issues tab is a fun read - never seen a response like this on a web spec.

>>lucide+(OP)
They seem to have closed down comments on it, I'm seeing

> An owner of this repository has limited the ability to comment to users that have contributed to this repository in the past.

>>leodri+C1
Has there ever been a case of someone locking GitHub issues while being in the right?

>>leodri+C1
> I’m giving everyone a heads up that I’m limiting comments to contributors over the weekend so that I can try to take a breath away from GitHub. I will reopen them after the weekend

https://github.com/RupertBenWiser/Web-Environment-Integrity/...

>>andret+0m
The firestorm will be worse by then. I predict this RFC will not allow comments.

>>andret+0m
Does it disturb anyone else that this is (a) in a personal namespace & (b) reason given for closing discourse being a single individual's need to disconnect from work at the weekend, when that person is employed by a large corp to maintain this spec which they are implementing in their product?

Surely Google as an org, if they're behind this, or at least a standards bodies own org namespace should both own this project, and also decision making around discourse, with any individual employees being free to leave the project un-answered outside of working hours?

This isn't some open source passion project someone's doing in their off time...

>>lucide+(OP)
https://github.com/RupertBenWiser/Web-Environment-Integrity/...

I never thought I'd see a CoC being used as ammo against this, but it's excellent.