Fork me on GitHub
Alex Miller (Clojure team)19:03:32

if anyone is interested in helping with Clojure dev, Fogus and I have identified a list of bugs that need some cleanup and review before Rich looks at them for vetting in 1.12. We'd be happy to have help in this process. Depending on response, I'll decide how to convey what needs to be done, not sure if chat/zoom/1-1 makes the most sense. Drop in thread if interested.


I’d be interested, depending on availability.

Alex Miller (Clojure team)19:03:38

can be mostly or totally asynchronous and best effort :)

awesome 1

Perfect. Sounds do-able to me!


i’d love to help out in this

Ben Sless19:03:34

"You have my bow"

😂 2

Very interested in contributing one way or another -- but I don't have availability in March (but can dig in from April onward).


"And my axe!"

Alex Miller (Clojure team)20:03:55

well I don't think we're going to run out of tickets :)


Hi, I think I could help out. What kind of time commitment do you think this would be?

Alex Miller (Clojure team)21:03:30

whatever you want it to be :)

👍 1

Happy to help!


I won't have too much free time in the coming months but would be interested to know more in case I might be able to help after all


I would like to help


I'd like to help too 🙂


I'd like to help too.


obviously count me in :)

Alex Miller (Clojure team)16:03:44

I know many of you are already on the contributors list, but if not, please follow the instructions here to sign the CA and get access to jira:

Daniel Craig23:03:20

I'd like to help :)


I feel like an intruder in this channel 😆, but I'd like to help


would love to participate 🙂

Alex Miller (Clojure team)21:03:17

Updating on this... I kind of jumped into this with a list and an idea (and without a plan), so I am kind of forming that as I go. I rewrote this page yesterday: to cover a lot of the things I think are important and to serve as a written guide. I'm going to do a zoom on Monday 3/14 and will record it as well, still in the process of working through some IT things to get there. Time will be 9 am US Eastern, noon US Pacific, 4 pm GMT

👍 8

9am eastern will be 6am pacific

Alex Miller (Clojure team)22:03:32

gah, I flipped those - 9 am pacific, noon eastern is what I meant :)

👍 2

1700 CET? Will you be posting the zoom link here?

Daniel Craig19:03:11

Looking forward to the zoom call tomorrow!


Ah, ok, 16 and not 17 CEST:

Alex Miller (Clojure team)13:03:06

yes, sorry - the time is an hour earlier than I quoted last week (90 minutes from now), I am trying to dodge people working at my house (which I may still fail at) :) but, I'm going to record, so no worries if you miss it


Sad to miss the meeting. Had a work thing come up. Looking forward to watching the vid.


@U064X3EF3 You happen to have a link to the video?

Alex Miller (Clojure team)14:03:38

thx for the reminder, never got an alert back on that so let me check on it

Alex Miller (Clojure team)14:03:48

ok, I have it, just need to chop it down a bit and post it somewhere, not sure I will get to that today and I'm out rest of the week, so we'll see

🙏 2

So starting to look a bit into this, we have the filter for the 1.12 candidates. The first issue that pops up there seems to be in a state that’s somewhat more than triaged. looking at would it be correct to say that it’s in a state waiting to be vetted by Rich? I guess the problem I’m grapling with is wether there is anything for the community to do on this (and other similar issues) or if we should have some other filter for “Issues which are candidates for 1.12 which the community can help move forward”?

Alex Miller (Clojure team)15:03:56

everything in this list is something we would like Rich to look at and target for 1.12, so I would like them to be in a state where they are at least good problem reports and ideally good problems. some are in ok shape, some may not be

Alex Miller (Clojure team)15:03:18

maybe @U050WRF8X can look through them and suggest ones that need more work than others

👍 1
slipset15:03:07 could get a test? Shouldn’t be too difficult to write?

slipset15:03:25 seems to be in less than a pristine state, like, I’d need to look into the patch to understand the approach taken (I believe)


I’m just listing here as a future reference for myself/others if that’s ok.

Alex Miller (Clojure team)15:03:34

on 2126, yes test would be helpful, could just add it as an additional patch and list both in the description

slipset15:03:32 needs more investigation it seems, missing both an approach and a patch/test. Seems involved 🙂

Alex Miller (Clojure team)15:03:19

on 1872, more than anything I think the real problem here is one of clarifying abstractions and expectations. One thing I think is missing a little bit on this is the motivation for a case where it would be useful to want this. I've certainly run into it and seen others run into it, but I don't have a motivating case at hand.

Alex Miller (Clojure team)15:03:18

just to repeat, for the purposes of vetting/targeting, we don't actually care about the solutions or patches much (but of course, working on those is also useful)


I don’t seem to have edit rights on CLJ-2160 ?

Alex Miller (Clojure team)15:03:33

shouldn't be any ticket-specific differences

Alex Miller (Clojure team)15:03:53

I'm assuming you're logged in?



slipset15:03:50 is fairly involved would IMO warrant some tests

Daniel Craig15:03:57

Might be good to make corresponding comments in Jira


Noting 🙂


Can we move chatter re: work to the main channel and reserve this thread for getting started? I don’t wanna unsubscribe so Alex has a place to drop the link when he gets it ready.


Most certainly.

🙏 3
Ben Sless16:03:19

Any update on the recording?


buried in the thread but from alex: > ok, I have it, just need to chop it down a bit and post it somewhere, not sure I will get to that today and I’m out rest of the week, so we’ll see


it = the recording

Alex Miller (Clojure team)16:03:49

not there yet but the bits must flow ...

Ben Sless17:03:43

He who controls the bits, controls the clojureverse!