Hello,
I'm trying to create a bit of process around the
https://github.com/bitcoin/bips repository.
A) Currently a lot of pulls are open for various BIPs and it is not
clear who should comment on them, or who decides on changes to be
merged.
Currently all BIP changes have to go through the Bitco
These BIPs should go to Final state - they are implemented all over
the place, and are thus entirely fixed in place now. Any changes would
require a new BIP as amandment:
- BIP 14 (BIP Protocol Version and User Agent)
- BIP 21 (URI Scheme)
- BIP 22 (getblocktemplate - Fundamentals)
- BIP 31 (Po
On Wed, Oct 15, 2014 at 8:29 AM, Wladimir wrote:
> Hello,
>
> I'm trying to create a bit of process around the
> https://github.com/bitcoin/bips repository.
>
> A) Currently a lot of pulls are open for various BIPs and it is not
> clear who should comment on them, or who decides on changes to be
>
> This all makes a lot of sense to me, and would help a lot with the
> workflow. Unfortunately github pulls and issues really have nothing
> to faciltate a multistage workflow... e.g. where something can go
> through several steps.
Indeed, pull requests don't have a "status".
It would be possible
RE: process:
I like author == primary control, and an "assume they will do the right
thing, revert if they don't"
RE: separate mailing list for BIP discussion:
Great idea. Jeff Garzik was looking for a better mailing list solution than
SourceForge, but assuming
there isn't a clearly better solut
>
> Great idea. Jeff Garzik was looking for a better mailing list solution
> than SourceForge, but assuming
> there isn't a clearly better solution I think "we" should create a
> strictly moderated bitcoin-bips@lists.sourceforge list.
>
Let's stay away from SF.net or any mailman-controlled lists i
please not google groups *, I'd vote for sourceforge or other simple
open list software over google groups.
Adam
* Google lists are somehow a little proprietary or gmail lockin
focused eg it makes things extra hard to subscribe with a non-google
address if google has any hint that your address is
On Wed, Oct 15, 2014 at 04:54:57PM +0100, Adam Back wrote:
> please not google groups *, I'd vote for sourceforge or other simple
> open list software over google groups.
>
> Adam
>
> * Google lists are somehow a little proprietary or gmail lockin
> focused eg it makes things extra hard to subscr
I don't care much what exact list software/service is used, but lists.sf.net
hasn't changed in years and is basically dying. Trashing all @yahoo
accounts because ancient mailman does a MITM attack on people's email is no
good, it's not any better than a web proxy that breaks every SSL
connection. F
On Wed, Oct 15, 2014 at 4:54 PM, Adam Back wrote:
> please not google groups *, I'd vote for sourceforge or other simple
> open list software over google groups.
>
Please not sourceforge.
> * Google lists are somehow a little proprietary or gmail lockin
> focused eg it makes things extra hard
Sounds like this is what you're after, it's a fairly new feature:
https://github.com/blog/1375%0A-task-lists-in-gfm-issues-pulls-comments
I've been meaning to use it in a PR to try it out.
Cory
On Wed, Oct 15, 2014 at 5:36 AM, Wladimir wrote:
>> This all makes a lot of sense to me, and would he
On Wed, Oct 15, 2014 at 08:00:10PM +0100, Btc Drak wrote:
> > * Google lists are somehow a little proprietary or gmail lockin
> > focused eg it makes things extra hard to subscribe with a non-google
> > address if google has any hint that your address is associated with a
> > gmail account. Quite
On 10/15/14 08:47, Wladimir wrote:
> These BIPs should go to Final state - they are implemented all over
> the place, and are thus entirely fixed in place now. Any changes would
> require a new BIP as amandment:
>
> - BIP 14 (BIP Protocol Version and User Agent)
>
> - BIP 21 (URI Scheme)
ACK.
On Wednesday, October 15, 2014 8:47:18 AM Wladimir wrote:
> These BIPs should go to Final state - they are implemented all over
> the place, and are thus entirely fixed in place now. Any changes would
> require a new BIP as amandment:
>
> - BIP 14 (BIP Protocol Version and User Agent)
ACK
> - BI
On Wednesday, October 15, 2014 7:40:04 PM Peter Todd wrote:
> On Wed, Oct 15, 2014 at 08:00:10PM +0100, Btc Drak wrote:
> > > * Google lists are somehow a little proprietary or gmail lockin
> > > focused eg it makes things extra hard to subscribe with a non-google
> > > address if google has any hi
Hi all,
I've also been spending a few months coding upon the change's Pieter has
been making with the headersfirst8 pull request.
My code updates are also ready to test, and are available on github at
https://github.com/rebroad/bitcoin/ and the branch is
"sipa-headersfirst8-patches".
I've made
>
> Shouldn't we be doing this in a GitHub PR rather than spamming up the ML?
Not really. BIP changes should be discussed on the mailing list,
that's the way to get community consensus (as specified in BIP1).
Wladimir
--
On Thursday, October 16, 2014 6:22:04 AM Wladimir wrote:
> > Shouldn't we be doing this in a GitHub PR rather than spamming up the ML?
>
> Not really. BIP changes should be discussed on the mailing list,
> that's the way to get community consensus (as specified in BIP1).
>
> Wladimir
Discussion
18 matches
Mail list logo