public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Corallo <lf-lists@mattcorallo.com>
To: Greg Maxwell <gmaxwell@gmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposed BIP editor: Kalle Alm
Date: Sat, 24 Apr 2021 10:45:46 -0400	[thread overview]
Message-ID: <6764cc61-70cc-2033-43bc-347158dcfd62@mattcorallo.com> (raw)
In-Reply-To: <CAAS2fgSrkH=7T6=MvhmLq4HAcmJC+_sR9YWQZ3CsrhyLrmBHAw@mail.gmail.com>

What is preventing the BIP maintainership role from moving to a bot? It does seem like a bot should be able to do a fine 
job given the explicit criteria (though ignoring obvious spam is often nice, its by no means a requirement).

Given recent events where humans have....acted like humans, it seems a move to a bot may be warranted.

Matt

On 4/24/21 00:42, Greg Maxwell via bitcoin-dev wrote:
> I am opposed to the addition of Kalle Alm at this time.
> 
> Those who believe that adding him will resolve the situation with
> Luke-jr's inappropriate behavior re: PR1104 are mistaken.
> 
> 
> 
> 27e59ffd51ee5a95d0e0faff70e045faca10b00015e90abc1c8de48b1dfff40c
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 


  reply	other threads:[~2021-04-24 14:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24  4:42 [bitcoin-dev] Proposed BIP editor: Kalle Alm Greg Maxwell
2021-04-24 14:45 ` Matt Corallo [this message]
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
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=6764cc61-70cc-2033-43bc-347158dcfd62@mattcorallo.com \
    --to=lf-lists@mattcorallo.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=gmaxwell@gmail.com \
    /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