public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Warren Togami Jr." <wtogami@gmail•com>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: Move Bitcoin Dev List to a Neutral Competent Entity
Date: Tue, 16 Jun 2015 14:19:04 -1000	[thread overview]
Message-ID: <CAEz79PphLdxOSVrL0r45mYF+XLFzWwB=-KAT-rb=GLb+tMp6+w@mail.gmail.com> (raw)
In-Reply-To: <CAEz79PrjoD3fvwqmr2+O+8myeQCV_4ZuX4q9zCkQdN=i=ovuMA@mail.gmail.com>

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

On Sun, Jun 14, 2015 at 5:19 PM, Warren Togami Jr. <wtogami@gmail•com>
wrote:

>
> *List Name?*  Would people prefer "bitcoin-development" for he new list
> name instead of a shorter name like "bitcoin-dev"?  I personally like the
> shorter name, but either is fine.
> https://lists.linuxfoundation.org/mailman/listinfo currently has
> "sidechains-dev", and "lightning-dev" is moving there sometime soon.
>

We're going ahead with "bitcoin-dev".  A request for creation is now
pending.


>
> *Proposed Cut-Off Date?*  Then we also need to agree on a date to cut off
> the old list.  Their sysadmin said we could have the new list auto-post
> from the old list for a short while.  I wonder how well that works ... if
> that will result in double posting if people write to the new and CC the
> old list.  Needs a little research how well it would behave to have both
> lists operating during a transition period.  I think we should announce a
> cut-off date when posts to the old list is shut off, July 15th, one month
> from now.  Thoughts?
>

Off-list I heard a suggestion to make the cut-off date as short as one week
after the new list is announced and people are given the option to
subscribe.  Could people please post feelings about this?

It seems most everyone agreed not to auto-subscribe everyone onto the new
list as that tends to be upsetting.

There is clarity if subscribing the old list to the new list is a good
idea.  Is anyone familiar with Mailman, is it smart enough to somehow
prevent double-posts if someone writes to both the old and new address?

Warren Togami

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

  parent reply	other threads:[~2015-06-17  0:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 10:12 Warren Togami Jr.
2015-06-14 15:15 ` Jeff Garzik
2015-06-14 16:56   ` Peter Todd
2015-06-15  3:19   ` Warren Togami Jr.
2015-06-15  5:50     ` Andy Schroder
2015-06-15  9:13     ` odinn
2015-06-17  0:19     ` Warren Togami Jr. [this message]
2015-06-17  1:59       ` grarpamp
2015-06-14 20:55 ` Andy Schroder
2015-06-14 21:59   ` Adam Back
2015-06-14 22:14     ` Davide Cavion
2015-06-14 21:54 ` odinn
2015-06-14 22:38 ` Gregory Maxwell
2015-06-15 10:13 ` Mike Hearn
2015-06-15 19:45   ` Adam Weiss
2015-06-15 20:50     ` Pieter Wuille

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='CAEz79PphLdxOSVrL0r45mYF+XLFzWwB=-KAT-rb=GLb+tMp6+w@mail.gmail.com' \
    --to=wtogami@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=jgarzik@bitpay$(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