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: Sun, 14 Jun 2015 17:19:09 -1000	[thread overview]
Message-ID: <CAEz79PrjoD3fvwqmr2+O+8myeQCV_4ZuX4q9zCkQdN=i=ovuMA@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0OOnYMuA-8qfHafw5D0zGw_U06PZaAKS2j=Av_KUhgt-A@mail.gmail.com>

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

On Sun, Jun 14, 2015 at 5:15 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:

> * ACK on moving away from SourceForge mailing lists - though only once a
> community-welcomed replacement is up and running
>
> * ACK on using LF as a mailing infrastructure provider
>
> * Research secure mailing list models, for bitcoin-security.  The list is
> not ultra high security - we all use PGP for that - but it would perhaps be
> nice to find some spiffy cryptosystem where mailing list participants
> individually hold keys & therefore access.
>
>
While I agree this is a good idea, this should not be a precondition for
moving the public bitcoin-dev list.  The security team needs to separately
research/write tools needed for this.

<jgarzik> warren, wanna just go ahead and create bitcoin-development @ LF?


*More Feedback?*  As for going ahead, perhaps we should wait to hear from
more of the other technical leaders?

*More Questions*

*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.

*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?

*Moderators?*  Mailman on the new server allows having separate logins for
admins and moderators.  I think the admins of the old SF project are gavin,
jgarzik and sipa... they are kind of busy.  Perhaps we should identify
known trusted community members who can help with moderation.  Usually this
is dealing with "held" messages that are flagged by the spam filter

Warren Togami

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

  parent reply	other threads:[~2015-06-15  3:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 10:12 [Bitcoin-development] Proposal: Move Bitcoin Dev List to a Neutral Competent Entity 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. [this message]
2015-06-15  5:50     ` Andy Schroder
2015-06-15  9:13     ` odinn
2015-06-17  0:19     ` Warren Togami Jr.
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='CAEz79PrjoD3fvwqmr2+O+8myeQCV_4ZuX4q9zCkQdN=i=ovuMA@mail.gmail.com' \
    --to=wtogami@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@bitpay.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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