| 18:50 | <littledan> | someone with permissions may want to delete this bizarre comment https://github.com/tc39/ecma262/issues/2229 |
| 18:57 | <Bakkot> | pretty sure that is a person with a fairly severe mental health issue; those always make me sad |
| 18:59 | <Bakkot> | cc akirose MylesBorins robpalme, this issue should be locked and the user blocked, probably on behalf of the tc39 org rather than a personal account |
| 18:59 | <Bakkot> | not sure who else has locking perms |
| 19:00 | <MylesBorins> | can you email the code of conduct team |
| 19:00 | <MylesBorins> | ? |
| 19:01 | <MylesBorins> | I'm on it but we should follow the protocol here at least to document |
| 19:01 | <MylesBorins> | tc39-conduct-reports⊙gc |
| 19:01 | <MylesBorins> | I can send the email |
| 19:04 | <robpalme> | Locked. I don't think I can delete. |
| 19:05 | <MylesBorins> | we actually don't have delete turned on |
| 19:05 | <MylesBorins> | we should make a request to the COC team if we are going to enable that I thinks |
| 19:05 | <MylesBorins> | (checked org settigns) |
| 19:05 | <ljharb> | i reported it to github, at least |
| 19:06 | <ljharb> | we could transfer it to a private "holding" repo if there's concerns about deletion, fwiw. probably best for the coc team to discuss |
| 19:07 | <ljharb> | MylesBorins: they also posted https://github.com/tc39/ecma262/issues/2230; would you mind blocking them from the org ASAP to prevent further spam, pending CoC team discussion? |
| 19:08 | <Bakkot> | recommend not locking from a personal account, incidentally |
| 19:09 | <Bakkot> | since they can see you did it, which may make you personally a target for harassment |
| 19:09 | <MylesBorins> | blocked |
| 19:09 | <ljharb> | indeed that's true, but i don't think we have a non-personal account available for that purpose atm |
| 19:09 | <ljharb> | i don't mind putting my name on it in the interim] |
| 19:09 | <ljharb> | MylesBorins: ty |
| 19:19 | <MylesBorins> | side bar, I'm opening an internal issue with github trust+safety team about protecting privacy of moderators |
| 19:27 | <Bakkot> | fwiw I believe the moderator-only actions - locking the thread, in particular - don't expose your username to people not in the org |
| 20:32 | <devsnek> | indeed |