public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] IRC meeting agenda, 18:00 UTC Thursday
Date: Tue, 6 Nov 2012 19:13:33 +0000	[thread overview]
Message-ID: <201211061913.35016.luke@dashjr.org> (raw)
In-Reply-To: <CABsx9T1K+XKr=OT5TC4d1KiQ_kXH+giCWHPiS=t7-NyVOmGTDw@mail.gmail.com>

On Tuesday, November 06, 2012 6:47:34 PM Gavin Andresen wrote:
> Thursdays at 18:00 UTC (6PM Europe/1PM east US/10AM west US) seem to
> be a good time for the core dev team to meet on the #bitcoin-dev
> freenode IRC channel to chat.
> 
> I'd like to talk about:
> 
> o Can we put together a TODO list to get to a 0.8 release candidate ?
> 
> o Is it time to feature-freeze 0.8 and work on just testing the new
> features and fixing existing bugs (the issues list keeps getting
> longer and longer ... )?

Not much has changed besides internal workings, right?
Though perhaps that's still significant enough for 0.8.

> o BIP process: are we happy with how it is working? What can we do to
> improve it?

Amir seems to be more and more absent these days, so it might be nice to setup 
a successor failsafe in the event that he cannot be reached. It would be a 
shame for the BIP process to fall apart merely because we can't get numbers 
assigned.

But more important to the success of BIP today, I think, is encouraging wider 
community participation. The stratum mining mess seems to be a direct result 
of lack of participation in the GBT BIP process (resulting in it not being as 
ideal as some pools desire) and lack of any peer review/contribution toward 
the stratum protocol. What can we do to increase awareness of BIP and 
encourage more collaboration?

Luke



  reply	other threads:[~2012-11-06 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-06 18:47 [Bitcoin-development] IRC meeting agenda, 18:00 UTC Thursday Gavin Andresen
2012-11-06 19:13 ` Luke-Jr [this message]
2012-11-06 19:56   ` slush
2012-11-06 22:12     ` Luke-Jr
2012-11-07 19:37 ` Pieter Wuille
2012-11-08  9:19   ` Mike Hearn
2012-11-08 12:56     ` Pieter Wuille
2012-11-08 13:07     ` Gregory Maxwell
     [not found]     ` <CA+s+GJDVLLv8troMfeyWoOwM3EH4GHYtd=bzUgmg_ZegVT6kXw@mail.gmail.com>
2012-11-08 13:10       ` [Bitcoin-development] Fwd: " Wladimir

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201211061913.35016.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox