Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org
	designates 209.85.212.181 as permitted sender)
	client-ip=209.85.212.181; envelope-from=drak@zikula.org;
	helo=mail-wi0-f181.google.com; 
MIME-Version: 1.0
In-Reply-To: <20140315172254.GA18318@savin>
References: <20140315134340.GA12937@savin>
	<CAJHLa0PDkOBHpwWPqy1HTwWRscSDQY2Vs8fmEghZAMTUzJtmMA@mail.gmail.com>
	<CANAnSg00ofpESqm4EoJ4gde5HpajLb2dukvK8yO80bK2AMwnAw@mail.gmail.com>
	<20140315172254.GA18318@savin>
From: Drak <drak@zikula.org>
Date: Sat, 15 Mar 2014 18:04:37 +0000
Message-ID: <CANAnSg0GYk3fRoj-7FZsoWGUw3+2drwaOKWC1UgywfFAgi6gGA@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=f46d0434c0b83512f704f4a9063c
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Andy Weidenbaum <archbaum@gmail.com>, Alex Mizrahi <alex.mizrahi@gmail.com>
Subject: Re: [Bitcoin-development] python-bitcoinlib v0.1 release - a
 low-level Python2/3 interface to the Bitcoin protocol
Precedence: list

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

Yes. I think the problem is your fork has been under more development and
upstream has stalled. The problem with this is it becomes unclear which
repo is the main one as it really has become a fork and of course then
development really does fork properly which is a shame because it doesn't
nurture community contributions around the project which is really
important.

Drak


On 15 March 2014 17:22, Peter Todd <pete@petertodd.org> wrote:

> On Sat, Mar 15, 2014 at 05:12:42PM +0000, Drak wrote:
> > Would it make sense to pull that stuff in and add Peter with commit
> access
> > since your repo is top of the fork tree.
>
> I've noticed it looks like people actually using my 'pythonize' code
> have been linking directly to my tree in things like documentation and
> build scripts, so the URL is probably not a problem.
>
> I did open a pull-req on the bitcoin.org repo to change that URL
> however: https://github.com/bitcoin/bitcoin.org/pull/346
>
> --
> 'peter'[:-1]@petertodd.org
> 0000000000000000ef4a047ecc7077b7855626b9c9bf07e528e0c6ace2da30a8
>

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

<div dir=3D"ltr">Yes. I think the problem is your fork has been under more =
development and upstream has stalled. The problem with this is it becomes u=
nclear which repo is the main one as it really has become a fork and of cou=
rse then development really does fork properly which is a shame because it =
doesn&#39;t nurture community contributions around the project which is rea=
lly important.<div>

<br></div><div>Drak<br><div><div><br></div></div></div></div><div class=3D"=
gmail_extra"><br><br><div class=3D"gmail_quote">On 15 March 2014 17:22, Pet=
er Todd <span dir=3D"ltr">&lt;<a href=3D"mailto:pete@petertodd.org" target=
=3D"_blank">pete@petertodd.org</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"><div class=3D"">On Sat, Mar 15, 2014 at 05:1=
2:42PM +0000, Drak wrote:<br>
&gt; Would it make sense to pull that stuff in and add Peter with commit ac=
cess<br>
&gt; since your repo is top of the fork tree.<br>
<br>
</div>I&#39;ve noticed it looks like people actually using my &#39;pythoniz=
e&#39; code<br>
have been linking directly to my tree in things like documentation and<br>
build scripts, so the URL is probably not a problem.<br>
<br>
I did open a pull-req on the <a href=3D"http://bitcoin.org" target=3D"_blan=
k">bitcoin.org</a> repo to change that URL<br>
however: <a href=3D"https://github.com/bitcoin/bitcoin.org/pull/346" target=
=3D"_blank">https://github.com/bitcoin/bitcoin.org/pull/346</a><br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
&#39;peter&#39;[:-1]@<a href=3D"http://petertodd.org" target=3D"_blank">pet=
ertodd.org</a><br>
0000000000000000ef4a047ecc7077b7855626b9c9bf07e528e0c6ace2da30a8<br>
</font></span></blockquote></div><br></div>

--f46d0434c0b83512f704f4a9063c--