Closed cwickert closed 8 months ago
Regarding "Geeko", here is a mail from 2016:
Date: Tue, 4 Oct 2016 17:01:01 +0000
From: "Scott Corfield"
To: "DL-SU-All"
Subject: Is He a Chameleon or Gecko?
All,
There has been some recent discussions and questions within the company about
our SUSE mascot, which I would like to clear up today. Some have asked if our
mascot is a chameleon or a gecko.
Our mascot is a chameleon.
The confusion probably started more than 10 years ago when we gave our mascot a
name (Geeko) during an internal competition. Some must have assumed that since
his name was Geeko, he must be a gecko-but he's not.
Six years ago we made the decision to retire the Geeko name in hopes it would
prevent further confusion. So moving forward, please do not refer to our
chameleon mascot as Geeko or as a gecko.
Contact me if you have any questions, thx!!
Even though Scott is probably not 100% correct about the date (6 years before 2016 means 2010, but "Geeko" was still used in 2011 for the "Geeko Gazette" newsletter), we really should not use the name any longer.
- Unisex names like https://www.whattoexpect.com/baby-names/unisex-baby-names/
- Well-known placeholder names such as "Jane Doe" or "John Doe". Use the female by default. Can be localized for more diversity, see https://en.wikipedia.org/wiki/List_of_terms_related_to_an_average_person
I like option (1) much more than preferring clearly female names which imo is just as bad as preferring male names. One the other hand, a lot of the supposedly gender-neutral names sound either clearly male or clearly female to me (= non-native speaker) anyway, so it comes out to about the same.
Just as clarification: My idea was to make exampleuser female (Jane Doe) and exampleuserII male (John Doe). I doubt there are placeholder families (at least not in many languages), so for exampleuserIII we need something different anyway. We could then again take a female name or an unisex one – assuming there are well-known ones.
For exampleuserIII we would likely have to go for something else – I doubt there are placholder families in many languages
My idea was to make exampleuser female (Jane Doe) and exampleuserII male (John Doe).
So, for one, Jane Doe and John Doe look and sound very similar. I am not sure I would use them together in a document. To me, it seems it would be better if the names were more different from each other, also because many of our readers are not native speakers and may be more easily confused there than natives. (Their German counterparts Max Mustermann and Erika Mustermann are much better at being distinctive.)
Also, checking with the two most common methods of creating user account names for Jane & John Doe:
jdoe
and jdoe
(i.e. same)jane
& john
(same number of characters and a "j" and and an "n" in each)For two, example user No. 1 will be used much more often than No. 2. This means, in a sense, No. 1 always gets preferential treatment.
I would favour a list of names which are both gender-neutral and international.
There are not many, but we do not need many, so coming up with a very short list should not be too hard.
I did some research, consulted multiple websites, and weeding out some names I consider confusing/inappropriate (for example, many people now use placenames as given names), here are my results.
UK
UK/US:
Hispanophone world:
Korea (over 50% of people)
Chinese diaspora:
South Asia
Jan, Kim, Lee and Park are all familiar and commonly-used names to several totally different cultural/language/national groups.
I decided it's not worth opening yet another can of worms!
We currently use free-software mascots, such as Tux (kernel), Wilber (GIMP) or Geeko (SUSE) as example names.
This is what we have in doc-sle's entity-decl.ent right now:
PROBLEMS
exampleuserfull_plain
,exampleuserIIfull_plain
andexampleuserIIIfull
.exampleuser
andexampleuserII
are first names,exampleuserIII
is the last name.SUGGESTION
While the inconsistencies are trivial, we should pay attention to inclusiveness and diversity (refer to #148).
I see two possible paths there:
STATS
number of occurrences in doc-sle: exampleuser: 30 occurrences exampleuser_plain: 106 exampleuserII: 29 exampleuserII_plain: 12 exampleuserIII: 11 exampleuserIII_plain: 23 exampleuserfull: 0 exampleuserIIfull: 1 exampleuserIIfull: 1