From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VYMXG-0001g6-JG for bitcoin-development@lists.sourceforge.net; Mon, 21 Oct 2013 20:57:10 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.47 as permitted sender) client-ip=209.85.219.47; envelope-from=benjamin.l.cordes@gmail.com; helo=mail-oa0-f47.google.com; Received: from mail-oa0-f47.google.com ([209.85.219.47]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VYMXF-0006kl-G0 for bitcoin-development@lists.sourceforge.net; Mon, 21 Oct 2013 20:57:10 +0000 Received: by mail-oa0-f47.google.com with SMTP id i18so2486472oag.34 for ; Mon, 21 Oct 2013 13:57:04 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.250.200 with SMTP id ze8mr2871225obc.72.1382389024051; Mon, 21 Oct 2013 13:57:04 -0700 (PDT) Received: by 10.182.5.198 with HTTP; Mon, 21 Oct 2013 13:57:03 -0700 (PDT) In-Reply-To: <201310211947.59640.luke@dashjr.org> References: <791a727f-2188-4848-bd77-ea733c8c5c2c@me.com> <201310211947.59640.luke@dashjr.org> Date: Mon, 21 Oct 2013 22:57:03 +0200 Message-ID: From: Benjamin Cordes To: Luke-Jr Content-Type: multipart/alternative; boundary=089e0160c660b8577604e9468636 X-Spam-Score: -0.6 (/) 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 (benjamin.l.cordes[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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: 1VYMXF-0006kl-G0 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Revisiting the BIPS process, a proposal 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: Mon, 21 Oct 2013 20:57:10 -0000 --089e0160c660b8577604e9468636 Content-Type: text/plain; charset=ISO-8859-1 I believe a better solution would to use a gitlab clone such as gitlab, which sits on top of the git repo, and allows for custom code around the BIP process. Potentially one could even build Bitcoin into such a BIP system. If somebody wants to support a BIP he donates Bitcoins to that proposal. Somebody who actually implements the BIP can receive some percent of the bounty (while some percent goes to the Bitcoin foundation). Via such a platform one could create assurance contracts to kickstart BIP developments or Bitcoin extensions (public infrastructure which is not part of the core, such as opensourced exchanges). On Mon, Oct 21, 2013 at 9:47 PM, Luke-Jr wrote: > On Monday, October 21, 2013 7:38:37 PM Jean-Paul Kogelman wrote: > > 1) Should the protocol specification page also be codified into BIP(s)? > > Probably wouldn't hurt, but it'd likely need a rewrite in a more modular > and > formal form. > > > 2) Should the current wiki pages be taken down / forwarded to the git > repo > > or be auto updated from the git repo? > > Since it's the same format, I'd keep it up there, maybe with a link to the > git > repo on the main BIP index wiki page. > > > 3) Even though the information in BIP 50 is valuable, should it really be > > considered a BIP? > > It's a hardforking protocol change, so IMO yes. > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --089e0160c660b8577604e9468636 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I believe a better solution would to use a gitlab clone su= ch as gitlab, which sits on top of the git repo, and allows for custom code= around the BIP process. Potentially one could even build Bitcoin into such= a BIP system. If somebody wants to support a BIP he donates Bitcoins to th= at proposal. Somebody who actually implements the BIP can receive some perc= ent of the bounty (while some percent goes to the Bitcoin foundation). Via = such a platform one could create assurance contracts to kickstart BIP devel= opments or Bitcoin extensions (public infrastructure which is not part of t= he core, such as opensourced exchanges).


On Mon, Oct 2= 1, 2013 at 9:47 PM, Luke-Jr <luke@dashjr.org> wrote:
On Monday, October 21, 2013 7:38:37 PM Jean-Paul Kogelman= wrote:
> 1) Should the protocol specification page also be codified into BIP(s)= ?

Probably wouldn't hurt, but it'd likely need a rewrite in a m= ore modular and
formal form.

> 2) Should the current wiki pages be taken down / forwarded to the git = repo
> or be auto updated from the git repo?

Since it's the same format, I'd keep it up there, maybe with = a link to the git
repo on the main BIP index wiki page.

> 3) Even though the information in BIP 50 is valuable, should it really= be
> considered a BIP?

It's a hardforking protocol change, so IMO yes.

---------------------------------------------------------------------------= ---
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fr= om
the latest Intel processors and coprocessors. See abstracts and register &g= t;
http://pubads.g.doubleclick.ne= t/gampad/clk?id=3D60135991&iu=3D/4140/ostg.clktrk
___________________________________= ____________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--089e0160c660b8577604e9468636--