From: Gregory Maxwell <gmaxwell@gmail•com>
To: "Warren Togami Jr." <wtogami@gmail•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 22:38:51 +0000 [thread overview]
Message-ID: <CAAS2fgTZ65G=Qpu0tPQMsGoaRwfi_L67w0GCJGtfwc4xLrOAgA@mail.gmail.com> (raw)
In-Reply-To: <CAEz79Pp_6FhDjtR6emBcXf_WT14MbDaTxMbeAo=QAfhS-ihFCQ@mail.gmail.com>
On Sun, Jun 14, 2015 at 10:12 AM, Warren Togami Jr. <wtogami@gmail•com> wrote:
> From the perspective of our community, for bitcoin-dev it seems like a great
> fit. Why? While they are interested in supporting general open source
> development, the LF has literally zero stake in this. In addition to
> neutrality, they seem to be suitable as a competent host. They have
I support this proposal.
But for clarity sake, we should recognize that Linux Foundation isn't
a charity chartered to act in the public good, is a trade organization
which acts in the commercial interest of it's membership.
I do not think this presents a problem: LF's membership's interests
are not at odds with ours currently, and aren't likely to become so
(doubly so with sourceforge as the comparison point). We are, after
all, just talking about a development mailing list; in the unlikely
case that there were issues in the future it could be changed, and
they've demonstrated considerable competence at this kind of operation
as well, and I would be grateful to have their support. I mention it
only because the 'foundation' name sometimes carries the charity
confusion, and to be clear that I think the stakes on this matter are
small enough that it doesn't require a careful weighing of interests.
These concerns may matter for other initiatives but as you note, LF
has zero stake beyond the general support of the open source
ecosystem.
I do not believe it would be wise to delete the SF account, at least
while there are many active links to it. As it might well be recreated
to 'mirror' things as a 'service' to those following the old links.
I also agree with Jeff's comments wrt, bitcoin-security.
next prev parent reply other threads:[~2015-06-14 22:38 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.
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 [this message]
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='CAAS2fgTZ65G=Qpu0tPQMsGoaRwfi_L67w0GCJGtfwc4xLrOAgA@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=wtogami@gmail$(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