This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-06
Channels
- # announcements (18)
- # asami (3)
- # aws (10)
- # babashka (47)
- # beginners (343)
- # calva (36)
- # cider (4)
- # clojure (66)
- # clojure-europe (9)
- # clojure-nl (3)
- # clojure-uk (23)
- # clojurescript (30)
- # community-development (69)
- # conjure (1)
- # eastwood (9)
- # events (7)
- # fulcro (81)
- # graalvm (1)
- # malli (5)
- # meander (1)
- # off-topic (41)
- # pathom (15)
- # rdf (1)
- # reitit (6)
- # sci (57)
- # shadow-cljs (18)
- # spacemacs (4)
- # startup-in-a-month (1)
- # testing (2)
- # vim (1)
Good question. I suspect someone has documented the commands to invite bots for logging via clojurians-log, and for Clojurians ZulipChat (two different bots), but it would be nice to have a page documenting those things, and links to the logs, and even maybe some brief instructions on how to search those logs.
I can create my own personal Github file documenting those things and link to them, but maybe there is a better "home" for that info.
yeah maybe above the fold on the readme of the clojurians-log app on github would be nice
Does anyone know if the bot logbot
(for clojurians-log) or zulip-mirror-bot
should show up in the list of members of a Slack channel after they have been invited? I've searched the list of members of a few Slack channels for those names, and not found them, so perhaps there is something special about them that they do not show up in those member lists?
And I guess /invite <name>
messages are always only visible to the sender, and shouldn't clutter up the view of other (human) channel members?
Answering my previous question: if the bot was not already invited, everyone sees a message that the bot was added to the channel. If the bot was already on the channel, no one sees a message except the person who attempted the invite, who sees a message that the bot is already a member of the channel. Nice going, Slack, for not cluttering up everyone's messages with repeated attempts to invite the same bot.
Feel free to comment, correct, or ask questions about this article, which if polished up maybe slightly more, I could try to find a better "home" for: https://github.com/jafingerhut/jafingerhut.github.com/blob/master/clojure/clojurians-slack-archive-notes.md
@andy.fingerhut Typing @log
in this channel offers @logbot as a completion and the same goes for typing @zul
offering @zulip-mirror-bot -- @pez if you invite @logbot to a channel, can you also invite @zulip-mirror-bot please?
Sean, are you asking whether doing an invite for @logbot
in a Slack channel can automatically also invite @zulip-mirror-bot
? If that is possible, cool. I wasn't expecting that it would be.
No, I'm asking people who invite logbot in to also invite zulip-mirror-bot in so messages are available in both places.
I just updated the README at https://github.com/clojurians/community-development (which is linked in the channel topic and also in the description here) so that it documents the logging bots.
Sean, if you think any of that article would be useful to add to the community-development Github repo you just linked to, let me know, and/or feel free to copy any of it you want. That repo seems like a good home for that content.
Feel free to send a PR!
@andy.fingerhut I don't know where you got the $1,200 figure from? According to the Slack Admin page, upgrading to their minimum paid plan would cost: "$8 USD x 952 members x 1 month = $7,616 USD" and they're currently offering a 50% discount for three months.
Screen cap of Slack upgrade page:
I've updated my article with that snapshot of price estimate. Thanks. $1,200 was from some incorrect memory of a discussion 1 or 2 months ago, but even though I remember the number mentioned there incorrectly, it was also calculated incorrectly then, too. Two wrongs did not make a right this time 🙂
Does anyone recall when http://clojurians.slack.com was created, out of curiosity?
and/or when you recall it becoming more popular than #clojure on IRC freenode?
I see clojurians-log #clojure channel log goes back to mid 2015
#admin-announcements was Created on March 1, 2015 which was the original "general" channel that Slack creates.
I don't know how many folks are on freenode IRC but Slack hit several hundred members very quickly...
we've been asking the question about forums on the state of clojure for several years and that's possibly useful to compare and track
Thanks, you two. I will quickly check several past state of Clojure survey results to see what the trends were.
Nope. It wasn't created until March 2015. See my comment above.
#clojure and #admin-announcements were created March 1, 2015.
Gavin-John Noonan set it all up (on March 1st, 2015) and it ballooned pretty quickly 🙂
I could be mixing this up with hanging out in the reagent (or clojurescript) channel somewhere, a lot, around that time. Could have been IRC then.
You joined Slack very early @borkdude:
gjnoonan,"Primary Owner",0,0,0,U03RZGPFT,"Gavin-John Noonan",gjnoonan,
arathunku,Member,0,0,0,U04V0EV9N,arathunku,arathunku,
jasebell,Member,0,0,0,U04V0TT98,jasebell,,
davy,,Member,0,0,0,U04V0UNM2,"Davy Duperron",davy,
kjw,Member,0,0,0,U04V12X4C,kjw,,
borkdude,Member,1,0,0,U04V15CAJ,"Michiel Borkent",borkdude,
I think that's in date-joined order.Active vs inactive I think.
I omitted the email addresses. I figured everything else was public data.
Yup! Congratulations!
But members go inactive and then become active again.
I think you should have a number over 1 in that column 🙂
There are only a handful of still-active users amongst those early joiners: Nate Smith, Delaguardo, Ray McDermott, Erik (slipset), Gert (eval2020), and me (51st person to join).
Looking back at the state of Clojure survey results, the first year that ecosystem involvement question was asked was 2016, probably late in the year since the article I see publishing the results are dated Jan 2017. By that time, Clojurians Slack was already the highest fraction of responders (responders were asked to list all they were involved in, not only one) at almost 60%, and it has always been near that percentage since then. The Google groups have taken the biggest dive since then (about 50% in 2016 down to 17% in the last survey), and IRC went from 16% down to about 4%)
I can publish an Excel sheet soon, in case anyone wants to see all of the others.
OK, chart is added to my article now, at the end: https://github.com/jafingerhut/jafingerhut.github.com/blob/master/clojure/clojurians-slack-archive-notes.md
Could you link to the official community repo for this Slack? https://github.com/clojurians/community-development Just for completeness.
(accidentally replied to myself instead of you, earlier) If you don't mind waiting a day or two for Gert Goet to review the article and suggest any changes he thinks of, I don't mind submitting a PR to that repo to add this article to it.
Skimming over what is there now, I think I had heard, but forgotten because it has been quite some time, the term "Slackpocalypse". I guess Slack didn't do many repeats of the kicking large OSS communities off their free service.
Yeah, we kept anticipating being kicked off as we approached 8k, then 9k, then 10k... and nothing happened... and now we're at 20k... but perhaps it's all about the number of active uses in which case we're still only at 1k and I suspect Slack doesn't care about that 🙂
But I would certainly be completely happy if everyone decamped from here and landed at Zulip...
I submitted a PR to your repos @andy.fingerhut . Happy to discuss it further via DM/PR if needed.
Hmm, I do not see any PRs on this repo, if that is the one you mean: https://github.com/jafingerhut/jafingerhut.github.com
I see it now. Thanks for adding the extra how-to on searching Zulip. I will try out the instructions to ensure they work for me, too. Will let you know if I have any questions.
@U04V70XH6 Gert made some nice additions on searching Zulip messages, and I massaged it a little bit more wording-wise on his text and mine, and created a PR to add it to https://github.com/clojurians/community-development
Thank you, @andy.fingerhut! Taking a look now...
Merged. Updated the readme to link to it prominently!
Cool. Sent a link to #news-and-articles so hopefully a few more people become aware of where to find this.
(it has a bunch of docs that reflect some of the earlier discussions that were had about this whole topic, as well as the README and the Code of Conduct)