public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: odinn <odinn.cyberguerrilla@riseup•net>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Proposal: Move Bitcoin Dev List to a Neutral Competent Entity
Date: Mon, 15 Jun 2015 02:13:03 -0700	[thread overview]
Message-ID: <557E971F.3010908@riseup.net> (raw)
In-Reply-To: <CAEz79PrjoD3fvwqmr2+O+8myeQCV_4ZuX4q9zCkQdN=i=ovuMA@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What about Gittorrent?

http://blog.printf.net/articles/2015/05/29/announcing-gittorrent-a-decen
tralized-github/

On 06/14/2015 08:19 PM, Warren Togami Jr. wrote:
> On Sun, Jun 14, 2015 at 5:15 AM, Jeff Garzik <jgarzik@bitpay•com 
> <mailto: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
> 
> 
> ----------------------------------------------------------------------
- --------
>
> 
> 
> 
> _______________________________________________ Bitcoin-development
> mailing list Bitcoin-development@lists•sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> 

- -- 
http://abis.io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
https://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVfpcfAAoJEGxwq/inSG8CEdsH+weboFo8SCbwgoe68oZLl6Et
r4JtzZRu8jtw5x6AYcpVMBvUo3CHtbYCWREidBhvSU+TlOUjnxZRU5CjLpjHcc61
QV2hIGD1RUdrcj93PBsnNrvuXkLVHd09sKXCIvldY1d1GqTqy9sVY1skExd7zY2h
LmJhLdmNw7I+gLP/r8Ivl7aDqrpzHXr7pnbFXZZ0hxhthncxXTefi/IV+kAt3ptL
qfSRYGPyyUXWLfXF/XW+/DH+scZm+Iu/SSoSa6xnEo4MgY4HzZM2Uy+9Te9aO6wd
xvdpMetZV5A9Ljr8Ww72DPDkvUprk7u55OMgZZ4Fps53PnqwpNOjt3phIUH4iVE=
=6Fxw
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2015-06-15  9:13 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 [this message]
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=557E971F.3010908@riseup.net \
    --to=odinn.cyberguerrilla@riseup$(echo .)net \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /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