Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.47 as permitted sender)
	client-ip=209.85.215.47; envelope-from=laanwj@gmail.com;
	helo=mail-la0-f47.google.com; 
MIME-Version: 1.0
In-Reply-To: <CA+s+GJDVLLv8troMfeyWoOwM3EH4GHYtd=bzUgmg_ZegVT6kXw@mail.gmail.com>
References: <CABsx9T1K+XKr=OT5TC4d1KiQ_kXH+giCWHPiS=t7-NyVOmGTDw@mail.gmail.com>
	<CAPg+sBisYEMWzS5JNXAoB5EeHc=YboOJqsktEqON1dY6Lo2SsA@mail.gmail.com>
	<CANEZrP0LUv69wYwg_6ivPc=mFiGEYKomaJXmmT2Zm14bKik0bQ@mail.gmail.com>
	<CA+s+GJDVLLv8troMfeyWoOwM3EH4GHYtd=bzUgmg_ZegVT6kXw@mail.gmail.com>
Date: Thu, 8 Nov 2012 14:10:45 +0100
Message-ID: <CA+s+GJCNR503KwyWgfFCAz=LWAShE7+T63mAi_2SqMn+7Fmjhg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=f46d0408386b221dfd04cdfb90e7
Subject: [Bitcoin-development] Fwd:  IRC meeting agenda, 18:00 UTC Thursday
Precedence: list

--f46d0408386b221dfd04cdfb90e7
Content-Type: text/plain; charset=UTF-8

On Thu, Nov 8, 2012 at 10:19 AM, Mike Hearn <mike@plan99.net> wrote:

> I won't be able to make it this time.  My feeling is IRC is a good place
> to bounce ideas around when time and people happen to be available, but
> having meetings there will inevitably lead to decision making that's better
> done in a slower manner via email.


Well I think regularly scheduled IRC meetings are a good idea, as for some
smaller decisions quick brainstorming tends to work better than long e-mail
threads.

But indeed big and important decisions should be posted on the mailing list
too.


> Comments:
>
>    BIP process: are we happy with how it is working? What can we do to improve
> it?
>
> Needing some kind of process to allocate a number is over the top. I
> skipped this for the bloom filtering BIP. We should take off the part of
> the {{BIP}} template that says "don't just pick a number and add a bip" -
> that's exactly what people should do. I'm not sure there's any need for an
> editing role either.
>

Agreed in that we don't need a "number allocation king". But some rules for
the numbering can be good to keep sanity. What about very simply "everyone
that wants to create a BIP picks the next available number and reserves
that page on the Wiki?".


>
>     Is it time to feature-freeze 0.8
>
> I'd like more time to get the bloom filtering work in. It'll be easier to
> promote the 0.8 release if we can sell it as "important
> scalability/performance improvement for the network, upgrade to help
> Bitcoin keep growing", as whilst there's no real auto update or organized
> people who religiously update promotion is very important. I think
> ultraprune + bloom filtering is the two major scalability improvements we
> have right now.
>

I'm not sure about a full feature freeze. I agree it could be wise not do
any more changes of the scale of ultraprune before 0.9, to give some
stability to fix the kinks in the current version.

Wladimir

--f46d0408386b221dfd04cdfb90e7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote"><div class=3D"im">On Thu, Nov 8, 2012 at 10:19 AM, Mike Hearn <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:mike@plan99.net" target=3D"_blank">mik=
e@plan99.net</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">
I won&#39;t be able to make it this time. =C2=A0My feeling is IRC is a good=
 place to bounce ideas around when time and people happen to be available, =
but having meetings there will inevitably lead to decision making that&#39;=
s better done in a slower manner via email.</blockquote>

<div><br></div></div><div>Well I think regularly scheduled IRC meetings are=
 a good idea, as for some smaller decisions quick brainstorming tends to wo=
rk better than long e-mail threads.</div><div><br></div><div>But indeed big=
 and important decisions should be posted on the mailing list too.</div>
<div class=3D"im">
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div>Comments:</div><div><d=
iv><br></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x">=C2=A0 =C2=A0BIP process: are we happy with how it is working? What can =
we do to=C2=A0</span><span style=3D"font-family:arial,sans-serif;font-size:=
13px">improve it?</span><br style=3D"font-family:arial,sans-serif;font-size=
:13px">


</div><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div></div><div><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">Needing some kind of process to allocate a number is over the top.=
 I skipped this for the bloom filtering BIP. We should take off the part of=
 the {{BIP}} template that says &quot;don&#39;t just pick a number and add =
a bip&quot; - that&#39;s exactly what people should do. I&#39;m not sure th=
ere&#39;s any need for an editing role either.</span></div>

</blockquote><div><br></div></div><div>Agreed in that we don&#39;t need a &=
quot;number allocation king&quot;. But some rules for the numbering can be =
good to keep sanity. What about very simply &quot;everyone that wants to cr=
eate a BIP picks the next available number and reserves that page on the Wi=
ki?&quot;.</div>
<div class=3D"im">
<div>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">=C2=
=A0 =C2=A0</span><span style=3D"font-family:arial,sans-serif;font-size:13px=
">=C2=A0</span><span style=3D"font-family:arial,sans-serif;font-size:13px">=
Is it time to feature-freeze 0.8</span></div>


<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x">I&#39;d like more time to get the bloom filtering work in. It&#39;ll be =
easier to promote the 0.8 release if we can sell it as &quot;important scal=
ability/performance improvement for the network, upgrade to help Bitcoin ke=
ep growing&quot;, as whilst there&#39;s no real auto update or organized pe=
ople who religiously update promotion is very important. I think ultraprune=
 + bloom filtering is the two major scalability improvements we have right =
now.</span></div>

</blockquote><div><br></div></div><div>I&#39;m not sure about a full featur=
e freeze. I agree it could be wise not do any more changes of the scale of =
ultraprune before 0.9, to give some stability to fix the kinks in the curre=
nt version.=C2=A0</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div><div>Wladimir<br></div><div><br></div></font></span></div></=
div>
</div><br>

--f46d0408386b221dfd04cdfb90e7--