From: Gary Rowe <g.rowe@froot.co.uk>
To: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Move authorative source for BIPs to git repository
Date: Thu, 5 Dec 2013 20:49:56 +0000 [thread overview]
Message-ID: <CAKm8k+2=kSeDALJJLF9hPfuyDyHN+G9Dx6cQRPGgcKRVOW-4aA@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0OhQn=+BpbvejqRZBv=x3Vd5BYSDERERMEYDrrQ0gRXkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2685 bytes --]
Personally, I would be more inclined to submit and work on a BIP if it was
in GitHub. It's a regular home from home for me now.
On 5 December 2013 14:43, Jeff Garzik <jgarzik@bitpay.com> wrote:
> This entire discussion is recycled. Please review the previous
> discussion, before asking the same questions over again.
>
> Properly done, there are FEWER hurdles. In the previous discussion,
> there was outlined a process whereby the BIPS Editor would receive an
> email, and could take it from there. No wiki login or bitcoin payment
> required. More advanced users may submit pull requests.
>
> Compared with a hash-sealed git repo as primary source, the wiki is
> second class.
>
>
> On Thu, Dec 5, 2013 at 9:27 AM, Luke-Jr <luke@dashjr.org> wrote:
> > 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
> >
> >
> ------------------------------------------------------------------------------
> > Sponsored by Intel(R) XDK
> > Develop, test and display web and hybrid apps with a single code base.
> > Download it for free now!
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
>
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 4157 bytes --]
next prev parent reply other threads:[~2013-12-05 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 13:37 [Bitcoin-development] Move authorative source for BIPs to git repository Wladimir
2013-12-05 14:27 ` Luke-Jr
2013-12-05 14:38 ` Wladimir
2013-12-05 14:43 ` Jeff Garzik
2013-12-05 20:49 ` Gary Rowe [this message]
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='CAKm8k+2=kSeDALJJLF9hPfuyDyHN+G9Dx6cQRPGgcKRVOW-4aA@mail.gmail.com' \
--to=g.rowe@froot.co.uk \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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