public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] A critique of bitcoin open source community
Date: Sat, 19 Oct 2013 16:20:59 -0700	[thread overview]
Message-ID: <CAAS2fgRu1j0w8RsiYutixEDxs1NYZVxQ7D7VRgDVi1b-wx+vUQ@mail.gmail.com> (raw)
In-Reply-To: <201310192229.19932.luke@dashjr.org>

On Sat, Oct 19, 2013 at 3:29 PM, Luke-Jr <luke@dashjr.org> wrote:
> See BIP 1 for the process.. proposals go to this mailing list first.

FWIW, he did post to the mailing list and he got an underwhelming response:

http://sourceforge.net/mailarchive/forum.php?thread_name=20ec1e35-3051-45d6-b449-e4a4d5c06dc8%40me.com&forum_name=bitcoin-development

When I responded to him on BCT I said "I was about to suggest you hit
the mailing list for some initial comments first— but I see you've
done that. I'll issue a number in a couple days once there has been a
little chance for some discussion.".

Since much discussion didn't materialize I went and gave it a
technical once over, posting to the forum.  In hindsight, I probably
should have also posted my review to the mailing list, which might
have served to restart some additional discussion.



  reply	other threads:[~2013-10-19 23:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19 16:38 [Bitcoin-development] A critique of bitcoin open source community Mitar
2013-10-19 16:50 ` Melvin Carvalho
2013-10-19 20:40 ` Gregory Maxwell
2013-10-19 21:09   ` Mitar
2013-10-19 21:16   ` Jean-Paul Kogelman
2013-10-19 22:29     ` Luke-Jr
2013-10-19 23:20       ` Gregory Maxwell [this message]
2013-10-19 23:35         ` Jean-Paul Kogelman
2013-10-19 23:57           ` Peter Todd
2013-10-20  0:52             ` Jean-Paul Kogelman
2013-10-20 22:43               ` Peter Todd
2013-10-20 23:11                 ` Peter Todd
2013-10-21  0:27                 ` Jeff Garzik
2013-10-21  6:25                   ` Peter Todd
2013-10-21  6:40                     ` Jean-Paul Kogelman
2013-10-21  6:43                       ` Peter Todd
2013-10-21  6:52                         ` Jean-Paul Kogelman
2013-10-21  7:03                           ` Martin Sustrik
2013-10-21  7:07                             ` Jean-Paul Kogelman
2013-10-21  7:28                               ` Martin Sustrik
2013-10-21  9:36                             ` Melvin Carvalho
2013-10-21  9:44                               ` Arto Bendiken
2013-10-21  9:49                                 ` Jean-Paul Kogelman
2013-10-21 10:21                                   ` Jorge Timón
2013-10-20 10:00         ` Wladimir
2013-10-19 23:21       ` Jean-Paul Kogelman
2013-10-19 23:22         ` Jean-Paul Kogelman
2013-10-19 22:33 ` Mike Hearn

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=CAAS2fgRu1j0w8RsiYutixEDxs1NYZVxQ7D7VRgDVi1b-wx+vUQ@mail.gmail.com \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --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