public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Karl <gmkarl@gmail•com>
To: Amir Taaki <policeterror@dyne•org>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposed BIP editor: Kalle Alm
Date: Fri, 30 Apr 2021 11:39:23 -0400	[thread overview]
Message-ID: <CALL-=e7OLDa8avzSufqhEMnTe9Oece2rnCffmrQrdnX6ymt2cQ@mail.gmail.com> (raw)
In-Reply-To: <4def9376-03dc-3805-89ea-28bd78077084@dyne.org>

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

A good solution here is to make it clear to visitors that facilitation,
mediation, and organisation help is badly needed in the core development
team.

People with such expertise can even be hired directly.

A good facilitator opens communication paths between all parties, leaving
everyone satisfied with decisions.  Don't accept a compromise if you can
look for something better.

On Fri, Apr 30, 2021, 8:00 AM Amir Taaki via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> A committee to guide the committee? You guys truly have lost the plot.
>
> All the good minds and cryptographers have left Bitcoin. What remains is
> an empty echo chamber.
>
> Truth is these problems start with lack of vision and long-term roadmap,
> not with the processes themselves.
>
> And the Bitcoin Core monopoly created this situation; one coin, one
> client, one vision. And the inevitable infighting for ultimate power.
>
> Really if we want to go down this route, there should be a long period
> of self reflection about where the problems began rather than patching
> some process and moving on.
>
> I propose Bitcoin Core is dissolved as the official Bitcoin project. The
> community is free to elect their preferred version of Bitcoin. And most
> importantly, Bitcoin developers commit to a fully specced standard that
> all implementations move towards using.
>
> On 4/28/21 12:30 AM, Jaime Caring via bitcoin-dev wrote:
> > Kalle should not be made an editor by an ad-hoc process. I reiterate
> > Greg's NACK.
> >
> > I propose that we form a stewardship committee of frequent contributors,
> > including you, Greg, and 21 others. The stewards appoint a small set of
> > editors with permanent oversight by the stewards. A defined process
> > prevents this controversy from arising in the future and makes
> > proceedings clear.
> >
> > My proposal has been moderated off of this list, but may be viewed here:
> > https://github.com/bitcoin/bips/pull/1113
> > <https://github.com/bitcoin/bips/pull/1113>
> >
> > I care not for the role of initial transitory editor. I would be pleased
> > should any responsible community member shoulder this onus in my stead.
> >
> > Peace be upon you,
> >
> > JC
> >
> > On Mon, 26 Apr 2021 at 00:37, David A. Harding via bitcoin-dev
> > <bitcoin-dev@lists•linuxfoundation.org
> > <mailto:bitcoin-dev@lists•linuxfoundation.org>> wrote:
> >
> >     On Sat, Apr 24, 2021 at 04:42:12AM +0000, Greg Maxwell via
> >     bitcoin-dev wrote:
> >     > I am opposed to the addition of Kalle Alm at this time.  Those who
> >     > believe [this] will resolve the situation [...] re: PR1104 are
> >     > mistaken.
> >
> >     PR1104 has been merged.  Do you continue to oppose the addition?
> >
> >     Thanks,
> >
> >     -Dave
> >     _______________________________________________
> >     bitcoin-dev mailing list
> >     bitcoin-dev@lists•linuxfoundation.org
> >     <mailto:bitcoin-dev@lists•linuxfoundation.org>
> >     https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >     <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>
> >
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists•linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

  reply	other threads:[~2021-04-30 15:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24  4:42 Greg Maxwell
2021-04-24 14:45 ` Matt Corallo
2021-04-26  0:36 ` David A. Harding
2021-04-27 22:30   ` Jaime Caring
2021-04-28  9:52     ` Amir Taaki
2021-04-30 15:39       ` Karl [this message]
2021-04-30 16:58       ` Jameson Lopp
  -- strict thread matches above, loose matches on Subject: below --
2021-04-23  2:09 Luke Dashjr
2021-04-23  3:36 ` Jeremy
2021-04-23  7:49   ` John Newbery
2021-04-23  7:50 ` Pindar Wong
2021-04-23  9:11   ` Eric Martindale
2021-04-23 15:34 ` Antoine Riard
2021-04-24 10:16   ` nopara73
2021-04-26 15:02 ` Sjors Provoost
2021-04-26 16:56   ` James O'Beirne
2021-04-26 18:13 ` W. J. van der Laan

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='CALL-=e7OLDa8avzSufqhEMnTe9Oece2rnCffmrQrdnX6ymt2cQ@mail.gmail.com' \
    --to=gmkarl@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=policeterror@dyne$(echo .)org \
    /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