Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vofs3-0006D4-U0 for bitcoin-development@lists.sourceforge.net; Thu, 05 Dec 2013 20:50:03 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.175 as permitted sender) client-ip=209.85.220.175; envelope-from=g.rowe.froot@gmail.com; helo=mail-vc0-f175.google.com; Received: from mail-vc0-f175.google.com ([209.85.220.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Vofs2-0006DI-DI for bitcoin-development@lists.sourceforge.net; Thu, 05 Dec 2013 20:50:03 +0000 Received: by mail-vc0-f175.google.com with SMTP id ld13so13663037vcb.34 for ; Thu, 05 Dec 2013 12:49:57 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.220.124.68 with SMTP id t4mr16549vcr.52.1386276596819; Thu, 05 Dec 2013 12:49:56 -0800 (PST) Sender: g.rowe.froot@gmail.com Received: by 10.220.205.71 with HTTP; Thu, 5 Dec 2013 12:49:56 -0800 (PST) In-Reply-To: References: <201312051427.44179.luke@dashjr.org> Date: Thu, 5 Dec 2013 20:49:56 +0000 X-Google-Sender-Auth: y39uCSpMeSTifhlPjuzq97yGx7Y Message-ID: From: Gary Rowe To: Bitcoin Development List Content-Type: multipart/alternative; boundary=089e013a29081d5add04eccfacf4 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: doubleclick.net] -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (g.rowe.froot[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Vofs2-0006DI-DI Subject: Re: [Bitcoin-development] Move authorative source for BIPs to git repository X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 20:50:04 -0000 --089e013a29081d5add04eccfacf4 Content-Type: text/plain; charset=UTF-8 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 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 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 > --089e013a29081d5add04eccfacf4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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. =C2=A0Pl= ease review the previous
discussion, before asking the same questions over again.

Properly done, there are FEWER hurdles. =C2=A0In the previous discussion, there was outlined a process whereby the BIPS Editor would receive an
email, and could take it from there. =C2=A0No wiki login or bitcoin payment=
required. =C2=A0More 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:
>>
>> http= s://github.com/bitcoin/bips
>>
>> To prevent confusion the next step should probably be to replace t= he 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.ne= t/gampad/clk?id=3D111408631&iu=3D/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-d= evelopment@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitco= in-development



--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0https://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/gam= pad/clk?id=3D111408631&iu=3D/4140/ostg.clktrk
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--089e013a29081d5add04eccfacf4--