Clojurians Log v2

I’d be interested, depending on availability.

can be mostly or totally asynchronous and best effort :)

Perfect. Sounds do-able to me!

i’d love to help out in this

"You have my bow"

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!"

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?

whatever you want it to be :)

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

^ likewise

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

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

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

So starting to look a bit into this, we have the filter https://clojure.atlassian.net/issues/?filter=10032 for the 1.12 candidates. The first issue that pops up there https://clojure.atlassian.net/browse/CLJ-2521?filter=10032 seems to be in a state that’s somewhat more than triaged. looking at https://clojure.org/dev/workflow 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”?

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

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

https://clojure.atlassian.net/browse/CLJ-2126 could get a test? Shouldn’t be too difficult to write?

https://clojure.atlassian.net/browse/CLJ-1872 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.

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

https://clojure.atlassian.net/browse/CLJ-2698 needs more investigation it seems, missing both an approach and a patch/test. Seems involved 🙂

https://clojure.atlassian.net/browse/CLJ-2694 seems good

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.

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 ?

shouldn't be any ticket-specific differences

I'm assuming you're logged in?

D’oh. PEBCAK

https://clojure.atlassian.net/browse/CLJ-2160 is fairly involved would IMO warrant some tests

Might be good to make corresponding comments in Jira

Noting 🙂

https://clojure.atlassian.net/browse/CLJ-1929 could do with a test

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.

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

it's uploading

https://www.youtube.com/watch?v=e9uErbiQSro

not there yet but the bits must flow ...

He who controls the bits, controls the clojureverse!

I think it's up now

would love to participate 🙂

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

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: https://clojure.org/dev/screening_tickets 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

9am eastern will be 6am pacific

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

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

Yes

I would like to help

I'd like to help too 🙂

I'd like to help too.

obviously count me in :)

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: https://clojure.org/dev/dev#_becoming_a_contributor

I'd like to help :)

Ah, ok, 16 and not 17 CEST:

yes, sorry - the time https://everytimezone.com/s/541e6757 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.

Looking forward to the zoom call tomorrow!

speaking of... zoom: https://nubank.zoom.us/j/89103959413?pwd=b3dSNEJNaFZoTWppZEhyOWF1VHZtdz09 time: https://everytimezone.com/s/541e6757 info: https://clojure.org/dev/screening_tickets (as a starting point)