Bozhidar Batsov

Perhaps the suggestion should be simply to be consistent in the usage of such macros.

Well, those macros are definitely not something particularly important, so no argument from me. The value they add is on the side of less typing, not clearer code. :-) Might...

On a more meta topic - I think that `if-not` generally reads poorly and the negative branch should naturally be `else` branch. ```clojure (if-not something foo bar) ;; same as...

@seancorfield I totally agree. I had originally borrowed this from https://clojure.org/dev/contrib_howto#_coding_guidelines and I didn't bother to extend the explanations, but I think this would be beneficial.

Fair point. We might also mention that it's fine to align the values as well, if one would like to make them stand out a bit more.

All macros/special forms that take a body parameter are indented differently, so I don't think there's anything special about the handling of `if`, `if-let` and so on. Can you elaborate...

Yeah, I guess that's a valid point. Perhaps the bare `if` deserves some special treatment, or at least a disclaimer.

> Is there similar consensus that names of boolean values should be suffixed with a question mark? Let's ask around. I don't do it myself (mostly because I'm too used...

What I dislike about alignment such as the proposed one is the impact on diffs each time you a longer name in the let that would require pushing all of...

> I think the only big thing to resolve would be the licensing / contribution question. The Clojure site repo content is EPL and governed under the Clojure CA. I...