The work, for now, is focused on changing a lot of references in the code from TC-related terms to CS-related terms. Obviously if the name is changed a lot of this work will go down the drain since everything will need to be changed again. Worse, one will need to watch out for both TC terms and CS terms unless the project starts from the beginning again. Please tell me where exactly I'm wrong here.
The current name was chosen carefully by the people in charge. In my opinion it's both good and original. Apparently a lot of the people interested in the name now weren't there to voice their opinion when it was chosen. Of course I know that CS didn't win that vote pool, but it came second and the first place got thrown out due to obvious copyright issues. From what I remember nobody really cared until over a month later, when the new name thread was made.
It also doesn't take a lot of compassion to throw in a random name suggestion, when one was already decided on months earlier. Discussion is good, but in my opinion this particular discussion is pointless, since the devs themselves said they won't change the name. Why discuss something that won't be changed no matter what?
No, I'm not. I believe I stated this several times in the past in other threads, but here it goes again.
Donating money to anything doesn't entitle the donor to anything. I can agree somewhat to the fact that TC devs were unresponsive, but on the other hand I can see how they thought of it as part of their OPsec, which apparently worked since no one knows who they are.
I believe I should also point out two things. First, this project has absolutely nothing to do with the TC devs, with the exception of using the TC code (obviously). Directing your anger caused by them at me or anyone else is stupid. Second, as I stated earlier, the devs won't change the name. The name discussion, in the current situation, is people yelling at a wall. So I still feel confident in saying this discussion is pointless.
I agree that projects are powered by people with often crazy suggestions, and think the community can easily help with said suggestions. Making sure that the community and the devs work together well is important, and both sides in this are important, contrary to what you may think I think. However if the community feels entitled to tell the devs exactly what to do and is angry that they do things their way, someone has to put the community in its place. Because if that doesn't happen, then the devs can pack up and leave out of anger, and the project really dies. Unless of course you think this project can be powered with the power of one name suggestion a week.
If I had someone over my shoulder tell me how to do my work, or that they don't like how I do my work, I'd quit. And I most certainly see the fact that if this continues, the devs probably will stop completely the already slow work they do and quit. I can assure you that it's then that the project will die, and it will happen because of the community.