Skip to content

Commit 2df5496

Browse files
hardingjnewbery
authored andcommitted
Meetings: minor improvements to 2018-07-12 and 2018-07-19
Includes some text about Bitcoin.org written by John Newbery
1 parent 494c83d commit 2df5496

File tree

2 files changed

+20
-15
lines changed

2 files changed

+20
-15
lines changed

_posts/en/meetings/2018-07-12-meeting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,8 +56,8 @@ there important things that [we] would otherwise miss but [which] are
5656
Several meeting participants listed things they'd like to get in that
5757
they're worried won't be complete before the freeze:
5858

59-
- [New `scantxout` RPC][#12196], mentioned by Jonas Schnelli
60-
- [New `disableprivatekey` setting][#9662] for watching-only wallets,
59+
- [New scantxout RPC][#12196], mentioned by Jonas Schnelli
60+
- [New disableprivatekey setting][#9662] for watching-only wallets,
6161
mentioned by Schnelli
6262
- [Partially-Signed Bitcoin Transactions support][#13557], mentioned by
6363
Andrew Chow

_posts/en/meetings/2018-07-19-meeting.md

Lines changed: 18 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -85,8 +85,8 @@ of this segment of the meeting for a review deadline of Monday.
8585
**Background:** Coin selection is the name used for how a wallet chooses
8686
which of a user's bitcoins to spend in a particular transaction. The
8787
selected *Unspent Transaction Outputs (UTXOs)*, often simply called
88-
*coins,* become *inputs* in the transaction. Developers have spent many
89-
hours in the past year improving Bitcoin Core's coin selection to be
88+
*coins,* become *inputs* in the transaction. Developers have spent
89+
a significant amount of time in the past year improving Bitcoin Core's coin selection to be
9090
able to sometimes improve privacy and lower transaction sizes (thus
9191
reducing fees) for users of Bitcoin Core's built-in wallet, with more
9292
improvements on the way.
@@ -181,7 +181,7 @@ node can use the seeder again if decentralized peer finding isn't
181181
working for it.
182182

183183
There are several seeder programs written by different authors. One of
184-
them is maintained by Pieter Wuille and is simply called `bitcoin-seeder`.
184+
them is maintained by Pieter Wuille and is simply called [bitcoin-seeder][].
185185

186186
**Discussion ([log][log seeder]):** Lucas Betschart requested and
187187
introduced the topic: "I thought because there are a few open issues and
@@ -197,18 +197,20 @@ it's the right message." Luke Dashjr echoed that sentiment.
197197

198198
## Moving away from Bitcoin.org
199199

200-
**Background:** Since the 2009 release of the original Bitcoin software,
201-
Bitcoin Core resources were traditionally hosted on Bitcoin.org. But
202-
over time, this was augmented with additional resources about the
203-
increasingly diverse Bitcoin network, so (in December 2015) Bitcoin Core
204-
began using its own domain---initially just to host its resources but
205-
now also to host its software releases. However, release announcements
206-
and software continue to be mirrored to Bitcoin.org.
200+
**Background:** since the 2009 release of the original Bitcoin software,
201+
Bitcoin (and later Bitcoin Core) resources have been hosted on
202+
Bitcoin.org. Over time, this was augmented with additional resources
203+
about the increasingly diverse Bitcoin network.
207204

208-
**Discussion:** please see the [log][log bco]. Note some discussion
209-
also occurred [after the meeting][post-meeting bco].
205+
In December 2015 Bitcoin Core began using its own domain to host its
206+
resources, and later also to host its software releases. Release
207+
announcements and software continue to be mirrored to Bitcoin.org.
210208

211-
[post-meeting bco]: https://botbot.me/freenode/bitcoin-core-dev/msg/102258762/
209+
**Discussion:** Andrew Chow introduced the topic by suggesting "moving away
210+
from Bitcoin.org". He added "we still link to bitcoin.org for things
211+
like downloads. [We] should probably change those". See the [log][log
212+
bco] for the full discussion. Some discussion also occurred [after the
213+
meeting][post-meeting bco].
212214

213215
**Conclusion:** no explicit conclusion. Post-meeting discussion seemed
214216
to indicate no significant changes to the current process.
@@ -292,13 +294,16 @@ and we will correct the mistake.
292294
[log seeder]: {{log}}#l-207
293295
[log bco]: {{log}}#l-231
294296
[log coredev meet]: {{log}}#l-279
297+
[post-meeting bco]: https://botbot.me/freenode/bitcoin-core-dev/msg/102258762/
298+
295299

296300
[meet osd]: /en/meetings/2018/06/28/#output-script-descriptors
297301
[osd gist]: https://gist.github.com/sipa/e3d23d498c430bb601c5bca83523fa82
298302
[coredev.tech]: https://coredev.tech/
299303

300304
[0.16.2rc2 bin]: https://bitcoincore.org/bin/bitcoin-core-0.16.2/test.rc2/
301305
[0.17 milestone]: https://github.com/bitcoin/bitcoin/milestone/33
306+
[bitcoin-seeder]: https://github.com/sipa/bitcoin-seeder
302307

303308

304309
{% include link-to-issues.md issues="9662,9502,13697,13666,13426,13712,8469,13617,12196,12257" %}

0 commit comments

Comments
 (0)