Github user xpe commented on the pull request:
https://github.com/apache/incubator-storm/pull/130#issuecomment-45163796
@revans2 Hello. The quality of the Storm code varies. It could stand some
improvement. Just like any project that is useful enough to live on, it spans
versions. It also spans the improvement in coding style of its contributors.
I'm with you; I don't want an arbitrary debate. I'd suggest "defining"
Storm's desired style, roughly, as what 80% of the Clojure community is
currently doing. The rest could be left open. Over time, it probably will
distill itself with little work on our part.
What is the 80% of less-than-controversial advice? I suggest we point
people to these useful references (to answer your documentation question):
* http://dev.clojure.org/display/community/Library+Coding+Standards
* https://github.com/bbatsov/clojure-style-guide
> Is there an automated tool that you used that can help with this
formatting as well?
Many people use Paredit or their editor. If I see a lint tool, I will let
you know. I see that https://github.com/jonase/eastwood is one kind of linter;
it might be worth a look. I'll keep my eyes open.
@revans2 I'll submit a pull request. Can you merge quickly? The longer we
wait, the more merge conflicts we'll get.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
