19:00:46 #startmeeting 19:00:46 Meeting started Thu Jul 16 19:00:46 2020 UTC. The chair is wumpus. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:46 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:00:49 hi 19:00:56 hi 19:01:13 hi 19:01:20 hi 19:01:22 hi 19:01:48 hi 19:01:50 hi 19:01:55 hi 19:01:57 one proposed topic: 0.20.1rc1 (fanquake) 19:02:02 any last minute topic suggestions? 19:03:05 #topic High priority for review 19:03:12 hi 19:03:34 #19334 for hi prio 19:03:36 https://github.com/bitcoin/bitcoin/issues/19334 | wallet: Introduce WalletDatabase abstract class by achow101 · Pull Request #19334 · bitcoin/bitcoin · GitHub 19:03:56 https://github.com/bitcoin/bitcoin/projects/8 11 blockers, 1 bugfix, 3 chasing concept ACK 19:04:11 hi 19:04:14 may I ask for #18710 to hi prio? 19:04:17 https://github.com/bitcoin/bitcoin/issues/18710 | Add local thread pool to CCheckQueue by hebasto · Pull Request #18710 · bitcoin/bitcoin · GitHub 19:04:50 achow101: added 19:05:30 hi 19:05:48 hebasto: added 19:05:57 wumpus: thanks! 19:06:52 another one was already merged, so we're at 12 blockers now 19:06:59 enough to review for everyone I'd hope 19:07:12 haven't seen it help tbh 19:07:13 oh 11 even 19:08:15 wumpus: please add #11082 19:08:20 https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub 19:08:59 luke-jr: added 19:09:14 it also has a "Waiting for author" label that should be removed AFAICT 19:09:36 ok 19:09:59 #topic 0.20.1rc1 (fanquake) 19:10:11 I guess technically #18818 needs to be dropped from the high-prio list. Nobody seems to care to review it, and it's not like the tarball has ever really worked anyway :/ 19:10:14 https://github.com/bitcoin/bitcoin/issues/18818 | Fix release tarball generated by gitian by luke-jr · Pull Request #18818 · bitcoin/bitcoin · GitHub 19:11:12 "I won't be at the meeting. However my input for my topic is that I think #19524 should be merged, and a 0.20.1rc1 tagged today/tomorrow. We've dragged our heels on this, and there is a publicly know issue affecting at-least the two most recent releases." 19:11:14 https://github.com/bitcoin/bitcoin/issues/19524 | [0.20] Backport #19517 - Increment input value sum only once per UTXO in decodepsbt by fanquake · Pull Request #19524 · bitcoin/bitcoin · GitHub 19:11:55 I agree with fanquake there; that PR has been merged now, so I intend to start the release process for 0.20.0rc1 soon 19:12:03 ack 19:12:09 ack 19:12:18 sgtm 19:12:21 sgtm 19:12:33 unless we want to merge Taproot with flagday activation on Dec 1st :P j/k 19:12:50 hehe 19:13:12 let's leave that for .2 :) 19:13:18 could a one line fix of https://github.com/bitcoin-core/gui/issues/32 bug could be included in 0.20.1 ? 19:13:53 how bad is it? 19:14:32 a user has problems while onboarding and choosing custom datadir 19:15:07 Fix is very simple #19536 19:15:08 https://github.com/bitcoin/bitcoin/issues/19536 | qt, build: Fix QFileDialog for static builds by hebasto · Pull Request #19536 · bitcoin/bitcoin · GitHub 19:15:28 I'm not sure that's critical enough to hold the release up further tbh 19:15:37 ok 19:15:45 but ok, it's a one line change 19:15:48 in bulid system 19:15:51 #proposedtopic p2p irc meeting 19:16:22 it means rebuilding Qt, but IMO should be fixed anyway 19:16:24 I'm sure we can get that merged and backported tomorrow if the build system people people review it 19:17:10 yes, it requires a rebuild of qt so would make the build somewhat longer 19:18:03 #topic p2p irc meeting (jnewbery) 19:18:16 thanks wumpus 19:18:32 I'd like to start a fortnightly (that's every two weeks) meeting in this channel for p2p PRs. 19:18:45 It seems like there are enough people doing interesting things in p2p that a short check-in to share what everyone’s focus is would be helpful 19:18:59 I’m aware of the following people actively working on p2p projects: 19:19:04 vasild (addrv2), carl (addrv2 and parallel validation protocol), aj (various), suhas (wtxid relay and various), gleb (addr relay and various), amiti (refactor peer types, testing, tx relay), sipa (tx relay and various), troy (logging), me (net/net_processing split) 19:19:17 ... and there are probably a bunch more that I’m temporarily not remembering. 19:19:24 Yup, I am, but I don't talk about it. 19:19:43 sounds good to me, though, don't those topics fit in the normal meeting? we generally have enough time for more topics in the main meeting 19:19:43 +1 i wanna lurk 19:20:04 jonatack: yes, I've seen you've been reviewing a bunch of PRs. There are quite a few other regular reviewers too 19:20:12 it might end up just being a five minute check in on what everyone's focus is that week. I don't like having long meetings for meetings' sake. 19:20:48 are there other code area-specific meetings? 19:20:54 the wallet meeting 19:21:02 jnewbery: it seems the biggest hurdle may be getting all those people on irc at the same time :) 19:21:05 build meeting 19:21:10 ack 19:21:19 gzhao408: there's a fortnightly wallet meeting, which I think was very successful at focusing attention (at least initially) 19:21:30 bitcoin-builds even has its own IRC channel, but no planned time afaik? 19:21:31 we've informally been doing meetings for buildsystem discussion too lately 19:21:36 imhere now, a bit sleepy though ;) 19:21:38 ohh 19:21:39 ^^ what hebasto said. 19:21:42 sipa: agree. this hour is too late for me tbh. 19:22:02 yes, with apologies to our antipodean friends I'm going to suggest that we do the same time on a different day 19:22:03 aj is also in a timezone far away from most others 19:22:47 jnewbery: i think it may make sense to first see people's availability and preferences; if this time of day would be a good meeting time, those people would already be here in this meeting right now, i'd expect 19:22:52 jnewbery: 1 min while everyone googles antipodean. 19:22:53 or we could do an hour or two earlier and still get america and europe. Again, sorry to Asia and Australia :( 19:23:17 TIL :) 19:23:23 ok, I don't think we need to figure out a time now. Was more looking for concept ACKs/NACKs 19:23:37 concept ACK 19:23:48 concept ACK 19:23:54 concept ACK 19:23:57 these hours are pretty US-centric, would be nice to alternate a bit if possible, ACK if earlier 19:23:58 concept ACK! I'm a fan of the idea of a p2p focused meeting. even if we can't get everyone at the same time, encouraging convo between our work tracks seems great! 19:23:59 like I said, I'd prefer to keep the meeting short. I think there's always value in hearing what other people's focus is 19:24:25 concept ACK, but conditional on finding a good time and buy-in :) 19:24:53 I defintely want to avoid adding an hour of unproductive time to people's calendars 19:24:57 my reasoning: if it'll just end up being the people who are here today now, we can also do it regular weekly meetings, especially if it's short 19:25:32 yes, that was also my only remark 19:25:37 maybe meetings could be called for by a sponsor when there's something concrete to discuss? 19:26:30 cfields jonatack: I think these things have much more chance of succeeding if they have a regular reliable time/day 19:26:38 i agree with that 19:26:48 fair enough. 19:27:22 cfields: antipodean:feet on the wrong end 19:27:57 ok, I'll try to figure out a process for choosing a time 19:28:01 antipodism (uncountable) 19:28:02 A form of foot juggling where the juggler lies on his or her back, usually on a sort of chair. 19:28:38 hehe 19:28:39 Ah yes, regular occurrence down here 19:28:41 clearly I was confused as that's the only usage I know ;) 19:28:54 I think there's no further topics for today then 19:29:11 #endmeeting