Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.172 as permitted sender)
	client-ip=209.85.217.172; envelope-from=melvincarvalho@gmail.com;
	helo=mail-lb0-f172.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAM_a8Jwo_7NJJoaKYUYo6T7U8AsDfT5=MZSXjmdYU4330OHNmw@mail.gmail.com>
References: <CAM_a8Jwo_7NJJoaKYUYo6T7U8AsDfT5=MZSXjmdYU4330OHNmw@mail.gmail.com>
Date: Sat, 25 May 2013 10:25:35 +0200
Message-ID: <CAKaEYhKOmSc+Mz=vA-M=34aXOs=VfC0jvCP+qNSdjE_2WVUfkg@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Zooko Wilcox-OHearn <zooko@leastauthority.com>
Content-Type: multipart/alternative; boundary=089e01419b06dd145204dd86a8af
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] (no subject)
Precedence: list

--089e01419b06dd145204dd86a8af
Content-Type: text/plain; charset=ISO-8859-1

On 25 May 2013 07:46, Zooko Wilcox-OHearn <zooko@leastauthority.com> wrote:

> jgarzik wrote:
>  > 1) Rule changes.  We don't want these.
>
> In general? What constitutes a rule change?
>
> For example, if I understand correctly (from what Gavin said at
> Bitcoin 2013), there is a move afoot to lift the block size limit.
> Although, when I went to confirm my understanding by reading the
> bitcoin-development list archives, I don't see mention of this. Is
> there another forum I should be reading if I want to follow Bitcoin
> development?
>
> Anyway, I hope that there are some rule changes that you would
> consider for Bitcoin, although I recognize there are vast classes of
> such changes that you wouldn't.
>
> I'm trying to figure out what's the most productive way to show you,
> and everyone, candidates for such changes. Things that are definitely
> not suitable for merging to trunk tomorrow, but might be suitable in a
> year or two, or "Next Time We Have A Hardfork".
>
> I don't think alternative bitcoin-clones are the best venue for those.
> Although they are certainly good venues for changes which can never
> make it into Bitcoin.
>
> Perhaps the best venue for such a thing is just to fork bitcoin.git on
> github.
>

It might be an idea to have 'rule change' fixes and 'bug fix' releases go
out separately


>
> Regards,
>
> Zooko Wilcox-O'Hearn
>
> Founder, CEO, and Customer Support Rep
>
> https://LeastAuthority.com
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--089e01419b06dd145204dd86a8af
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 25 May 2013 07:46, Zooko Wilcox-OHearn <span dir=3D"ltr">&lt;<a =
href=3D"mailto:zooko@leastauthority.com" target=3D"_blank">zooko@leastautho=
rity.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">jgarzik wrote:<br>
=A0&gt; 1) Rule changes. =A0We don&#39;t want these.<br>
<br>
In general? What constitutes a rule change?<br>
<br>
For example, if I understand correctly (from what Gavin said at<br>
Bitcoin 2013), there is a move afoot to lift the block size limit.<br>
Although, when I went to confirm my understanding by reading the<br>
bitcoin-development list archives, I don&#39;t see mention of this. Is<br>
there another forum I should be reading if I want to follow Bitcoin<br>
development?<br>
<br>
Anyway, I hope that there are some rule changes that you would<br>
consider for Bitcoin, although I recognize there are vast classes of<br>
such changes that you wouldn&#39;t.<br>
<br>
I&#39;m trying to figure out what&#39;s the most productive way to show you=
,<br>
and everyone, candidates for such changes. Things that are definitely<br>
not suitable for merging to trunk tomorrow, but might be suitable in a<br>
year or two, or &quot;Next Time We Have A Hardfork&quot;.<br>
<br>
I don&#39;t think alternative bitcoin-clones are the best venue for those.<=
br>
Although they are certainly good venues for changes which can never<br>
make it into Bitcoin.<br>
<br>
Perhaps the best venue for such a thing is just to fork bitcoin.git on gith=
ub.<br></blockquote><div><br></div><div>It might be an idea to have &#39;ru=
le change&#39; fixes and &#39;bug fix&#39; releases go out separately<br>
</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Regards,<br>
<br>
Zooko Wilcox-O&#39;Hearn<br>
<br>
Founder, CEO, and Customer Support Rep<br>
<br>
<a href=3D"https://LeastAuthority.com" target=3D"_blank">https://LeastAutho=
rity.com</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
Try New Relic Now &amp; We&#39;ll Send You this Cool Shirt<br>
New Relic is the only SaaS-based application performance monitoring service=
<br>
that delivers powerful full stack analytics. Optimize and monitor your<br>
browser, app, &amp; servers with just a few lines of code. Try New Relic<br=
>
and get this awesome Nerd Life shirt! <a href=3D"http://p.sf.net/sfu/newrel=
ic_d2d_may" target=3D"_blank">http://p.sf.net/sfu/newrelic_d2d_may</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div></div>

--089e01419b06dd145204dd86a8af--