Scrabble is a trademark name.

[kotp]

It should be capitalized. It is also a noun, meaning a "doodle", and a verb, such as what this description could be considered.

In our case, we are referring to the trademarked name of the game Scrabble.

[kotp]

It was suggested that this change is good, but perhaps a little bit subtle. Should we mention that Scrabble is a game, or is the description suitably vague to encourage just a little bit of research?

[petertseng]

Then, you may also like to change some other instances of the uncapitalised word "scrabble".

exercises/etl/canonical-data.json:        "Transforms a set of legacy scrabble data stored as letters per score",
exercises/etl/description.md:We're going to extract some scrabble scores from a legacy system.
exercises/etl/description.md:The shiny new scrabble system instead stores the score per letter, which
exercises/scrabble-score/description.md:Given a word, compute the scrabble score for that word.
exercises/scrabble-score/metadata.yml:blurb: "Given a word, compute the scrabble score for that word."

of course, choosing not to do so wouldn't be grounds for refusing this PR, it would just be an indication that perhaps there is more work to be done.

[kotp]

Good idea, keeps it in line with the PR, and appropriate.

[yawpitch]

We should not change the exercise name in the canonical-data.json “exercise” field. Several other exercises have proper names in that field (armstrong-numbers and pascal-triangle for example) and there’s no sense settings the precedent for a corporate trademark over a human person’s name. Plus this is used to map to a directory on the file system in at least one script I can think of, so this would end up forcing brittle case comparison and could cause real problems with case-sensitive file systems.

[kotp]

We should not change the exercise name in the canonical-data.json “exercise” field. Several other exercises have proper name’s in that field (armstrong-numbers and pascal-triangle for example) and there’s no sense settings the precedent for a corporate trademark over a human person’s name. Plus this is used to map to a directory on the file system in at least one script I can think of, so this would end up forcing brittle case comparison and could cause real problems with case-sensitive file systems.

I was thinking it might be "sensitive". Thanks for the confirmation.

[joshgoebel]

I think the changes elsewhere are good. It's a proper noun if nothing else, hence deserving of caps.

[rpottsoh]

Versioning on json is blocking.

[yawpitch]

Since there is now no substantive change to the canonical-data.json file could that be removed from the PR rather than have a whitespace-only change?

[yawpitch]

Ok, I believe this repo is still “locked” (see #1560) and this isn’t technically a bug fix change, but it’s now non-impactful and con-controversial, so should be okay to merge.

[kotp]

Sorry, trailing whitespace is making noise... I can make this a separate commit, if anyone is having problems with it being included here.

[petertseng]

well of course. including a whitespace change in a commit whose commit message mentions Scrabble means that the commit message tells an untruth.