Stream: rust-survey-2019

Topic: Add languages having a survey translation to demographics Qs

DH (Dec 02 2019 at 06:30, on Zulip):

Hi, this is DH who translated Rust survey of the last and this years to Korean.

In the list of languages in the question asking language fluency , in the "Demographics" section, Korean, for instance, is not included. I added Korean to the top of the list last year while being afraid of confusing the result aggregation (since one who do it may be confused by the different ordering of languages). This year I put Korean right before "etc." item.

If I were one answering the survey with a translation to one's mother tongue, I'd expect my mother tongue to be in the list. So I think it would be better to add all the languages with a translation of the survey to the list. Or we may set a rule for translators that one's target language should be placed at the top or end of the list.

What do you think?

apiraino (Dec 02 2019 at 08:58, on Zulip):

I think @DH you do have a great point :)
If time allows to further edit the master form, I'd vote to update all translations to reflect this change: add the form language as first language of that list.
However I'm not sure what happens when putting different labels on the first item of that list. Is the results correctly aggregated or do we end up with a lot of "first item choice" (actually corresponding to the value of the first item in the master form)?
hope I could explain what I mean :-)

XAMPPRocky (Dec 02 2019 at 09:21, on Zulip):

I believe the intent is to publish the survey today, so I don't know if there's time to change master survey, and update the other surveys. Not that your point isn't valid, whether the translations can add extra item, I think that's up to @Jasun Carr I don't know if this affects the results of the survey.

DH (Dec 02 2019 at 09:42, on Zulip):

It's ok not to immediately remedy the situation. It would be good enough if we can reflect such a consideration to the next survey.

nikomatsakis (Dec 02 2019 at 13:28, on Zulip):

we should definitely be taking some notes for next year

Santiago Pastorino (Dec 02 2019 at 13:31, on Zulip):

that sounds good :+1:

Santiago Pastorino (Dec 02 2019 at 13:32, on Zulip):

https://docs.google.com/document/d/1hUJ_76ufq_5-qlBftgEgpa8EHXpznklAk-pdRryS1mM/edit?usp=sharing

Santiago Pastorino (Dec 02 2019 at 13:32, on Zulip):

@DH can you add your thoughts there?

Santiago Pastorino (Dec 02 2019 at 13:56, on Zulip):

just changed the link to Google docs so we keep a copy on the Survey Drive directory

nikomatsakis (Dec 02 2019 at 13:58, on Zulip):

k

DH (Dec 03 2019 at 01:26, on Zulip):

@Santiago Pastorino I'll leave some note there shortly.

Jasun Carr (Dec 03 2019 at 15:53, on Zulip):

@DH Well, that's an embarrassing oversight... Go ahead and leave Korean as an option in the Korean translation (it won't negatively effect the survey results) and let's definitely add an item on the changes/notes for next year to make sure that all translated languages are included in the language list.

DH (Dec 03 2019 at 22:30, on Zulip):

@Jasun Carr Korean is already at the bottom of the choices this year, right before the Google Forms generated last item ('other' in English? Google Forms show me that in Korean to me). Thanks for confirming that it's ok to add Korean to the choices from your professional perspective.

Last update: Jan 28 2020 at 01:55UTC