{"type":"rich","version":"1.0","author_name":"npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p","author_url":"https://nostr.ae/npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-11-19\n📝 Original message:On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik \u003cjgarzik at bitpay.com\u003e wrote:\n\n\u003e BIP drafts are stored in git://github.com/bitcoin/bips.git/drafts/ and\n\u003e are not automatically assigned a BIPS number.\n\u003e\n\nAre we going to move ahead with this?\n\nIf so, I'm volunteering to create the repository and import the current\nBIPs from the wiki there (and convert from wiki markup to markdown where\nnecessary).\n\n2) Time passes.  Software for BIP drafts is developed, tested,\n\u003e published, and publicly discussed in a typical open source manner.\n\u003e\n\nPersonally I think it is useful to have a number as soon as a BIP can be\nimplemented, even if still in draft status; it gives something to refer to\nwhen mentioning a certain improvement proposal (in commit messages and such\nit could be called BIP xxx Draft).\nI don't think we are at risk of running out of numbers to assign any time\nsoon.\n\nWladimir\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131119/295bc88c/attachment.html\u003e"}