What should we call our new website and org? #23
Replies: 5 comments 2 replies
-
|
Why now geocompr.com ? It's available. |
Beta Was this translation helpful? Give feedback.
-
|
Could be an option, but re thinking of moving away from the focus on Geocomputation with R (geocompr) to geocompuation in with any language and in general (geocompx was my thinking on that). |
Beta Was this translation helpful? Give feedback.
-
|
I do not recommended using hyphen. There are several reasons and I regret doing it myself few times. I vote that you put your book on domain geocomputation.book. I.e. avoid too short cryptic names. Use the *.book extension! |
Beta Was this translation helpful? Give feedback.
-
|
I agree with that and was of the reasons for pitching geocomputation with x (geocompx) but that doesn't seem to be a popular option! |
Beta Was this translation helpful? Give feedback.
-
|
The x in geocompx is a nice way to put emphasis on the multi-language aspect of the project. I'd also be a bit concerned about trademark issues with geocomp.xyz because there are lots of companies coming up in google searches for "geocomp". |
Beta Was this translation helpful? Give feedback.
-
|
After a lot of debates we decided to use the geocompx name: see https://geocompx.org/ and https://github.com/geocompx |
Beta Was this translation helpful? Give feedback.
-
|
Yay, issue closed, question answered! |
Beta Was this translation helpful? Give feedback.
-
The Geocomputation with R project has come a long way since the first commit in the geocompr repo on 3rd March 2017. The community of users has grown. There are now almost 70 direct contributors to the original repo, many translations, and a thriving Discord group (new members welcome)! We also have a Geocomputation with Python book project living under the geocompr banner, in the geocompr/py repo.
If you think it's slightly incongruous for a book called Geocomputation with Python to live in an organization set-up to be about Geocomputation with R, you're not alone. For that reason, to encourage further projects, and to be more language agnostic, welcoming and future-proof, we (primarily @Nowosad and I but we have also discussed this elsewhere) think that it's time for a change.
Below are some options. We think all of them are viable. Feel free to add other ideas on names, URLs and the future of the Geocomputation with ... journey. And please let us know your thoughts with the vote buttons below!
29 votes ·
Beta Was this translation helpful? Give feedback.
All reactions