From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Move authorative source for BIPs to git repository
Date: Thu, 5 Dec 2013 14:27:43 +0000 [thread overview]
Message-ID: <201312051427.44179.luke@dashjr.org> (raw)
In-Reply-To: <CA+s+GJCuWNj7LuLJy4rSkN_t0qgO3UsBS2hEBTgm6DiiQyqbVQ@mail.gmail.com>
On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:
> Hello all,
>
> A while ago after discussion on the mailing list a repository was set up to
> store the BIP documents, as this is deemed a more secure solution than
> having them on the wiki:
>
> https://github.com/bitcoin/bips
>
> To prevent confusion the next step should probably be to replace the BIPs
> on the wiki with links to the github documents, with a notice that changes
> should be proposed on github or mailed to the BIP editor (gmaxwell).
>
> Agreed?
I think this would stifle active BIP draft editing. We're already having a
hard time getting some developers to write BIPs for their proposals - I don't
think we should be putting up bigger hurdles.
Luke
next prev parent reply other threads:[~2013-12-05 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 13:37 Wladimir
2013-12-05 14:27 ` Luke-Jr [this message]
2013-12-05 14:38 ` Wladimir
2013-12-05 14:43 ` Jeff Garzik
2013-12-05 20:49 ` Gary Rowe
2013-12-05 23:16 ` Gavin Andresen
2013-12-06 13:41 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201312051427.44179.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox