This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-10-14
Channels
- # admin-announcements (21)
- # aws (5)
- # boot (41)
- # cider (76)
- # cljs-dev (15)
- # clojure (251)
- # clojure-brasil (25)
- # clojure-dev (16)
- # clojure-japan (8)
- # clojure-nl (1)
- # clojure-russia (110)
- # clojure-uk (7)
- # clojurescript (168)
- # clojurewerkz (1)
- # cursive (10)
- # datomic (45)
- # devcards (50)
- # emacs (5)
- # hoplon (6)
- # instaparse (6)
- # ldnclj (73)
- # lein-figwheel (4)
- # leiningen (6)
- # liberator (7)
- # luminus (2)
- # off-topic (19)
- # om (80)
- # onyx (2)
- # re-frame (11)
- # testing (12)
@alexmiller: would there be any interest in a patch to fix trailing whitespace in clojure.test?
oops, too late
No worries
It could be helpful for me (and others) to have some written documentation on JIRA outlining Core’s attitude towards contributions, and what types of patches are encouraged or discouraged.
I’m not asking for a change in the process, just clarity into the thought process
There is actually a page with this intent on the wiki but I don't think it's very up to date
I couldn’t see anything under the “Contributing section”. There’s http://dev.clojure.org/display/community/Contributing+FAQ but it doesn’t give any info on what kinds of contributions are wanted
I was thinking of http://dev.clojure.org/display/design/Why+Feature+X+Was+Declined
Which is admittedly pretty buried
That’s a good start, but it would be helpful to give some concrete examples
might be worth adding “yes, we know the clojure codebase is badly formatted and hard to read; this will never change; deal with it” to the document, maybe people would stop asking
it might change. just not through a patch.