From: Bryan Bishop <kanzure@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>,
Bryan Bishop <kanzure@gmail•com>
Subject: [bitcoin-dev] Fwd: [Lightning-dev] Lightning Developers Biweekly Meeting Announce
Date: Wed, 12 Jul 2017 20:38:24 -0500 [thread overview]
Message-ID: <CABaSBazG2HBiGoNf4JPWwzTssku6x5+D7nsXH=zTu3r6HXy6dQ@mail.gmail.com> (raw)
In-Reply-To: <87mv898cdz.fsf@rustcorp.com.au>
---------- Forwarded message ----------
From: Rusty Russell <rusty@blockstream•com>
Date: Wed, Jul 12, 2017 at 6:27 PM
Subject: [Lightning-dev] Lightning Developers Biweekly Meeting Announce
To: lightning-dev@lists•linuxfoundation.org
Hi all!
Every two weeks we've been running an informal Google Hangout
for implementers of the Lightning spec; as the spec is starting to
freeze, we've decided to formalize it a bit which means opening access
to a wider audience.
The call is at 20:00 UTC every two weeks on Monday: next call is
on the 24th July. We'll be using #lightning-dev on freenode's IRC
servers to communicate as well: if you're working on the Lightning
protocol and want to attend, please send me a ping and I'll add you to
the invite.
I'll produce an agenda (basically a list of outstanding PRs on
github) and minutes each week: I'll post the latter to the ML here.
The last one can be found:
https://docs.google.com/document/d/1EbMxe_QZhpHo67eeiYHbJ-BvNKU1WhFd5WhJFeD9-DI/edit?usp=sharing
The routine with the spec itself is that from now on all
non-spelling/typo changes will require a vote with no objections from
call participants, or any devs unable to make it can veto or defer by
emailing me in writing before the meeting.
Cheers!
Rusty.
_______________________________________________
Lightning-dev mailing list
Lightning-dev@lists•linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
--
- Bryan
http://heybryan.org/
1 512 203 0507
parent reply other threads:[~2017-07-13 1:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87mv898cdz.fsf@rustcorp.com.au>]
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='CABaSBazG2HBiGoNf4JPWwzTssku6x5+D7nsXH=zTu3r6HXy6dQ@mail.gmail.com' \
--to=kanzure@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