From: Cory Fields <lists@coryfields•com>
To: Simon Selitsky <simon@coingyft•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Weekly IRC Meeting Time Poll
Date: Wed, 11 Jul 2018 18:15:19 -0400 [thread overview]
Message-ID: <CAApLimhA7qUXDhm4jUh5u53=w-Zs_6uOHdd9m74wjDJc8P7rVg@mail.gmail.com> (raw)
In-Reply-To: <9E231A5B-5053-4870-9D2A-22D4798003F0@coingyft.com>
Hi Simon
The poll is intended for regular Bitcoin Core contributors, who meet
once a week to discuss what they're working on. It is a mundane
software meeting, unrelated to the research and discussion of Bitcoin
itself. The meetings are open to all, but it makes sense to constrain
scheduling decisions to the current active contributors. If you'd like
to attend but are unable, meeting transcripts are always made
available online afterwards.
Please see the Contributing doc [0] if you're interested in becoming a
regular contributor to Bitcoin Core :)
Regards,
Cory
0: https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md
On Tue, Jul 10, 2018 at 7:17 PM, Simon Selitsky <simon@coingyft•com> wrote:
> Cory,
>
> Please send me a link to vote.
>
> Thanks !
>
>> On Jul 10, 2018, at 4:24 PM, Cory Fields via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>>
>> Hi all
>>
>> This is a bit offtopic for bitcoin-dev, but I'm sending here since
>> many core devs are subscribed.
>>
>> As discussed in last week's meeting, it would be helpful to have an
>> idea of what times devs are generally available to meet online. With
>> better data, we could potentially reschedule the weekly IRC meetings
>> to a time that would exclude fewer people.
>>
>> I've thrown together a quick poll, please watch for a mail from
>> civs@cs•cornell.edu and follow the link to vote. To keep it simple,
>> the day of the week (Thursday) is fixed for now.
>>
>> The initial list of voters is based on previous meeting participation.
>> If you regularly attend the weekly meetings (or can't now but may be
>> able to attend at a different time), but do not receive a link to vote
>> in the next hour, please reply here or ping me on IRC so that I may
>> add you.
>>
>> Polling will conclude at the end of the scheduled IRC meeting on July 19.
>>
>> Regards,
>> Cory
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
prev parent reply other threads:[~2018-07-11 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 20:24 Cory Fields
2018-07-10 23:17 ` Simon Selitsky
2018-07-11 1:35 ` mark M
2018-07-11 22:15 ` Cory Fields [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='CAApLimhA7qUXDhm4jUh5u53=w-Zs_6uOHdd9m74wjDJc8P7rVg@mail.gmail.com' \
--to=lists@coryfields$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=simon@coingyft$(echo .)com \
/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