01:22 <isd> Reminder: office hours in ~40 min

01:27 <JacobWeisz[m]> I did a mailing list post too in case it helps remind people more.

01:28 <isd> Saw that.

01:28 <isd> Thanks.

02:01 <isd> Reminder: office hours

02:05 <isd> I seem to be the only one here, though I see ocdtrekkie put a bunch of stuff down on the agenda.

02:09 <isd> well, nevermind then.

02:11 <JacobWeisz[m]> Oh shoot

02:11 <JacobWeisz[m]> Gosh darnit.

02:12 <JacobWeisz[m]> Nobody else showed up?

02:12 <isd> Nope

02:12 <isd> I hung around for 10 min or so

02:14 <JacobWeisz[m]> Well then, uh, I'm available now if you want to chat about anything I put up there. Or, you know, there's IRC...

02:14 <isd> I feel like the occasional check-in is useful, but there's a lot of overhead in setting up a notes page, copying stuff to the wiki, and reminding everyone that it's a thing. and it seems like half the time we've kinda discussed everything on IRC already...

02:15 <isd> Maybe we could just shift more formally to a vague periodic IRC-check-in.

02:16 <JacobWeisz[m]> I just wonder if something like github.com/sandstormports/community-project might be a better way to asynchronously do that than IRC. Which isn't too much better than office hours.

02:17 <isd> I mean, for individual issues there's the issue tracker.

02:18 <JacobWeisz[m]> Yeah, my thought was maybe to pull away from the formal project tracking (and issues on various projects, outside of the main one)

02:18 <isd> IRC is nice in that it is semi-synchronous; you can still kinda have live conversations, but there's automatic logging so you can just look back at the history if you need to catch up. And the logging also means we don't have to be quite as judicious about notes (which we have been failing to do)

02:19 <JacobWeisz[m]> True

02:25 <isd> I want a better issue tracker. I feel like keeping track of "what's on my plate" and/or "who's working on what" should be easier, and shouldn't require setting up a separate tracker...

02:31 <isd> I wish it were easier to filter prs where "the ball is in my court" so to speak.

02:35 <JacobWeisz[m]> Yeah, "ready for review" is basically meant to be that for Kenton. But it's hard to do that for everyone.

10:08 <xet7> isd: Better issue tracker? Like Wekan? ;)

10:08 <xet7> Although, I should fix bug of only 20 newest comments visible

10:09 <crab> i've used wekan to do some issue tracking, and it worked nicely.

23:49 <isd> The thing I'm struggling with most re: issue tracking is at any given time I'm working on stuff across like 5-10 different repos, often with dependency edges that cross repos (e.g. ocap-merkledag stuff is currently blocked on haskell-capnp stuff)

23:49 <isd> ...dependency tracking in general is something that would be really useful.

23:50 <isd> I'd also like to be able to add personally-scoped metadata to issues that I don't "own"; I should be able to organize issues that are relevant to me but are "owned" by projects I don't have privileges for.