This a delicate matter and can not be resolved easy, I am not in charge of the COGH project, but I can add some information and knowledge
Ronel, you are project leader for South African Roots & substitute for Susan on COGH (which is a sub-project to SAR). So you do have much influence
I am very unhappy that my ancestor's profiles, where I have original documents stating the place to be "Cabo de Goede Hoop", are being changed to "Dutch Cape Colony".
This was already explained to you in the private conversation we had. Pointing out that we needed to have a distinction between the time periods when the VOC and Britain was in charge, but as Louis pointed out a rather poor choice it seems and used incorrectly it seems, but it was the best solution at the time.
The choice was obvious: You should have checked the Wikitree location naming protocol and followed it by NOT using "Dutch Cape Colony" but the closest English equivalent: "Cape of Good Hope". This is still not strictly correct but would be an acceptable compromise to accommodate English-only readers.
I am sure if anyone had a better workable solution the Project would have been happy to use it :-)
What I am suggesting now, belatedly, is the "better workable solution".
Also that persons who intentionally change event names to other than Wikitree guidelines be barred from doing so.
We can not bar anyone from editing profiles and I would recommend you correspond with the persons involved or if you can not come to an agreement ask a mediator to intervene and help solve the problem
The person involved was Philip. From Philip's latest G2G reply: "I only want to accommodate the truth as historically proven. Those who know me can vouch for that. For now I'm waiting for the leaders to weigh in."
I interpret that as that he now agrees with me (regarding place names for birth, marriage & death.)
We all have action on profiles we manage that are incorrect or controversial and I am happy to report WikiTree made available the option to reverse changes, should you feel you have exhausted your options of communication. :-P
So that is another option.
I formally request that the term "Dutch Cape Colony" be removed from the list of allowable event place names.
This is not a decision that can be made by only a few members or leadership alone.
As a start and a showing of good faith on your part, all you need to do is to remove the words "Dutch Cape Colony" from the Cape column in the SA country names table. That one single action should prevent the problem from getting bigger by the day.
We need a mandate from the Cape of Good Hope members before we can just remove place names on a large scale. .
Do you really think you need a vote to correct a mistake you made 6 years ago? It boils down to correcting a spelling mistake!
I recommend we start a voting process.
If it makes you happy, do it, but look at my suggestion below and then explain to the members that it is to correct a mistake which is absolutely contrary to Wikitree location naming protocol.
A vote option should be available to all members as this will result in a huge amount of profiles that must be changed, if we do start to change about 20 000 profiles the members need to know the intention and or reason.
If we go for the compromise of using "Cape of Good Hope" instead of "Dutch Cape Colony", it could be done by using a substitution program. I am sure Brian Casey could help under the circumstances. To quote Wikitree's own words:. "Brian is our system administrator. Our lead programmer. Our hacker-in-chief" He helps Chris Whitten, Founder and President of Wikitree. (They may wish to replace with "Cabo de Goede Hoop", if they insist on conformance to the location naming protocol).
.If you do it this way, nobody has to do anything manually on any profile.
I hope this will help explain the reason for the changes and also how we might resolve the matter
If we can do this within the SA group (maybe with the help of the 'Head Office' techie), It would be much better than If I had to go through all 8 stages of conflict escalation, (right up to Chris Whitten),.