>
>
> • I propose that BIPs be wiki pages, with a social convention that the
> Author gets final word if any editing wars break out.
ACK
>
• If he's willing, I propose that Amir take the role of BIP editor.
>
> ACK
> • I think bitcoin is still too small to have a specialized
> "bitcoin-ideas"
I think what Jeff has said is ideal for a stable 1.0 or 1.1 release of
a kernal. I also think it's absolutely the direction we should be
heading in, but not this afternoon. The desire to keep a 0.4.x stable
branch is a symptom of a bigger QA problem, one that I am attempting
to address in general.
> We need to avoid a user/contributor experience of: "my pull request
> was abruptly closed with no warning"
I agree, I definitely want to go about this in a non-jerk way. I would
be pissed if I spent hours coding something, and it was put on the
back burner and eventually closed (especially with
I would like to propose adding timers to the pulls / issues:
https://github.com/bitcoin/bitcoin/pull/523
"From time to time a pull request will become outdated. If this occurs, and
the pull is no longer automatically mergeable; it will be closed after 15
days. This can be avoided by rebasing the
I'm sorry that I misunderstood the protocol being separate from the
client in regard to 'BEPS'. It definitely makes more sense that way.
As far as naming; I vote BER pronounced Beer.
On Mon, Sep 19, 2011 at 12:57 PM, Gavin Andresen
wrote:
> New 'standard' transaction forms would be perfect cand
http://www.python.org/dev/peps/ is a good reference if you're
interested in seeing how PEPs work in action. I would be more than
willing to maintain a similar index if that's what people want.
Something to note is that Python does not use Git or GitHub (AFAIK).
So we would need to update 001 to re
On Wed, Sep 14, 2011 at 4:28 PM, Gavin Andresen wrote:
> What do other people think? I think it is too high risk for too
> little benefit and shouldn't be done until we have a really compelling
> reason to introduce a forking change.
Could we bundle this and potential future blockchain-splittin
Can you please submit a pull request and testing plan? If these already
exist, can you please link them here?
I'm exciting to get this in, as it will close the wx issues. (and hopefully
not bring on too many qt issues)
Thanks,
Alex
-
I expect that I will make a lot of mistakes, and probably ask too many
questions - but I hope you can bear with me.
I've been trying to keep a low profile as I get better acquainted with the
project. I'm clearly in the company of some very smart people - and would
like to keep it that way.
I've t
https://github.com/bitcoin/bitcoin/pull/506 has been closed pending
additional commits or a change in consensus.
--
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented m
response to https://github.com/alexwaters/bitcoin/issues/2
This is not a requirement for pull requests, but will help process the
important/easy ones a lot faster. I would love to discuss other ways of
prioritizing pull requests, but this seems like it can get the job done for
the time-being.
-Alex
11 matches
Mail list logo