> There is a real cost to changing APIs/documentation/UIs. This is an OSS project. If someone cares enough about it, they should submit a (non-breaking) patch

> There is a real cost to changing APIs/documentation/UIs. This is an OSS project. If someone cares enough about it, they should submit a (non-breaking) patch along with a patch for the documentation. There are no costs to people who don't find it a valuable change. > My experience talking to black (one African, one European) coworkers is their reaction is "That's the problem you're going to fix?". Obviously this isn't fixing any of the fundamental issues, but it does bother some people. My preference is to respect the people who have problems with it. An easy policy is to simply avoid creating new software which uses that terminology and to accept any patches which fix it. That way the people who feel the change is important bear the burden of the cost (which is likely small some thing like this).