doc: add chalker as collaborator

[ChALkeR]

PR-URL: #1927

[Fishrock123]

LGTM

[ChALkeR]

Updated to the actual gitconfig name (as suggested in IRC) and GitHub username.
/cc @jbergstroem

[bnoordhuis]

LGTM and welcome aboard.

[jbergstroem]

LGTM!

[rlidwka]

That's the first fully non-ascii name we'll have in README. Is everybody okay with that?

[vkurchatkin]

Yeah, it's probably better to have it transliterated

[ChALkeR]

@rlidwka

I asked in the IRC about that and said that I could take one of two options for everything to match:

1. Use the cyrillic full name for the Readme.md (as the one that is in AUTHORS, GitHub profile and commits). This does not match with how other collabolators are listed.
2. Use the transliterated variant (as was initially in this PR), change it in AUTHORS with the same commit, and set it in the local git config. This will not match with GitHub profile and my commits to all other projects (both GitHub-hosted and not).

I was told (in IRC) by @bnoordhuis that the first variant should be preferred because of that's how it is mentioned the git history already.

I will hold off merging this until more people review this.

[ChALkeR]

@vkurchatkin It was initially transliterated in this PR, I was told not to.
Delaying merging until a consensus is reached.

[jbergstroem]

What's the counter argument against cyrillic? I don't have a strong opinion for either but the history reference @bnoordhuis brought up makes sense to me.

[rlidwka]

What's the counter argument against cyrillic?

People who aren't familiar with the language won't be able to read it, figure out how to pronounce it, and check if it's been copy-pasted to Reviewed-By correctly. I don't know how much of an issue it is, just pointing it out.

[vkurchatkin]

People who aren't familiar with the language won't be able to read it, figure out how to pronounce it, and check if it's been copy-pasted to Reviewed-By correctly. I don't know how much of an issue it is, just pointing it out.

+1

[ChALkeR]

@rlidwka@vkurchatkin Just for reference:

and check if it's been copy-pasted to Reviewed-By correctly.

Copy-pasting and checking the «Reviewed-By» field was the reason why I was asked to use a single variant everywhere, and this is why I changed the original PR in the first place.

[Fishrock123]

I'm not sure, I'm ok with having Cyrillic / etc character names in the readme, although, I would prefer something I can begin to pronounce. :)

Perhaps a compromise could be made where we have:
**full name** _(Transliterated)_ [@username]()?

[chrisdickinson]

That's the first fully non-ascii name we'll have in README. Is everybody okay with that?

I am ok with it – those of us who can't read it can always copy-paste it, or this might be a good motivator for us to pick up Cyrillic! :)

[tellnes]

I'd go for both cyrillic and translated version like @Fishrock123 suggests.

[jbergstroem]

I'm not a fan of keeping this PR (which is supposed to be the welcoming step) open for a slightly different discussion than what the PR itself accomplishes. I count enough LGTM's to merge -- how about we open a discussion elsewhere for improving README.md (and/or .gitconfig) in terms of i18n?

[brendanashworth]

+1 for @jbergstroem. Collaborator PRs are more symbolic, not really a place for this sort of discussion.

Anyways.. if we want to get technical and argue, other alphabets around the world carry letters and sounds that don't have English / Latinized equivalents. The "Latinize everything" approach wouldn't scale to lots of languages - just because Cyrillic is comparably similar doesn't mean we should make our decision based only off of this. (oh, and Cyrillic is easy to learn 😉)

[ChALkeR]

Ok, I am merging this as it is now, marking this as reviewed by people who reviewed the current version.
I changed the commit message, so if there will be a future consensus on how to write non-ASCII names, the transliterated name could be taken from there.