From: Jeremy Rubin <jeremy.l.rubin@gmail•com>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] CTV Meeting #7 Reminder + Agenda (Tuesday, April 19th, 12:00 PT / 7PM UTC)
Date: Mon, 18 Apr 2022 21:13:09 -0700 [thread overview]
Message-ID: <CAD5xwhhRHChEvV-0pfL9E5Sd1NYVQBzEywLwn3KvoWvgT9Vehw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
Devs,
Apologies for the delay in posting the reminder. As noted on March 22nd,
the 7th meeting was postponed to the time of the 8th meeting given the
Miami conference scheduling conflicts.
We'll hold the meeting tomorrow at noon Pacific time as usual.
The Agenda for the meeting will be an open discussion on the possibility of
activating CTV in 2022, why we may or may not wish to do that, if we did
want to do that what would need to be done, what the path might look like
if we do not do that.
I will try to publish some written thoughts ahead of the meeting for
reference.
If you are unable to attend, you may leave a comment in response below and
I will reference it in the minutes of the meeting.
Best,
Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
[-- Attachment #2: Type: text/html, Size: 2602 bytes --]
reply other threads:[~2022-04-19 4:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAD5xwhhRHChEvV-0pfL9E5Sd1NYVQBzEywLwn3KvoWvgT9Vehw@mail.gmail.com \
--to=jeremy.l.rubin@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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