The Terms of Use is written in Markdown. When using Markdown with Git, many people place each new line of text on a new line. For example, the README of Images.jl or the README of haskell-language-server. These newlines are convenient for people who use more advanced text editors, like Vim and Emacs, to quickly manipulate sentences. More importantly, they improve the readability of the diff.
Just now, I received a mail to inform me about the updated Terms of Use for COS websites and services. This mail contains a link to the diff of the Terms of Use. Specifically, https://github.com/CenterForOpenScience/cos.io/pull/1025/files. One of the changed lines went from 458 words to 513 words. The exact change is non-trivial to detect.
With this issue, I would like to request for the next Terms of Use change to be placing new sentences on new lines if possible, so that the changes can easily be inspected.
The Terms of Use is written in Markdown. When using Markdown with Git, many people place each new line of text on a new line. For example, the README of Images.jl or the README of haskell-language-server. These newlines are convenient for people who use more advanced text editors, like Vim and Emacs, to quickly manipulate sentences. More importantly, they improve the readability of the diff.
Just now, I received a mail to inform me about the updated Terms of Use for COS websites and services. This mail contains a link to the diff of the Terms of Use. Specifically, https://github.com/CenterForOpenScience/cos.io/pull/1025/files. One of the changed lines went from 458 words to 513 words. The exact change is non-trivial to detect.
With this issue, I would like to request for the next Terms of Use change to be placing new sentences on new lines if possible, so that the changes can easily be inspected.