[phoe-krk]

> Then don’t make a whole big public announcement about it.

I don't understand. How do you resign from a public project without resigning from that public project? If it is not about the resignation but about the message, do you think that a "we are resigning as a whole team that was made pbulic and we do not provide any public reason for that" would work any better?

[whatshisface]

They could have resigned without making a post about it. Is that a good idea? Maybe, it depends on the details we don't know.

[kbenson]

And what, leave the Rust community not knowing that there's no CoC team because they've all resigned over something, but the community wasn't informed?

It's not like there's some membership card with paid dues. Their responsibility was to anyone that viewed themselves as part of the Rust community, and consumes anything to do with that community (whether or not they put anything into it).

Not informing all the people of that community because it appeases random public commenters would be a far worse failure of their duties than letting the general public gossip.

[whatshisface]

>leave the Rust community not knowing that there's no CoC team

They did have the option of finding replacements before leaving.

[colejohnson66]

Employees have no duty to find replacements for their employer. There's especially no moral duty if your bosses are being jerks. I'd say that logic applies to this situation as well.

[phoe-krk]

This isn't a post, it's a PR. If your names are listed in a public Git repository, then you need to have them removed if you resign. This means a PR and a review of that PR, which is exactly what happened here.