From: Milly Bitcoin <milly@bitcoins.info>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] This thread is not about the soft/hard fork technical debate
Date: Mon, 5 Oct 2015 23:39:59 -0400 [thread overview]
Message-ID: <5613428F.4080504@bitcoins.info> (raw)
In-Reply-To: <8EF9A9A8-3EBE-4427-9745-1C494DF12E9A@gmx.com>
> I believe we should work to deprecate the idea that Core is somehow the “core of Bitcoin,"
I never did understand the terminology. There were "core developers"
which i understood to mean the primary developers of the Bitcoin
software. Then, suddenly, the software's name was changed from QT to
"Core." That seemed to me to be different meaning of the word "Core"
yet it was often treated as the same. So a developer who is not one of
the anointed 5 is a "Core developer" because they work on Bitcoin Core.
The anointed 5 would be "Core Core Developers?"
In any case if I could get a list of "Core Developers" as referenced in
the copyright notice that would also be good since that is a legal notice.
Russ
next prev parent reply other threads:[~2015-10-06 3:40 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 15:56 [bitcoin-dev] This thread is not about the soft/hard fork technical debate Sergio Demian Lerner
2015-10-05 16:39 ` NxtChg
2015-10-05 16:51 ` Luke Dashjr
2015-10-05 16:56 ` Mike Hearn
2015-10-05 17:01 ` Paul Sztorc
2015-10-05 17:33 ` Peter R
2015-10-05 17:56 ` NxtChg
2015-10-05 22:56 ` Btc Drak
2015-10-05 23:05 ` Milly Bitcoin
2015-10-05 17:35 ` Btc Drak
2015-10-06 18:23 ` Venzen Khaosan
2015-10-06 18:28 ` Venzen Khaosan
2015-10-06 19:34 ` naama.kates
2015-10-05 17:03 ` Btc Drak
2015-10-05 17:26 ` Tom Zander
2015-10-05 17:52 ` Btc Drak
2015-10-05 18:04 ` Gregory Maxwell
2015-10-05 18:33 ` Tom Zander
2015-10-05 18:50 ` NotMike Hearn
2015-10-05 17:33 ` s7r
2015-10-05 18:51 ` Tom Zander
2015-10-05 18:35 ` Gregory Maxwell
2015-10-05 19:13 ` Tom Zander
2015-10-05 19:41 ` Gregory Maxwell
2015-10-05 20:05 ` Steven Pine
2015-10-05 20:21 ` Milly Bitcoin
2015-10-06 7:17 ` cipher anthem
2015-10-06 7:20 ` Eric Lombrozo
2015-10-06 7:29 ` Marcel Jamin
2015-10-06 8:34 ` NotMike Hearn
2015-10-06 19:40 ` naama.kates
2015-10-05 20:28 ` Santino Napolitano
2015-10-05 20:35 ` Tom Zander
2015-10-05 20:54 ` Dave Scotese
2015-10-05 20:56 ` Gregory Maxwell
2015-10-05 21:08 ` Tom Zander
2015-10-05 21:16 ` Milly Bitcoin
2015-10-05 21:26 ` Gregory Maxwell
2015-10-06 7:14 ` Tom Zander
2015-10-05 21:27 ` Peter R
2015-10-05 21:30 ` Gregory Maxwell
2015-10-05 21:36 ` Milly Bitcoin
2015-10-05 21:37 ` Peter R
2015-10-06 1:37 ` Tom Harding
2015-10-06 3:20 ` Peter R
2015-10-06 3:39 ` Milly Bitcoin [this message]
2015-10-06 4:54 ` Luke Dashjr
2015-10-06 5:08 ` Milly Bitcoin
2015-10-06 5:49 ` Milly Bitcoin
2015-10-06 5:53 ` Luke Dashjr
2015-10-06 6:03 ` Milly Bitcoin
2015-10-06 22:14 ` phm
2015-10-06 5:07 ` NotMike Hearn
2015-10-06 5:33 ` Peter R
2015-10-05 19:36 ` Milly Bitcoin
2015-10-05 23:18 ` Eric Lombrozo
2015-10-06 17:28 ` Venzen Khaosan
2015-10-07 0:04 ` Sergio Demian Lerner
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=5613428F.4080504@bitcoins.info \
--to=milly@bitcoins.info \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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