public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Troy Benjegerdes <hozer@hozed.org>
To: Luke Dashjr <luke@dashjr.org>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Requirement for pseudonymous BIP submissions
Date: Fri, 24 Mar 2017 02:30:29 +0000	[thread overview]
Message-ID: <20170324023029.GD23538@hostname.unassigned> (raw)
In-Reply-To: <201703181915.11040.luke@dashjr.org>

On Sat, Mar 18, 2017 at 07:15:09PM +0000, Luke Dashjr via bitcoin-dev wrote:
> On Saturday, March 18, 2017 3:23:16 PM Chris Stewart via bitcoin-dev wrote:
> > There is inconvenience added here. You need to make a new email address,
> > you need to make a new github account to submit the BIP. 
> 
> GitHub doesn't allow people to have multiple accounts last I checked.

C'mon people.

Anyone remember when git didn't even exist and all we had was CVS, 
subversion, and BitKeeper?

Get me a couple of motivated grad students who know Python and we can
turn a combination of Mercurial, BitTorrent, and pynode into a distributed,
leaderless, decentralized version control system that can let users 
create a crypto key, anonymously propose BIPs, and then get paid in
crypto for the best commits.

Who else would contribute to a crowdfunding effort to do such at thing?


  reply	other threads:[~2017-03-24  2:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 15:23 [bitcoin-dev] Requirement for pseudonymous BIP submissions Chris Stewart
2017-03-18 16:57 ` Andrew Johnson
2017-03-18 17:35   ` Chris Stewart
2017-03-18 19:15 ` Luke Dashjr
2017-03-24  2:30   ` Troy Benjegerdes [this message]
2017-03-29  8:49 ` Tom Zander
     [not found] <mailman.29.1489924803.11420.bitcoin-dev@lists.linuxfoundation.org>
2017-03-19 21:17 ` Steve Davis
2017-03-19 23:43 muyuu
2017-03-24  2:18 ` hozer
     [not found]   ` <CAGL6+mEceO2D2ueeVgv20r5p6tsofMLSTN1ExWfGysJHuM5XfA@mail.gmail.com>
2017-03-28  1:31     ` Troy Benjegerdes

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=20170324023029.GD23538@hostname.unassigned \
    --to=hozer@hozed.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=luke@dashjr.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