that’s what worries me because there’s no objective criterion for that to end
eh, I think it’s a mix
> Sorry for playing a certain amount of hardball on this one, but we don't want to massively reshuffle things until we see if this works well. this is certainly relevant
so even if we have this productivity forever...
maybe
well, I think part of it is the case of people getting used to the idea
It feels like dysfunction is what we already have though 😄
sure
I agree, and that’s kinda what worries me
it’s a social problem, not a technical one (isn’t it always)
yeah, definitely. A mix of status quo bias and a certain degree of entitlement.
I’d consider asking Tom directly if he’s the person making the decision about whether and when cloverage can be transfered to the github group. If he’s not, ask to involve them in the conversation directly (I expect there’s a certain amount of he-said she-said going on when you ask for specific requirements); possibly via email if they’re more comfortable with a private conv. Maybe give them a day to respond to your last comments though 😛 Also be aware that everyone in LShift is in the UK so the timezones are part of why the discussion takes a while
Anyway, good luck, and I wanna say again how I’m really happy to see some movement around cloverage again 🙂
sure, I also want to be cognizant of their point of view
I think it’ll end up OK, it’s just, eh, uncomfortable right now
I am definitely glad that it is moving as well
It’s hard for me to argue for Clojure internally when we can’t have decent code coverage