public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Stadulis <dstadulis@gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] 2015-09-24 #bitcoin-dev Weekly Development Meeting Minutes
Date: Thu, 24 Sep 2015 17:29:02 -0700	[thread overview]
Message-ID: <CAHpxFbGa_4VRDyQJJYVXScWdg6KQOJnb-XdZ30NAvFbouhLHrQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2171 bytes --]

If you weren't able to attend the first, weekly development meeting, the
following are the minutes:

Meeting Title:

#bitcoin-dev Weekly Development Meeting

Meeting Date:

2015-09-24

Meeting Time:

19:00-20:00 UTC

Participants in Attendance:

luke-jr

CodeShark

sipa

morcos

sdaftuar

dstadulis

jtimon

wumpus

jgarzik

kanzure

gmaxwell

cfields

gavinandresen

IRC Chat Logs:

http://bitcoinstats.com/irc/bitcoin-dev/logs/2015/09/24#l1443121200.0

------------------------------

Topics Discussed:


   1.

   libconsensus and refactoring
   2.

   All goals for 0.12 release
   1.

      libsecp256k1 is ready for 0.12?
      1.

         libsecp256k1 needs a native OSX travis build
         1.

            cfields has work that moves to the new Travis infrastructure
            2.

            PROPOSAL: propose libsecp256k1 validation PR as soon as all
            currently-in-pipeline API changes are merged
            2.

      OP_CHECKSEQUENCEVERIFY
      3.

      mempool limiting
      4.

      version bits
      3.

   BIP process
   4.

   Split off script base classes/execution for use in consensus?
   5.

   Current/near-term “what are you working on”
   1.

      versionbits: Codeshark has been working on an implementation
      2.

      gavinandresen: simple benchmarking framework then plan on optimizing
      new block relay/broadcast.

------------------------------

Meeting Conclusions:

Mempool limiting discussion will be delayed until 2015-10-1 meeting

#

Action items

Responsible Parties

ETA

1

Please review 6557 (starting Saturday), 6673 and any other mempool pulls
for concept

Everyone

Next Thurs. meeting (2015-10-01)

2

libsecp256k1 needs a native OSX travis build


3

Propose libsecp256k1 validation PR as soon as all currently-in-pipeline API
changes are merged


4

Review BIP 68, review #6312, #6564


5

versionbits BIP number assignment

gmaxwell

2015-09-25

Google Doc:
https://docs.google.com/document/d/1zsWVaf5H9ECrN1zPutMdD_2ky3fnhQUM411NDrRrc-M/edit

[-- Attachment #2: Type: text/html, Size: 21786 bytes --]

             reply	other threads:[~2015-09-25  0:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25  0:29 Daniel Stadulis [this message]
2015-09-28 18:26 ` [bitcoin-dev] 2015-09-24 #bitcoin-dev Weekly Development Meeting Minutes Wladimir J. van der Laan

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=CAHpxFbGa_4VRDyQJJYVXScWdg6KQOJnb-XdZ30NAvFbouhLHrQ@mail.gmail.com \
    --to=dstadulis@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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