Hi, Maxim Cournoyer <maxim.courno...@gmail.com> writes:
>> I don’t think that’s related, is it? I think few of us care whether >> people use two spaces in commit messages, but I’d personally be more >> picky in text snippets because I find it clearer… > > It's related in that we're discussing contributing guidelines that cause > friction for newcomers and add limited value. I think the two-spaces > convention must feel similarly baroque as the GNU ChangeLog git commit > messages for newcomers. Yes, I understand, and I agree reducing friction is a worthy goal. Having reviewed documentation changes, I think that double-space is a minor hindrance compared to the other requirements we have for documentation. For example, we usually insist on documenting services in the manual, starting with an introduction giving some context and links, providing a minimal example, and following a number of other typographic conventions. This is quite demanding for contributors but I think it’s also something we appreciate as users. For package synopses and descriptions, it may cause more friction in otherwise simple patches, though that’s just one of the elements of the “Synopses and Descriptions” guidelines. In short, I think it’d be easier to keep the discussion focused on commit messages first, and I doubt anyone would insist on two-spaces in this context (I wouldn’t! :-)). Ludo’.
