go-spatial
Suggestion: Move off .io ccTLD
In keeping with the letter, but definitely the spirit of this project's Code of Conduct, I suggest moving off the .io ccTLD, tegola.io
.io is for the "British Indian Ocean Territory", and fees go to support the British military occupation, which has carried an effective genocide of an entire people (the Chagossians). A CIA black site is rumored to be operating there. In recent weeks, the United Nations' International Court of Justice has ruled the occupacion illegal. read more
Funding such racist, imperialist actions cannot be seen as supporting anti-racism. Yes, it will be inconvenient to move domain and backlinks, but most CoCs "prioritize marginalized people’s safety over privileged people’s comfort", so in that spirit, I recommend that you move the domain.
See more:
- https://en.wikipedia.org/wiki/Expulsion_of_the_Chagossians
- https://www.chagossupport.org.uk/
1½ years later and no response. Shall we interpret that this is not viewed as a CoC issue, and yous will take no action on this area?
@rory To be honest, this is just not a top priority right now. I appreciate you opening the issue but just opening the issue is only a portion of the effort. The request here is for us to uproot our established domain which as you mentioned is inconvenient. I have considered moving https://tegola.io to https://tegola.go-spatial.org, but this will require combing through the documentation in this repo and finding all references and making the necessary changes.
Are you willing to open a PR with the necessary documentation changes if I make the DNS adjustments?
From the Tegola CoC.
Project maintainers have the … responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct
Sorry, but you signed up for it. Or just drop that part of your CoC.
@rory I think you're missing the spirit of open source. We develop tegola in the open with a very liberal license, we're excited to engage with the community, and we welcome new ideas and people surfacing concerns (like you're doing). This considered, we're not required to attend to every request that's made.
You seem very passionate about this topic, which is great. I'm not as passionate about it, but I did provide an opening for you to help move the request forward. I simply asked for you to make the adjustment to the documentation and send in a PR. I would then follow-up with the associated DNS migration. Rather than use your time to move your request forward you chose to spend your time reading the code of conduct, quoting it, and then trying to shame us into complying with your request. It's probably similar or marginally more effort to make the modification to the documentation and send in the PR.
I will provide the offer again. If you're willing to make the effort to update the docs to align with your request, then I will make the necessary DNS changes. If not, then we can either leave this issue open or close it. It's up to you.