public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] A critique of bitcoin open source community
Date: Sun, 20 Oct 2013 12:00:43 +0200	[thread overview]
Message-ID: <CA+s+GJB04yBopuV7n2p2UsTCqwy_E=4-ingogne=DMNRS1DREw@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgRu1j0w8RsiYutixEDxs1NYZVxQ7D7VRgDVi1b-wx+vUQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

On Sun, Oct 20, 2013 at 1:20 AM, Gregory Maxwell <gmaxwell@gmail•com> wrote:

> Since much discussion didn't materialize I went and gave it a
> technical once over, posting to the forum.


At least I now understand where he got the idea of bitcoin devs being a
bunch of paranoid, anti-authoritarian nutjobs :-) I've been on a lot of
forums in my life but never encountered one with such selfish, unhelpful,
trolling, complaining sods (well maybe apart from 15-year old gamers).

Nick couldn't have got that idea from discussion on this mailing list or
#bitcoin-dev. Please don't send anyone to that jungle. People shouldn't get
the idea that that the forum is our development community, or even endorsed
by the devs.

As for the real developer community, I haven't noticed so much
unfriendliness or closedness. But the core devs are with very few people
(certainly compared to the number of users) and reviewing and testing takes
time so pull requests, proposals and such can linger for a while. Which can
indeed be frustrating.

Wladimir

[-- Attachment #2: Type: text/html, Size: 1710 bytes --]

  parent reply	other threads:[~2013-10-20 10:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19 16:38 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
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 [this message]
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='CA+s+GJB04yBopuV7n2p2UsTCqwy_E=4-ingogne=DMNRS1DREw@mail.gmail.com' \
    --to=laanwj@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=gmaxwell@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