Fork me on GitHub
#community-development
<
2017-08-26
>
seancorfield01:08:18

BTW, @lepistane Your Reddit post links to dev-ua/clojure for Gitter but https://gitter.im/clojure/general this is probably more applicable for the community as a whole?

seancorfield01:08:14

There are also rooms for clojure/java.jdbc and clojure/tools.cli (mostly because I maintain those and created those rooms), plus clojure-emacs/cider is pretty active on Gitter.

seancorfield01:08:31

As is onyx-platform/onyx BTW.

lepistane14:08:50

i think it's safe to assume that

lepistane14:08:57

voting didnt go so well XD

lepistane14:08:27

850+ views 237 votes

lepistane14:08:15

so only 8.5% of people saw that and only 2.5% actually voted

lepistane14:08:27

not to mention topic on reddit is heavily downvoted

lepistane14:08:54

right i will change it

lepistane14:08:25

anyway i will do what i preach try to help community on multiple platforms and encourage people to use SO and use it

seancorfield18:08:31

Every platform has its pros and cons, and its supporters and detractors. Communities grow organically and they take root where others are willing to nurture them. No one could have predicted this Slack would attract 11,000 Clojure developers but here we are. For comparison, the CFML (ColdFusion) community has been declining steadily for almost ten years but around the time this Slack started, I created a CFML Slack, told a few people about it, and hung out to help anyone who joined. It now has 3,000 members making it just about the largest gathering of CFML developers there has ever been on a single platform. And the interesting thing is that a lot of folks who've stopped doing CFML have stayed in that Slack to help those who still make their living that way. Prior to that Slack, most CFML mailing lists had dwindled to a few hundred members and IRC had just two channels with about 20-30 people. Logic and reason (and votes) don't drive communities. Some great ideas, proposed by strong advocates, just don't take root -- no matter how sensible, obvious, and beneficial they are.

lepistane14:08:05

and if something goes wrong with slack - other places will be active enough so they can choose where to go

lepistane14:08:11

anyway thank you for help and feedback

seancorfield18:08:31

Every platform has its pros and cons, and its supporters and detractors. Communities grow organically and they take root where others are willing to nurture them. No one could have predicted this Slack would attract 11,000 Clojure developers but here we are. For comparison, the CFML (ColdFusion) community has been declining steadily for almost ten years but around the time this Slack started, I created a CFML Slack, told a few people about it, and hung out to help anyone who joined. It now has 3,000 members making it just about the largest gathering of CFML developers there has ever been on a single platform. And the interesting thing is that a lot of folks who've stopped doing CFML have stayed in that Slack to help those who still make their living that way. Prior to that Slack, most CFML mailing lists had dwindled to a few hundred members and IRC had just two channels with about 20-30 people. Logic and reason (and votes) don't drive communities. Some great ideas, proposed by strong advocates, just don't take root -- no matter how sensible, obvious, and beneficial they are.

seancorfield18:08:55

I'd point to the long trail of documentation efforts in the Clojure community as an example of that last part. So many great ideas have produced docs sites that quickly go out of date or go offline because, for whatever reasons, the community just doesn't rally round and support them.

seancorfield18:08:11

http://ClojureSphere.com and http://ClojureAtlas.com are the first two that came to mind (both gone -- although an old version of the latter lives on as a subdomain of Chas's site).

seancorfield18:08:29

http://Clojure-Doc.org survives but gets very little community contribution. I moved the Java.jdbc docs there because folks complained the CA was blocking contributions while the docs were in the Contrib repo -- guess what? I'm still pretty much the only person who works on those docs (although I've had some great contributions from a new community member just recently).