{"action":"created","issue":{"url":"https://api.github.com/repos/SUSE/doc-styleguide/issues/85","repository_url":"https://api.github.com/repos/SUSE/doc-styleguide","labels_url":"https://api.github.com/repos/SUSE/doc-styleguide/issues/85/labels{/name}","comments_url":"https://api.github.com/repos/SUSE/doc-styleguide/issues/85/comments","events_url":"https://api.github.com/repos/SUSE/doc-styleguide/issues/85/events","html_url":"https://github.com/SUSE/doc-styleguide/issues/85","id":370124633,"node_id":"MDU6SXNzdWUzNzAxMjQ2MzM=","number":85,"title":"back-end should be backend","user":{"login":"dmpop","id":837588,"node_id":"MDQ6VXNlcjgzNzU4OA==","avatar_url":"https://avatars0.githubusercontent.com/u/837588?v=4","gravatar_id":"","url":"https://api.github.com/users/dmpop","html_url":"https://github.com/dmpop","followers_url":"https://api.github.com/users/dmpop/followers","following_url":"https://api.github.com/users/dmpop/following{/other_user}","gists_url":"https://api.github.com/users/dmpop/gists{/gist_id}","starred_url":"https://api.github.com/users/dmpop/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dmpop/subscriptions","organizations_url":"https://api.github.com/users/dmpop/orgs","repos_url":"https://api.github.com/users/dmpop/repos","events_url":"https://api.github.com/users/dmpop/events{/privacy}","received_events_url":"https://api.github.com/users/dmpop/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-10-15T11:45:42Z","updated_at":"2018-10-16T20:17:18Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"There are actually no clear rules governing compound nouns, i.e., both *backend*, *back end*, and *back-end* are correct. See, for example: https://dictionary.cambridge.org/de/grammatik/britisch-grammatik/about-nouns/nouns-compound-nouns\r\n\r\nHowever, *back-end* can be misinterpreted as an adjective, and *back end* can introduce ambiguity in certain contexts. So to simplify things, it would make better sense to write compound nouns as one word."},"comment":{"url":"https://api.github.com/repos/SUSE/doc-styleguide/issues/comments/430385062","html_url":"https://github.com/SUSE/doc-styleguide/issues/85#issuecomment-430385062","issue_url":"https://api.github.com/repos/SUSE/doc-styleguide/issues/85","id":430385062,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMDM4NTA2Mg==","user":{"login":"sknorr","id":5476547,"node_id":"MDQ6VXNlcjU0NzY1NDc=","avatar_url":"https://avatars0.githubusercontent.com/u/5476547?v=4","gravatar_id":"","url":"https://api.github.com/users/sknorr","html_url":"https://github.com/sknorr","followers_url":"https://api.github.com/users/sknorr/followers","following_url":"https://api.github.com/users/sknorr/following{/other_user}","gists_url":"https://api.github.com/users/sknorr/gists{/gist_id}","starred_url":"https://api.github.com/users/sknorr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sknorr/subscriptions","organizations_url":"https://api.github.com/users/sknorr/orgs","repos_url":"https://api.github.com/users/sknorr/repos","events_url":"https://api.github.com/users/sknorr/events{/privacy}","received_events_url":"https://api.github.com/users/sknorr/received_events","type":"User","site_admin":false},"created_at":"2018-10-16T20:17:18Z","updated_at":"2018-10-16T20:17:18Z","author_association":"CONTRIBUTOR","body":"Whatever level of silliness one assigns to this spelling (which is essentially an arbitrary/personal value), the fact that we've been writing like that for multiple years should be taken into consideration.\r\n\r\nI know some of our docs are not style checked particularly well, but e.g. SLES docs are. So, there's an obvious disincentive to change the spelling of this rather common term if both versions are correct (as in: work for writers, cost for retranslation)."}}
{"actor":{"display_login":"sknorr"}}