📅 Original date posted:2013-10-21
📝 Original message:I was wondering, would it be possible to create an area where proposals like your NODE_BLOOM and BIP 38 could live?
On 2013-10-20, at 11:25 PM, Peter Todd <pete at petertodd.org> wrote:
> On Sun, Oct 20, 2013 at 08:27:47PM -0400, Jeff Garzik wrote:
>> On Sun, Oct 20, 2013 at 6:43 PM, Peter Todd <pete at petertodd.org> wrote:
>>> FWIW I think that BIP's should have been done as a github repository,
>>> allowing for dealing with this stuff transparently as a pull-request.
>>> It'd also be useful to handle BIP's that way to make it easy to archive
>>> them, update them, and keep a log of what and why they were updated.
>>> Just put them in markdown format, which is pretty much feature
>>> equivalent to the wiki now that markdown supports images.
>>
>> Agreed -- let's do it. I nominate you to do the conversion, and we'll
>> put it up at github.com/bitcoin/bips.git.
>
> Done: https://github.com/petertodd/bips/
>
> GitHub supports MediaWiki these days, so just directly copying from
> 'View Source' in the bitcoin.it wiki worked pretty well; I archived the
> exact text of BIP. Tables, images and math is all supported by github
> and look fine, although github doesn't seem to support coloration in
> tables. Users wishing to edit their pull-req's or create new ones can do
> so easily by forking the repository - they can see their changes as they
> go in GitHub.
>
> I've probably missed some stuff re: formatting, and I haven't changed
> any of the submission guideline text in bip 1 yet, but that's probably
> 90% of the work done.
>
> --
> 'peter'[:-1]@petertodd.org
> 000000000000000245a735ccc14b98552e152f773c07efa2e89dd7f0463f61cf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131020/6a8548ee/attachment.sig>;
Jean-Paul Kogelman [ARCHIVE] /
npub1sa…8y304
2023-06-07 17:07:37
in reply to nevent1q…jewm
Author Public Key
npub1sa86gng3pvs3jgyt5majwcrhn8ck5qxgy9pjqxkh79u638cd7dys28y304Seen on
wss://relay.noswhere.comPublished at
2023-06-07 17:07:37Event JSON
{
"id": "0812a1ea9c75c0b8f00b52154d76f8f636df9a48ab9b10c1a14b893d62071c71",
"pubkey": "874fa44d110b2119208ba6fb27607799f16a00c82143201ad7f179a89f0df349",
"created_at": 1686150457,
"kind": 1,
"tags": [
[
"e",
"d7c1869dab2bd34b6e5ae79cda5d73bda811a1af3e65276521fa77a929d2819d",
"",
"root"
],
[
"e",
"cd79d1716a414945642f83fb66955031bf5eb04806e1a321a023360068436785",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2013-10-21\n📝 Original message:I was wondering, would it be possible to create an area where proposals like your NODE_BLOOM and BIP 38 could live? \n\nOn 2013-10-20, at 11:25 PM, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\n\u003e On Sun, Oct 20, 2013 at 08:27:47PM -0400, Jeff Garzik wrote:\n\u003e\u003e On Sun, Oct 20, 2013 at 6:43 PM, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\u003e\u003e\u003e FWIW I think that BIP's should have been done as a github repository,\n\u003e\u003e\u003e allowing for dealing with this stuff transparently as a pull-request.\n\u003e\u003e\u003e It'd also be useful to handle BIP's that way to make it easy to archive\n\u003e\u003e\u003e them, update them, and keep a log of what and why they were updated.\n\u003e\u003e\u003e Just put them in markdown format, which is pretty much feature\n\u003e\u003e\u003e equivalent to the wiki now that markdown supports images.\n\u003e\u003e \n\u003e\u003e Agreed -- let's do it. I nominate you to do the conversion, and we'll\n\u003e\u003e put it up at github.com/bitcoin/bips.git.\n\u003e \n\u003e Done: https://github.com/petertodd/bips/\n\u003e \n\u003e GitHub supports MediaWiki these days, so just directly copying from\n\u003e 'View Source' in the bitcoin.it wiki worked pretty well; I archived the\n\u003e exact text of BIP. Tables, images and math is all supported by github\n\u003e and look fine, although github doesn't seem to support coloration in\n\u003e tables. Users wishing to edit their pull-req's or create new ones can do\n\u003e so easily by forking the repository - they can see their changes as they\n\u003e go in GitHub.\n\u003e \n\u003e I've probably missed some stuff re: formatting, and I haven't changed\n\u003e any of the submission guideline text in bip 1 yet, but that's probably\n\u003e 90% of the work done.\n\u003e \n\u003e -- \n\u003e 'peter'[:-1]@petertodd.org\n\u003e 000000000000000245a735ccc14b98552e152f773c07efa2e89dd7f0463f61cf\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 842 bytes\nDesc: Message signed with OpenPGP using GPGMail\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131020/6a8548ee/attachment.sig\u003e",
"sig": "dac5abbf121e769d1e9b59914f962bb09b3aac93a850e00ff05af28037090ad13e5e945d283e7726a6dec0bc1a8e27b47f3ecf8b893f9087b6309510d7f5ba6b"
}