This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (102)
- # boot (5)
- # cider (1)
- # cljs-dev (15)
- # cljsjs (1)
- # cljsrn (20)
- # clojure (104)
- # clojure-austin (1)
- # clojure-europe (8)
- # clojure-italy (39)
- # clojure-nl (17)
- # clojure-spec (38)
- # clojure-uk (23)
- # clojurescript (33)
- # cursive (31)
- # data-science (5)
- # datomic (3)
- # emacs (28)
- # joker (1)
- # kaocha (5)
- # klipse (1)
- # leiningen (1)
- # off-topic (66)
- # quil (4)
- # reagent (35)
- # ring-swagger (1)
- # rum (1)
- # shadow-cljs (121)
- # test-check (1)
- # tools-deps (33)
- # uncomplicate (2)
- # vim (15)
- # yada (1)
When publicly posting a request for code review for a library I'm working on, which is better: a brief message of "this is what I'm working on, take a look and let me know your thoughts" or a small-novel-sized post of my current thoughts and questions on this project? I'm having trouble getting into clear specific questions without it getting extremely long and I'm thinking about just putting it out there without much comment.
@jjttjj In a project I work on, I put a mix of that into a README and then a Github project that has the current ideas of the roadmap.
but now you've also captured it in an actionable way even for yourself, by opening issues/labeling them (`help-wanted` and
good-first-issue are great labels to have)
then when you post it, just mention that all of those important things in your brain are here, there, and over yonder in the repo.
you can put projects on the repo too, we use an org-level project only because we have multiple repos that are all interrelated and need to be reference-able once we convert them into issues.
@jjttjj Also, there's a #code-reviews channel here that is a good place to have some of the "thoughts and questions" discussions around code under review.
Seems that history on https://clojurians-log.clojureverse.org/ is minimal & only goes to 2016 -- anyone know the story of why it was cut (and if there's a replacement?)
Hmm. Looks like the project is a little stalled. Unfortunate -- due to Clojure's smaller set of learning resources, the Slack logs have been invaluable to me over the years. If @plexus is still around and/or has interest, I'd be willing to chip into a montly Patreon or something similar to get it up & running again
https://ask.clojure.org to ask questions in a permanently searchable manner fyi...
The slack-archive at Clojurians-Zulip exists since Feb and can be found here: https://clojurians.zulipchat.com/#narrow/stream/180378-slack-archive
I'm glad there is ask.clojure now, but it is pretty tragic that the slack logs can't really be kept in a searchable manner. I think there will always be types of discussions that will be more appropriate for a chat room, or arise from them. The old clojure IRC logs are a real goldmine of interesting discussion that I stumble upon sometimes with google, and it's kinda sad that this is basically dead now due to slack's success
Zulip is cool but I feel it's kind of too late to get the whole community to move there in the way the people moved from IRC to slack
Status of clojurians-log: https://clojureverse.org/t/clojurians-log-working-on-a-relaunch-cloud-sponsor-exoscale/4158
I thought I read somewhere that there were GDPR related issues and it wasn't just a matter of the project being stalled
It is a certainty that the Clojure community will stop using Slack at some point in the future. Whether it moves to something else, or ceases to be, is a separate question 🙂
@jjttjj no need for moving. It’s about having a place that is more appealing to smaller communities (ie having a lower pace).
@jjttjj There was some discussion around the GDPR implications of auto-logging from Slack to another location -- mostly around folks not necessarily knowing that what they post here, in an essentially private forum, might end up publicly searchable via Google when published on a logging site. There are questions about whether users need to be able to opt out of logging, whether the logging site needs to support the "right to forget" and so on. I don't know that anyone really knows the answers since a lot of the GDPR has yet to be tested in court.
i don't know that the spirit of the law is to stunt open source communities. maybe showing a best effort in case someone would want to be removed, even after the fact would be good enough
What you say makes sense, but it also doesn't exactly encourage folks not wanting legal troubles to volunteer their time to spearhead those efforts. If they had clear answers to what was enough, before starting their volunteer efforts, it would be more likely to happen, I would guess.
Though there is many other targets for such an action. Plenty of malicious compliance, or plain non compliance on juicier targets
The existence of other targets doesn't exactly help one, if one is also targeted.
true again, but where do we stop then, there is no certainty outside testing it in court
I am simply saying that non-profit efforts are unlikely to be pushing for creating test cases, unless they are some organization like the ACLU that does that for their reason-for-being. They will instead wait, indefinitely, until someone else establishes case law for them.
Well, unless you would like to go forward with it, or convince someone else to volunteer
In the mean time, Zulip chat is logging things searchably, in the same gray-ish legal area.
too bad zulip has only part of the channels, and i had little success with the search function there
It is easy to enable logging for more channels on Zulip, for anyone, not just the admins, I believe. I can look up the message you must send to the Slack channel to start it happening.
just to make sure I'm doing this right:
1.) create stream with same name on Zulip (i.e.
onyx to match Slack
2.) on the Slack channel side, run
(Is #1 actually necessary?)
I notice that the #jackdaw stream doesn't exist on Zulip running the
/invite responds with
@zulip-mirror-bot is already in this channel, so I suspect I'm missing something here
The mirror channels/topics are "inside" of the top level slack-archive topic on Zulip
@U22M06EKZ Andy is correct: do not create a stream on Zulip. Just invite the bot into the Slack channel you want mirrored -- most of them already have the bot but there may be some smaller, lower traffic channels that do not.
I'm struggling to find the Slack archive for topics -- if I look at the #zulip stream, I see a
slack archive header, but it doesn't contain the contents off any other channels. Even the Clojure stream doesn't seem to have a "slack archive" topic, so it must be elsewhere.
Could either of you spell out exactly where I should look for say, the #cider archive history?
https://clojurians.zulipchat.com/#narrow/stream/180378-slack-archive -- that's the stream -- and here's the cider topic https://clojurians.zulipchat.com/#narrow/stream/180378-slack-archive/topic/cider
If you search for a topic named for the Slack channel, that should also work:
topic:cider (and press enter/return) that should find the #cider channel archive.
I just did
/topic:off-topic<return> and found these messages at the of that topic 🙂
@U04V70XH6 Figured it out, thanks!
I had to make sure to put a full
stream:slack-archive topic:cider, but now I can view any channel. That's awesome for some of the smaller libraries I've been using (Onyx & Jackdaw come to mind).
Appreciate the help & work it took to get the Zulip bot online!
(I documented this in the #zulip
slack archive topic, so hopefully helps in the future too)
Every person who chooses to go on-line and engage in conversation makes their own individual choice of what medium to use, every time. Clojurians Slack is currently a popular choice, but it will not always be so. It could change next year, for all we know.
slack is the de facto official clojure chat. I may not like it, but I don't see that changing any time soon. Not a huge deal if it wasn't for this logging issue