This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-07-20
Channels
- # admin-announcements (15)
- # announcements (1)
- # beginners (10)
- # boot (39)
- # bristol-clojurians (2)
- # clojure (146)
- # clojure-canada (1)
- # clojure-gamedev (8)
- # clojure-italy (2)
- # clojure-japan (16)
- # clojure-korea (1)
- # clojure-poland (1)
- # clojure-russia (20)
- # clojure-spain (3)
- # clojurebridge (5)
- # clojurescript (104)
- # core-typed (2)
- # datomic (80)
- # indycljs (1)
- # jobs (1)
- # ldnclj (31)
- # off-topic (15)
- # om (21)
- # onyx (7)
- # ox (9)
- # re-frame (2)
- # reagent (16)
The critical issue seems to be that the broader community does not and will never have a voice in the governance and direction of Clojure. To this there is no solution but exit, the question is one if if how and why.
Just talked with @mikethompson and he said that theres a few key things in a fork: 1. Provide compelling features for people to switch 2. Frame it in a positive way
The first month or so is critical for adoption
Agreed... one question I've been struggling with is what's the governance goal so that we don't wind up back in the same place.
governance goal?
What does the maintainership structure look like. How do we grow it. Presumably we don't want to limit it to the two of us.
There’s plenty of examples of good governance around