Fork me on GitHub
#community-development
<
2016-09-16
>
keatondunsford02:09:30

I feel like something is better than nothing considering the size of the Clojure community is growing exponentially.

seancorfield03:09:57

I’ve posted the link several times. It’s terrible from an admin point of view however.

keatondunsford03:09:11

Huh weird. When I’ve been searching via Gitter nothing has been coming up for me.

seancorfield03:09:28

There’s clojure/general, clojure/clojure, clojure/java.jdbc, clojure/tools.cli

keatondunsford03:09:29

That’s why I commented about it, but hell yeah I’ll join these now.

seancorfield03:09:43

(I created the last two based on the GH repos since I maintain those)

seancorfield03:09:05

The CIDER folks and Onyx folks have fairly active communities around their projects there

keatondunsford03:09:53

Awesome! Thanks!

seancorfield03:09:34

Regarding the growth of this Slack — it has actually slowed down a bit lately.

keatondunsford03:09:32

Yeah Gitter sucks.

keatondunsford03:09:05

What about Mattermost? To self-host it some of us could chip in.

keatondunsford04:09:52

Nevermind, it also sucks

kauko05:09:57

Has anyone used telegram? It has groups (200 members), supergroups (5k members) and "channels", which apparently aren't places where you discuss with your own name, rather you make announcements "as the channel". If a group/supergroup is similar to Slack's channels (like #community-development ), they could work for us - but if they're like Slack's teams (Clojurians), then they won't

richiardiandrea05:09:37

I have to say I was surprised that nobody talked about Telegram here, the problem about history is still there though (and no search whatsoever)

richiardiandrea05:09:09

The rest is pretty much akin to Slack (at least the features I am using)

kauko05:09:48

Those would be nice, true, but hardly a priority IMO. Accessibility is priority #1, and then price (free as in free beer).

kauko05:09:04

accessibility is the reason irc doesn't really work, there's a bunch of people who use it (me included), but a growing number of people can't be bothered with it. It even has full history and search if you know how to grep your .irc_history 😉

richiardiandrea05:09:06

From what I gathered, but i might be wrong, the history search is a priority as Slack is basically free if you don't want to use...I think. Braid chat was a thing and probably it still is, but I don't have more info on it.

hans05:09:17

I think an alternative platform will be used as soon as enough people are bothered with problems in Slack and don't want to continue using it. What are the problems with Slack, though? Limited number of users has been quoted primarily, and the issue with that is that is that it only bothers people who want to join the community, not the community itself. Is this a real problem, though? Are a lot of people denied access to the Clojure Slack because it is full?

hans05:09:14

Or are there other problems with Slack that I'm not aware of?

kauko05:09:44

The Scala team on Slack was shut down by Slack because it grew too big

hans05:09:24

Once that happens, a new platform needs to be chosen, that I understand. How big was the Scala Slack when it was shut down? Was it shut down without notice? Can people who try to go to the Scala Slack find the new home easily?

hans05:09:49

Well, I think I understand the purpose of this channel now. It is good to see people care for the future in which Clojure is really big 🙂

kauko05:09:54

I tried looking for info on the scala slack thing, but couldn't find anything. Maybe I'm mistaken?

seancorfield05:09:11

@kauko: do you have links to that information about the Scala community and Slack? Hah... Yeah I couldn't either.

kauko05:09:48

I remember there was a github repo discussing the future of this community - things like alternative chats etc., and there was a mention of it

kauko05:09:06

slackapocalypse, scalapocalypse, it was called something epic like that

seancorfield05:09:58

It's linked in the channel topic.

kauko05:09:31

oh right, that's it

kauko05:09:41

it was reactflux, not scala 🙂

seancorfield05:09:28

Looking at their post about it, they moved to Discord (the gaming server network). It didn't have search and channel management / discovery seems to be poor.

seancorfield05:09:13

I'm pretty sure someone set up a Clojure server on Discord for folks to try. Let me see if I can find it...

seancorfield06:09:55

Ah it was just a #clojure channel on the main http://matrix.org server. I tried it for a bit. I thought it was horrible but maybe that's just me.

seancorfield06:09:17

Some more digging turned up a number of channels on http://discordapp.com

dominicm11:09:38

I'm going to leave my usual link here: http://whatthefuck.computer/blog/2015/11/01/on-the-balkinization-of-my-chat-communities/ and mention my vote for http://matrix.org, as it seems like what we really want (IRC for the modern age)

dominicm11:09:23

@seancorfield what issues did you have with matrix?

seancorfield15:09:12

I don't remember the specifics of why folks didn't like http://matrix.org as a replacement for Slack. I wasn't driving this rodeo so I assumed others were writing down the objections being raised.

seancorfield15:09:59

The problem here is inertia. Folks like Slack so there's no real effort put into trial runs on other platforms. It's why the question keeps coming up but nothing gets done about it.

seancorfield15:09:08

The folks who like various platforms tend to just drop a link in here, say it's "the solution" but never put in the effort to encourage a decent trial including admin / moderation functionality.

seancorfield15:09:48

I don't know why I even bother getting involved with discussions here, except out of a sense of trying to help folks address the "Slackopalypse" worries they have.

seancorfield15:09:42

All that usually happens is I get drilled about why I don't like a particular solution being offered. Like my opinion matters? I'm not driving this!

fellshard15:09:17

(This occurs for any giving communications-oriented platform; it's the same thing that keeps people trapped in Skype, even though as a communications app it fails utterly in terms of reliability)

seancorfield15:09:27

So, yeah, @dominicm I'm pretty annoyed at your response because we've been round this several times.

sveri15:09:15

Yea, it sounds like @seancorfield is keeping people from switching to matrix which could not be farther from the truth

seancorfield15:09:57

I'm going to try to ignore this question in future so I don't keep getting dragged into the endless (and rather pointless) back and forth on which platform we should move to.

dominicm15:09:00

I didn't mean to imply that sean was blocking any kind of switch

dominicm15:09:57

@seancorfield I didn't remember a specific problem you had with Matrix. I would have asked anyone who'd said they found Matrix horrible. Sorry if I've asked before, my memory isn't the greatest.

seancorfield15:09:49

If you care about Matrix and think it's a good solution then set it up properly in terms of channel management, moderation, discoverability etc -- all the things that make Slack work -- put in some effort, rather than just dropping in a link to it. And document people's reactions.

seancorfield15:09:04

Otherwise you're being part of the problem.

seancorfield15:09:04

I'm tired of hearing drive-by comments about "We should switch to XYZ because it's great" without folks doing a proper follow up.

dominicm15:09:47

@seancorfield Ah, I've never considered trying to set up Matrix as a working replacement for Slack, until the slackocalypse seemed imminent. I understand your annoyance with my comment now. I didn't mean to drill you, it's a genuine interest (that never ends because my memory really is that poor)

seancorfield16:09:22

The platform needs to be slick, fast, free to users, have good quality apps for desktop, iPhone, and Android at least, be commercially supported, have good discoverability of channels, have solid admin / moderator features in terms of user permissions and integrations. Probably other features are key too. Like I say, I'm not driving this, just trying to list what folks said they needed back in... January? Whenever the HackPad was written and most of the trails occurred.

dominicm16:09:15

@seancorfield I previously thought the Clojurians moderation team wanted to take on moderation role, and were using this channel to gauge community interest in various platforms.

seancorfield16:09:11

We (the admins) have never been the ones driving Slackopalypse. That was all started by a few vocal community members. Most of whom have left the community by the way.

seancorfield16:09:00

We created this channel mostly as a place for those passionate few to duke it out about platforms. They were clogging up the technical channels.

seancorfield16:09:44

They fought about platforms for a while. Mostly rejected everything they collectively came up with. Then they gradually went quiet / went away.

seancorfield16:09:38

About once a month someone asks "what happens if we get kicked off Slack" and I direct them here to "rally the troops" simple_smile

plexus16:09:23

Thanks a lot for doing that @seancorfield! I was aware of the potential danger of being kicked off Slack, and would like to help find an alternative, but so far I had completely missed all the past discussion.

seancorfield16:09:57

Unfortunately having a 10,000 message cap on history means old discussions are lost (and therefore repeated, sometimes over and over and over).

seancorfield16:09:31

Another feature to add to the list above: unlimited, searchable message history.

seancorfield16:09:35

(Although that would be a bonus new feature -- it's certainly a desirable one)

akiva21:09:10

I’m still here!

akiva21:09:23

But I kind of don’t care. I’m curious and interested, to be certain, but I literally have no dog in the race.

akiva21:09:25

Something IRC-based would be fine for me, I’m a veteran of the EFNet split wars of the late 90s. And it’d be nice to be able to just pipe it into Spacemacs. But really. [shrug]

fellshard21:09:42

What is it that makes IRC a less viable option these days? Lack of archives? Not as discoverable? Not as likely for folks to have good clients?

sveri21:09:52

@fellshard Even my fellow colleagues look surprised at me when I tell them that I still use IRC today. And some of them only remember the offensive language they encountered.

fellshard21:09:58

I understand the desirability of Slack for an enterprise setting, where many users will not be comfortable with using IRC. But for a software community...

fellshard21:09:31

Especially one such as this, with a focus on simplicity 😉

sveri21:09:37

That was my thinking too, but, like I said, none of my real life programmer friends use IRC, not a single one

fellshard21:09:04

It's a rarity, yeah. But maybe all that is needed is the right reasons, the right publicity. To make it discoverable again.

fellshard21:09:38

Which is why I'm wondering why it's lost its edge, and if it were to be introduced, which vectors would be the most effective for propagation.

sveri21:09:57

well, of course it has to have a fancy web ui

sveri21:09:59

like slack

sveri21:09:08

and integration in the major phone markets

fellshard21:09:37

Hmm, good call. Wonder how friendly IRC is for mobile use.

akiva21:09:47

I think it falls hard on the UI. I mean, really, Slack is just IRC v2 with pretty bits in.

fellshard21:09:16

Yep. It even borrows from the sigils of IRC (@, #, /)

akiva21:09:28

Incorrectly, even!

fellshard21:09:03

With curated channels and less distributed administration.

akiva21:09:36

The only thing I’d really miss from Slack is the code formatting.

fellshard21:09:44

To developers focused on community, though, I think we'd put up with a fair amount of bare-bones UX if the community was seen as more important

akiva21:09:05

Honestly, the best thing we could do is write our own in Clojure.

fellshard21:09:48

There was an effort to make something like that iirc

akiva21:09:57

People have talked it up a bit, yeah.

fellshard21:09:58

Found it lying around abandoned from a year or so back

akiva21:09:14

No one’s going to care until we’ve gone past our expiration date, really.

fellshard21:09:49

And by that time the community's fragmented, too late to make a coordinated shift

fellshard21:09:54

Hence the attempt to forestall here :T

fellshard21:09:03

But yeah, I agree.

fellshard21:09:10

What should happen vs. what will

fellshard21:09:29

I mean good grief, Skype is a sinking ship and people will cling to it 'til it sinks

akiva21:09:35

And Sean’s right; we’re already fragmented. One of the admins has totally disappeared, etc.

fellshard21:09:44

Fragment further, though

fellshard21:09:56

A few of the channels for major libraries have been pretty key

akiva21:09:14

This is where Twitter should be going, honestly. A Twitter version of Slack? Hello.

fellshard21:09:34

Char limit / microblogging is not a proper conversation framework

fellshard21:09:41

Two different goals

akiva21:09:54

Nah, that’s not what I mean. I

akiva21:09:12

er I mean literally Twitter’s framework with Slack’s UI and capabilities.

akiva21:09:32

I get a ton of interaction about of Clojure on Twitter even at 140 characters.

akiva21:09:40

Seriously, I swear, I know English.

seancorfield21:09:17

IRC is unmoderated and has no way to make it a safe space for a community. It’s also a flat collection of (unrelated) channels — unless you run your own server, just for Clojurians.

seancorfield21:09:55

Mozilla run their own server for Rust folks (or did?) and it was always being targeted by trolls and spammers. IRC is pretty much impossible to admin / moderate from a community p.o.v.

fellshard21:09:06

Alright, gotcha.

akiva21:09:12

I agree. IRC requires 24/7 babysitting.

fellshard21:09:29

So the administrative concerns are high.

akiva21:09:35

That’s what I meant when I typed about the EFNet split wars. It was a constant battle just to even keep your channel.

seancorfield21:09:02

I used IRC heavily for decades...

fellshard21:09:06

Never been deeply involved, so not aware of the frustrations and pitfalls

akiva21:09:31

Yeah. There’d be a split and suddenly you’d lose all of your ops and someone else would take over.

seancorfield21:09:36

…in fact I was still using it heavily up until early last year when I finally gave up, as communities were moving to Slack.

fellshard21:09:06

"Time to re-reinvent community communications."

akiva21:09:19

I’d be totally down with Slack injecting ads or whatever they need to do. The fact that they’re just shutting FOSS communities down… I dunno.

fellshard21:09:22

I mean we could go back to mailing lists :V

akiva21:09:30

Seems a bit wrong-headed but they’ve got to make money so I get that too.

fellshard21:09:36

Just like OpenJDK's 😉

akiva21:09:11

Actually, I’d like to see GitHub to step up.

akiva21:09:34

Maybe they are. The recent updates are pretty compelling.

fellshard21:09:44

I wonder if it would help if the community itself had to cover its own costs, e.g. $1 a person per period

seancorfield21:09:53

Mailing lists have their place too — for async communication. I like mailing lists and use them heavily too. I do not like "web forums" where you have to go to a web site and navigate around to take part.

akiva21:09:54

It’s absurdly expensive.

fellshard21:09:56

Design a new system that lets us operate at a low cost

fellshard22:09:09

Not Slack, just thinking system constraints

seancorfield22:09:13

@fellshard You know that Slack’s pricing is about $7/person/month right?

fellshard22:09:26

Something individual FOSS communities could set up on their own ad hoc

seancorfield22:09:44

Gitter supports that around — for projects on GitHub.

fellshard22:09:52

Yeah, but that's single channel isn't it?

fellshard22:09:05

And it's for projects, yeah, not communities

shaun-mahood22:09:06

If anyone is thinking about rewriting in Clojure, it's worth listening to http://softwareengineeringdaily.com/2016/09/12/slacks-architecture-with-keith-adams/ - a lot goes into slack that didn't cross my mind at all the last time my hubris got a hold of me and I thought about rewriting it 🙂

akiva22:09:20

I thought that Gitter was just IRC.

fellshard22:09:21

Nice, I'll check that out

seancorfield22:09:23

I’m guessing you haven’t checked out the Clojure Gitter setup I posted a link to earlier / yesterday? @fellshard

fellshard22:09:31

And I don't doubt it's crazy difficult.

fellshard22:09:42

I've seen other Gitters before, but it's been a while. I'll check it again

seancorfield22:09:23

@akiva No, although Gitter does have IRC protocol support directly, as I recall?

fellshard22:09:33

Okay, rooms present.

fellshard22:09:05

If there was a community I'd expect could pull it off though... this is one of the few 😉

seancorfield22:09:38

https://gitter.im/clojure/general — if folks want to try it (also clojure/clojure and clojure/java.jdbc etc), but it’s pretty horrible from a community admin perspective

akiva22:09:51

We are quite awesome, aren’t we?

seancorfield22:09:24

And this community has tried to design and build its own chat service… which got as far as a talk at Clojure/West I believe…?

akiva22:09:04

Basically, someone just has to do it and then everyone else will glom on, I imagine.

seancorfield22:09:14

(although I believe that talk never actually happened in the end)

fellshard22:09:16

Saw that. It would probably take a bit more to compel folks to pursue that all the way to a viable product; maybe all it'll take is time, pressure, or passion.

seancorfield22:09:54

Meanwhile we’re all just waiting for those folks to volunteer and build it 🙂

fellshard22:09:16

"Trapped inside this Octavarium"

seancorfield22:09:31

…and then some company has to pay for the hosting / infrastructure / ops side of it.

fellshard22:09:12

Would it be possible to adapt IRC as it exists now to give the community management tools needed?

fellshard22:09:32

Some sort of wrapper around an IRC server, an additive modification to the protocols?

seancorfield22:09:33

Seriously tho', we’ve been all over this discussion several times — including the idea of building on top of IRC…

fellshard22:09:39

Heheh I'm sure

seancorfield22:09:00

…it never goes anywhere because the folks who make the suggestions tend not to be the folks who can / will actually build all of this.

akiva22:09:52

I’d like to do it but I’ve just launched an offline IMAP->maildir thing.

fellshard22:09:06

> Running forward > Falling back > Spinning round and round > Looking outward > Reaching in > Scream without a sound > > Leaning over > Crawling up > Stumbling all around > Losing my place > Only to find I've come full circle

fellshard22:09:19

But yeah. Almost need a more structure / concerted effort. Folks who can take the lead for product vision, set design goals etc.

seancorfield22:09:36

That was what #braid-chat was supposed to be...

akiva22:09:46

Forgot all about that.

fellshard22:09:58

It would be a shame to see the community go, give it's one of the best resources for Clojure out there...

seancorfield22:09:09

@fellshard If Slack restrict us, the most likely approach would just be cutting off new invites — so we’d remain, say, 7,500 strong… so it would stay a great community for those already here but it couldn’t grow any more.

seancorfield22:09:44

So then it would be a matter of a new, unlimited community needing to grow organically somewhere else to overtake it.

akiva22:09:21

I still lean on Twitter for that. I often see things on Twitter before they percolate up here.

akiva22:09:29

New version announcements, etc.

akiva22:09:22

And quite a bit of Clojure hate but, y’know, it ain’t Twitter if someone isn’t being mean about something.

sveri22:09:29

btw. the clojure community consists of more resources than slack: http://clojure.org/community/resources

akiva22:09:41

Good point.

fellshard22:09:59

Yep, this is just one particularly strong resource.

sveri22:09:18

Well, before slack I also got all my questions answered

seancorfield22:09:30

FWIW, there are (currently) 630 folks on the #clojure IRC channel (on freenode).

fellshard22:09:03

Here, I can look and see new libraries and discussions about them immediately. It's a really neat way to discover new resources on the fly.

seancorfield22:09:13

(and 7,349 here — although not all of those are "active" user accounts)

fellshard22:09:15

It's one subtle benefit

fellshard22:09:55

It's one of the upsides to Twitter and Slack - conversations are preserved when offline

akiva22:09:43

I’d say there are probably less than 500 active accounts. And I’m being generous here.

akiva22:09:38

Even Gavin’s rarely about now. No one knows where PK O’Brien is.

akiva22:09:20

Pretty sure I spelled ol’ boy’s last name incorrectly. Heh.

sveri22:09:46

I think he was investing his time in braid chat

sveri22:09:37

Although braid-chat was never intended for these masses of users, IIRC

seancorfield22:09:03

@akiva there are 1,347 users active for billing purposes on this Slack (as one of the admins, I have access to that data)

seancorfield22:09:14

And to give you an idea of volume, nearly 12,000 messages were posted in the last seven days (which is why the free 10,000 limit gets us so hard).

shaun-mahood22:09:43

@seancorfield: Do you know if there's any official position from slack on our archiving of the chat data? I've heard it's not really allowed, but if it's fine with the slack rules I'd like to put some effort into improving that experience - there are a bunch of concerns I'm sure I haven't thought about (such as privacy, ability to delete, etc.) but those aren't being handled that well now anyway.

seancorfield22:09:30

I’d say "Go read their Terms of Service" and see what it says.

fellshard22:09:50

In summary: no

fellshard22:09:14

Given that's one of the keystones of their monetization

fellshard22:09:31

It would be pretty silly of them to allow archival, even if it is self-hosted

shaun-mahood22:09:51

Yeah, that's kind of what I got from others (and my extremely inexpert reading of the ToS). Hoping I was wrong though.

akiva23:09:55

There’s still an active bot logging everything, though, isn’t there?

seancorfield23:09:59

It only logs in channels to which it’s been invited (but, yeah, def. a grey area).

akiva23:09:19

[zips lips, mimes throwing away key]