public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Heritage Samuel Falodun <herrytheeagle@gmail•com>
To: Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>, Jeremy <jlrubin@mit•edu>
Subject: Re: [bitcoin-dev] BIP-119 Deployment and Review Workshops
Date: Fri, 31 Dec 2021 17:56:17 +0100	[thread overview]
Message-ID: <CAKrV5kCJ=LEjSzMnpf_uCJ8oTfeo-4e-ugBBBJkXkSVd3DEvgw@mail.gmail.com> (raw)
In-Reply-To: <CAD5xwhjdpmOSdsGZALBq5UZKdG+cu7+-e+4UB8+NpMenrxcR8Q@mail.gmail.com>

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

Okay Jeremy, I plan to attend.

On Thu, Dec 30, 2021 at 9:29 PM Jeremy via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> Dear Bitcoin Developers,
>
> I've selected a time (every 2 weeks on Tuesday 12:00 PM PT starting
> January 11th in Liber ##ctv-bip-review) to host a recurring meeting to
> discuss BIP-119 review and deployment topics.
>
> Before the meeting, please send me any topics you would like to cover & I
> will circulate a preliminary agenda incorporating feedback in advance of
> the meeting.
>
> The rough plan will be to coordinate review, testing, and iron out any
> wrinkles around release timelines and procedures based on my request for
> comment here https://rubin.io/bitcoin/2021/12/24/advent-27/. Meetings
> will be moderated tightly to remain on topic, but all relevant topics will
> be welcome (similar to how I moderated the meetings I hosted for Taproot).
>
> Participation in these meetings does not signify any sort of endorsement
> of BIP-119's inclusion, nor a specific roadmap, but rather to carry on the
> 'gradient descent process' of consensus in an open, interactive, and
> productive format. Logs will be available via gnusha.
>
> Happy New Year,
>
> Jeremy
>
> p.s. If you plan to attend feel free to drop me a private note / reply
> here, otherwise I may ping you to ask if you can attend.
>
> --
> @JeremyRubin <https://twitter.com/JeremyRubin>
> <https://twitter.com/JeremyRubin>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-- 
Heritage Samuel Falodun

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

      reply	other threads:[~2021-12-31 16:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 20:28 Jeremy
2021-12-31 16:56 ` Heritage Samuel Falodun [this message]

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='CAKrV5kCJ=LEjSzMnpf_uCJ8oTfeo-4e-ugBBBJkXkSVd3DEvgw@mail.gmail.com' \
    --to=herrytheeagle@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=jlrubin@mit$(echo .)edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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