zlacker

[parent] [thread] 4 comments
1. leodri+(OP)[view] [source] 2023-07-21 18:59:20
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.

replies(2): >>joseph+f4 >>andret+ok
2. joseph+f4[view] [source] 2023-07-21 19:18:59
>>leodri+(OP)
Has there ever been a case of someone locking GitHub issues while being in the right?
3. andret+ok[view] [source] 2023-07-21 20:30:02
>>leodri+(OP)
> 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/...

replies(2): >>Button+ut >>lucide+YN
◧◩
4. Button+ut[view] [source] [discussion] 2023-07-21 21:10:52
>>andret+ok
The firestorm will be worse by then. I predict this RFC will not allow comments.
◧◩
5. lucide+YN[view] [source] [discussion] 2023-07-21 22:55:55
>>andret+ok
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...

[go to top]