Last active
March 18, 2021 21:09
-
-
Save moneyball/071d608fdae217c2a6d7c35955881d8a to your computer and use it in GitHub Desktop.
Core Weekly Meeting Topic List
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| To propose a topic, post with tag #proposedmeetingtopic to #bitcoin-core-dev on freenode. | |
| Febuary 6, 2020 Meeting Topics | |
| - proposed by MarcoFalke: (short topic) Remove i686 Linux download link from bitcoincore website | |
| January 30, 2020 Meeting Topics | |
| - proposed by kanzure: topic idea collection for physical meeting | |
| January 23, 2020 Meeting Topics | |
| - none | |
| January 16, 2020 Meeting Topics | |
| - none | |
| January 9, 2020 Meeting Topics | |
| - none | |
| January 2, 2020 Meeting Topics | |
| - proposed by MarcoFalke: Vanilla debian Bitcoin Core package, #17343 | |
| December 12, 2019 Meeting Topics | |
| - proposed by sipsorcery: appveyor CI future | |
| December 5, 2019 Meeting Topics | |
| - proposed by emilengler: GUI CLI Arg test framework | |
| November 14, 2019 Meeting Topics | |
| - proposed by moneyball: next CoreDev ... proposing week of March 23, 2020 at Bitcoin 2020 in SF https://www.bitcoin2020conference.com/ | |
| November 7, 2019 Meeting Topics | |
| - proposed by nickler: security email address for bitcoin-core/secp256k1 (https://github.com/bitcoin-core/secp256k1/pull/679) | |
| - proposed by instagibbs: #17331 and opt-in SRD | |
| - proposed by wumpus: Move subtrees out of src/ | |
| - proposed by fanquake: not so much a topic, but a reminder that if everyone wants to air / dump their GitHub grievances into #15847, I'll be discussing with GH next week | |
| October 31, 2019 Meeting Topics | |
| - proposed by moneyball: follow-up on travis and #16148 | |
| - proposed by wumpus: close Boost → C++11 migration project for now | |
| - proposed by dongcarl: MacOS, notarization https://github.com/bitcoin/bitcoin/issues/15774 | |
| - proposed by jeremyrubin: epoch mempool | |
| October 24, 2019 Meeting Topics | |
| - none | |
| October 17, 2019 Meeting Topics | |
| - proposed by moneyball: taproot proposal next steps; possible review sessions | |
| October 10, 2019 Meeting Topics | |
| - proposed by BlueMatt: #16834 | |
| October 3, 2019 Meeting Topics | |
| - proposed by moneyball: travis and #16148 | |
| September 26, 2019 Meeting Topics | |
| - proposed by instagibbs: what to do with change output creation with bech32-default Core wallets: https://github.com/bitcoin/bitcoin/issues/15560#issuecomment-531796601 | |
| September 19, 2019 Meeting Topics | |
| - proposed by instagibbs: what to do with change output creation with bech32-default Core wallets: https://github.com/bitcoin/bitcoin/issues/15560#issuecomment-531796601 | |
| - proposed by wumpus: making better use of Transifex | |
| - proposed by fanquake: #16883: QML based mobile GUI - feel free to skip if I'm not up. | |
| - proposed by fanquake: #16713 Ignore old versionbit activations to avoid 'unknown softforks' warning | |
| September 12, 2019 Meeting Topics | |
| - proposed by aj: p2p pr dashboard https://gist.github.com/ajtowns/6073bd110b9f3193293b4321ce8a0394 | |
| September 5, 2019 Meeting Topics | |
| - proposed by jnewbery: review/merge #16704 or #16713 to remove worrying "unknown new rules activated (versionbit 1)" warning | |
| - proposed by fjahr: Rolling UTXO set hash | |
| - proposed by achow101: avoid loading every wallet transaction into memory | |
| August 29, 2019 Meeting Topics | |
| - proposed by fanquake: transifex org discussion | |
| - proposed by luke-jr: macOS/GNOME developers pushing their UI on everyone else | |
| August 22, 2019 Meeting Topics | |
| - proposed by dongcarl: upgrade to C++17 | |
| August 15, 2019 Meeting Topics | |
| - none | |
| August 8, 2019 Meeting Topics | |
| - proposed by MarcoFalke: Who wants to volunteer as co-maintainer of the Bitcoin Core flatpak? | |
| - proposed and cancelled by dongcarl: [maybe short] generic feature-signaling message for non-monotonic features that don't fit in the protocol version model (like BIP 36) | |
| - proposed by MarcoFalke: GitHub ci | |
| August 1, 2019 Meeting Topics | |
| - proposed by fanquake: Do we have any contributors that are likely to be affected by GH blocking access/functionality in certain countries. | |
| - proposed by jonasschnelli: bitcoin-dev mailing list moderation | |
| - proposed by BlueMatt: is transaction.nVersion signed or unsigned? | |
| - proposed by wumpus: 0.18.1 ready for final? | |
| July 25, 2019 Meeting Topics | |
| - proposed by amiti: Transaction Rebroadcasting https://gist.github.com/amitiuttarwar/b592ee410e1f02ac0d44fcbed4621dba | |
| July 18, 2019 Meeting Topics | |
| - proposed by MarcoFalke: Remove mempool expiry, treat txs as replaceable instead #16409 | |
| - proposed by MarcoFalke: 0.18.1 | |
| - proposed by sdaftuar: -blocksonly not being a hidden option in 0.18.1 | |
| July 11, 2019 Meeting Topics | |
| - none | |
| July 4, 2019 Meeting Topics | |
| - none | |
| June 27, 2019 Meeting Topics | |
| - proposed by MarcoFalke: 0.18.1: Backports #16035 | |
| - proposed by cfields: depends build cache | |
| June 20, 2019 Meeting Topics | |
| - proposed by jnewbery: Bitcoin Core PR review club (https://bitcoin-core-review-club.github.io/) | |
| - proposed by fanquake: ASN blob discussion that was missed at the end of last meeting. Assuming sipa and bluematt are available. | |
| - proposed by fanquake: Requiring 2FA for bitcoin orgs on GH. This was discussed a little at Core dev, and we got 4-5 members to turn 2FA on. | |
| June 13, 2019 Meeting Topics | |
| - proposed by MarcoFalke: Update EOL dates https://github.com/bitcoin-core/bitcoincore.org/pull/659#issuecomment-499884131 | |
| - proposed by moneyball: when/where should we have next CoreDev? | |
| - proposed by jonasschnelli: travis stability and usefulness in current state | |
| June 6, 2019 Meeting Topics | |
| - no meeting | |
| May 30, 2019 Meeting Topics | |
| - topic proposed by jnewbery: has travis got worse or have we just added so many builds to our job that it times out? | |
| - topic proposed by moneyball: please review GitHub feedback issue and vote with thumbs up on issues you think you make the top 10 https://github.com/bitcoin/bitcoin/issues/15847 | |
| May 23, 2019 Meeting Topics | |
| - none | |
| May 16, 2019 Meeting Topics | |
| - none | |
| May 9, 2019 Meeting Topics | |
| - topic proposed by MarcoFalke: windows 32 bit | |
| May 2, 2019 Meeting Topics | |
| - none | |
| April 25, 2019 Meeting Topics | |
| - topic proposed by MarcoFalke: 0.18.0-final early next week? | |
| April 18, 2019 Meeting Topics | |
| - topic proposed by sipa: Should send-to-non-v0-witness be standard (spending such outputs is nonstandard independently) | |
| - topic proposed by jnewbery: Bitcoin Core design documentation | |
| - topic proposed by MarcoFalke: net: Hardcoded seeds update for 0.18 (#15791, #7398) (wumpus) | |
| - topic proposed by moneyball: opportunity to provide feedback with GitHub CEO | |
| April 11, 2019 Meeting Topics | |
| - topic proposed by cfields: Bitcoin CRust; Potential platform deprecation | |
| April 4, 2019 Meeting Topics | |
| - none | |
| March 28, 2019 Meeting Topics | |
| - topic proposed by gmaxwell: Bech32 support shipped first in Bitcoin Core in Feb 2018, more than a year ago. We should consider making an announcement that Bitcoin Core intends to change the default addresstype from p2sh-segwit to bech32 in 0.19 or 0.20. | |
| - (obviously we'd continue to support getting p2sh-segwit on demand, but any service that doesn't support sending to bc1x addresses would see a rise in complaints/support requests. | |
| - https://en.bitcoin.it/wiki/Bech32_adoption < useful reference. | |
| - (and now I think I've said enough that the discussion can be had without me around) | |
| - https://github.com/bitcoin/bitcoin/issues/15560 | |
| March 21, 2019 Meeting Topics | |
| - none | |
| March 14, 2019 Meeting Topics | |
| - none | |
| March 7, 2019 Meeting Topics | |
| - none | |
| February 28, 2019 Meeting Topics | |
| - none | |
| February 21, 2019 Meeting Topics | |
| - none | |
| February 14 (<3), 2019 Meeting Topics | |
| - topic proposed by provoostenator: minimum QT version for v0.18, see #13478 | |
| February 7, 2019 Meeting Topics | |
| - none | |
| January 31, 2019 Meeting Topics | |
| - topic proposed by luke-jr: Possibly change to rebasing policy | |
| January 24, 2019 Meeting Topics | |
| - topic proposed by jnewbery: Chaincode summer residency: looking for (remote) mentors and recommendations for residents | |
| January 17, 2019 Meeting Topics | |
| - none | |
| January 10, 2019 Meeting Topics | |
| - none | |
| January 3, 2019 Meeting Topics | |
| - topic proposed by achow101: having users create their wallets instead of automatically creating a default wallet | |
| December 13, 2018 Meeting Topics | |
| - topic proposed by jamesob: I'd like to revisit making some headway on one of the outstanding "add address index" PRs (e.g. #14035). Many companies end up using dubious peripheral systems (e.g. Bitcore) simply because bitcoind doesn't offer an address index, and I think there's a case to be made that the engineering costs & risk associated with maintaining such an index in core is outweighed by the practical risk many companies assume in having to run less-than-ideal indexing software. Would like to also discuss the alternative of having a "blessed" peripheral program that does indexing should an in-core index prove objectionable. | |
| December 6, 2018 Meeting Topics | |
| - topic proposed by moneyball: next CoreDev meetup...be ready to give feedback at Thursday's weekly meeting...considering 3 days prior to Breaking Bitcoin June 5-7 in Amsterdam https://twitter.com/breakingbitcoin/status/1070060118866305026 | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On "Bitcoin Core design documentation":
There are currently a lot of high-level design considerations that aren't documented in the codebase. Some of them may exist in individual contributor's gists, or might not be written down at all. Should we try to have some standard location to put them in so it's easier for people to understand why things are the way they are? One suggestion would be to use github's wiki feature.