Earlier quoted context omitted.
> Content moderation at GitHub scale is hard and sometimes mistakes are made. This is completely fair, but lack of transparency makes it significantly more frustrating.
Agree strongly with this. If a repo is public and gets banned, I think it's reasonable to expect that the community can know why , regardless of the rights or wrongs of the decision.
* Sometimes legal counsel provide advice that there should be no further response to the individual or organization. Often technical people don't understand this situation, but it doesn't change the merits of the legal advice. In smaller organizations a leader might take a chance in further engagement, if they think it's helpful, but it's unlikely a large organization would expose themselves to this risk.
* Breakdown in internal response processes. You'll find that many people are really uncomfortable in these situations (e.g. compliance team shut down service, but don't "own" the response.) Unless the legal team has written a response and instructions on how to deliver it, you will often see people in organizations avoid giving the response. Things get passed down as low as they can go which doesn't help because there is less experience with handling tough situations. Very often some poor person with support ends up having to give the response and they basically ignore it because they can avoid the situation. This isn't very professional of the organization, but it's a reality.