This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (48)
- # alda (1)
- # aws (24)
- # beginners (4)
- # boot (103)
- # cider (69)
- # clojure (111)
- # clojure-art (5)
- # clojure-dev (35)
- # clojure-greece (2)
- # clojure-nl (3)
- # clojure-russia (1)
- # clojure-shanghai (1)
- # clojurescript (220)
- # clojurescript-ios (1)
- # clojurewerkz (3)
- # community-development (3)
- # core-logic (5)
- # cursive (5)
- # datomic (24)
- # devcards (21)
- # editors (3)
- # funcool (1)
- # hoplon (20)
- # ldnclj (47)
- # ldnproclodo (1)
- # liberator (1)
- # off-topic (7)
- # om (21)
- # onyx (36)
- # reagent (1)
- # ring-swagger (2)
- # spacemacs (38)
- # yada (17)
really interesting idea a "Cjojure" solution would also increase visibility even more
@gjnoonan: @chris: The #C08P6MXC7 group are already building a simple event management system but we are not very far into it. Perhaps we should redirect our energies to a Slack replacement instead?
@agile_geek: @gjnoonan @chris - I have clearly missed something… Is the Slack account / channel for Clojure under threat in some way..?
@agile_geek sounds good, I think further discussion is needed! An Event management system is something that could be on the clojurians site also 😉
I've created a #C0CB40N8K channel if anyone wants to join and discuss how we could develop a new site, and applications for our community.
@agile_geek: Ah I see, sorry - probably could have figured that out for myself (facepalm)… Still it could be a worry in the long term, so thinking about planning for an alternative makes sense.
@gjnoonan: that’s why we started with that. Although the group is currently London based I’m trying to figure out a sensible way to run it remotely too…with an element of OSS project to it but it is ultimately a user group/dojo so don’t want to lose the community feel and inclusiveness.
P.S. want it remote cos that way I can still join in when up in Newcastle! selfish
Sounds good I want to create a Northern Clojurians to rival #C0522EZ9N .. but that is another topic
..but we will then have that awkward discussion about when the midlands stop and the north starts!
The North starts at the Staffordshire / Cheshire border, Midlands to the South, The North to the North 😉
I am on the border of North and east yorkshire, so maybe I could say North East too @agile_geek ? haha
@agile_geek: I mean, right now I’m in The Philippines, so I don’t really have a leg to stand on, but it’s the Red Rose of Lancashire that’s tatooed on my soul
Not sure why I’m arguing about the North…as someone from a Welsh family, born in London, who grew up in East Anglia and has lived in NE for 30 years…who knows where my allegiances are!?
@agile_geek: I know what you mean, Lancashire may be the home of my soul, but until my wife and I put our stuff in storage and moved our little family to The Philippines I had been living in the SE for 12 years!
@rbf I am not sure it’s as clear cut as them not wanting to support, the comments make it sound like they have limited resources and are focusing them on paying customers…which you might expect. Not sure if that may change in future but you’re right, it’s a shame.
Here as in IRC, as traffic increases, it gets harder to track overlapping conversations. I'd like to see threads in the interface.
I’d like to use Zulip just to try how threading works out, definitely agree that threading is an option for chat apps that hasn’t been explored enough
I once wrote down some ideas for a chat app with threading as first class mechanism but never really had the time to make it into something usable: http://www.martinklepsch.org/chaf.html — feedback/thoughts welcome
yeah I’ve heard about that, some people stated that they sticked to flowdock vs slack because of that.
Slack also stated that they are working on adding threading. That said it can also clutter an interface I guess.
Yeah, I like it definitively better for (small) company use but wouldn't work for large communities
Message tagging is also very useful feature, it works like a company wide link list for us
I guess it would be hard to get Conclusions. Who would have the "authority" to say, this is the last word on the subject?
@bensu: I imagined conclusions to be wiki-like assuming no bad-intending actors. tbh I think there are many rough edges that need to be worked out by actual usage.
Oh, I misunderstood Conclusions. It's not that somebody comments and declares it a conclusion. Is that somebody decides "we can wrap up", and then people can chime in