public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Antoine Riard <antoine.riard@gmail.com>
To: Brandon Black <freedom@reardencode.com>
Cc: Matt Corallo <lf-lists@mattcorallo.com>, Murch <murch@murch.one>,
	 bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
Date: Thu, 28 Mar 2024 19:42:15 +0000	[thread overview]
Message-ID: <CALZpt+E8DohYEJ9aO+FiF6+EKMCP5oEbHSKSXpq0VKVBhJLhrw@mail.gmail.com> (raw)
In-Reply-To: <ZgWRu32FXzqqg69V@console>

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

Hi all,

On the timeframe of the new appointment of new BIP editors, I would suggest
to postpone the effective date to the 1st May or after.

There is a CoreDev edition happening in April and it's better to not
conflict the appointment of new BIP editors with any of the CoreDev dates
by transparency towards the wider community.
This avoids last-minute "Hong-Kong Agreement" decision-making-style and
anyone present in the room with the GH administrative rights on the BIP
repository making the change in a "fait accompli".

On all the other concerns, I think it's still better to split the
administrative rights between 1) editors who can merge and 2)
"product-management" style privileges for PR / issues sorting.
I think it's good to let technical relevance of the proposal be appreciated
by the wider community, marking them as "rejected" if necessary.

As new BIP editors, I'm supporting the following list:
- Kanzure (great responsiveness in my experience)
- Ruben (very knowledgeable in all part of Bitcoin stack)
- Roasbeef (i think it's good to have someone for all inter-compatibility
clients things)
- Murch (top bitcoin stackoverflow contributor)
- Jon Atack (much experience with bitcoin core codebase and great
responsiveness too)

As new BIP "decentralized PM", I'm supporting the following list:
- Seccour

I don't know the Bitcoin technical credentials of Greg Tonoski.

I think a good thing is to have not-only US-based BIP editors for higher
timezones coverage and BIP process responsiveness.

Best,
Antoine


Le jeu. 28 mars 2024 à 16:16, Brandon Black <freedom@reardencode.com> a
écrit :

> I agree with Matt's suggestions, and also support Jon Atack as a BIP
> editor.
>
> * Jon's work in bitcoin has focused on practical concerns of users of
> the bitcoin software, a valuable perspective for the BIP process as
> well. He's been a steady contributor to the bitcoin node software for 4
> continuous years, this steadiness would be a boon to the BIP process.
>
> Best,
>
> --Brandon
>
> On 2024-03-27 (Wed) at 19:54:53 -0400, Matt Corallo wrote:
> > Seems reasonable to me.
> >
> > While there are plenty of competent technical folks who would make fine
> BIP
> > editors, I'd suggest Kanzure and Murch as clear candidates over others:
> >
> >  * Kanzure has been around for longer than any other candidate as far as
> I
> > can tell, and has certainly seen more proposals for changes to Bitcoin
> than
> > anyone. This makes him a great candidate to point new BIP authors to
> > appropriate citations. Similarly, he has a long history of being very
> > responsive, which I believe is part of the goal in appointing new editors
> > here.
> >  * Murch similarly has lots of experience dealing with lots of various
> ideas
> > around Bitcoin, but importantly here also has worked extensively to
> document
> > appropriate terminology for all things Bitcoin [1]. This makes him an
> > excellent copy editor of Bitcoin technical proposals, which is basically
> the
> > only thing the BIP editors are supposed to do.
> >
> > While there are a handful of other candidates mentioned in this thread
> who
> > are technically quite competent, that isn't really the relevant criteria
> for
> > BIP editors.
> >
> > Matt
> >
> > [1] https://github.com/murchandamus/bips/pull/1/files
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Bitcoin Development Mailing List" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/bitcoindev/cuMZ77KEQAA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> bitcoindev+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/bitcoindev/ZgWRu32FXzqqg69V%40console.
>

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/CALZpt%2BE8DohYEJ9aO%2BFiF6%2BEKMCP5oEbHSKSXpq0VKVBhJLhrw%40mail.gmail.com.

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

  reply	other threads:[~2024-03-28 20:19 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 18:53 [bitcoindev] Adding New BIP Editors 'Ava Chow' via Bitcoin Development Mailing List
2024-02-27 20:11 ` [bitcoindev] " 'Léo Haf' via Bitcoin Development Mailing List
2024-02-27 22:40   ` Luke Dashjr
2024-02-27 22:57     ` 'Ava Chow' via Bitcoin Development Mailing List
2024-02-27 23:26     ` Steve Lee
2024-02-28 11:12     ` bitcoin-dev-ml.void867 via Bitcoin Development Mailing List
2024-02-28 16:31     ` Tim Ruffing
2024-03-07 20:56       ` Antoine Riard
2024-03-14 11:56       ` Chris Stewart
2024-03-27 21:25         ` Murch
2024-03-27 23:36           ` Keagan McClelland
2024-03-27 23:39           ` John C. Vernaleo
2024-03-28 13:02             ` Murch
2024-03-28 16:09               ` /dev /fd0
2024-03-28 20:04                 ` Matt Corallo
2024-03-28 20:31                   ` Antoine Riard
2024-03-28 20:59                   ` John C. Vernaleo
2024-03-28 21:19                     ` Matt Corallo
2024-03-29  2:34                     ` Michael Folkson
2024-03-29  5:24                   ` /dev /fd0
2024-03-29 21:08                     ` Antoine Riard
2024-03-30 11:51                       ` Michael Folkson
2024-03-30 20:01                         ` Antoine Riard
2024-03-31 16:01                           ` Michael Folkson
2024-04-01 20:14                             ` Antoine Riard
2024-04-07 10:11                             ` Ali Sherief
2024-04-01 21:13                   ` David A. Harding
2024-04-01 23:55                     ` /dev /fd0
2024-04-02  0:37                       ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-02 13:49                         ` /dev /fd0
2024-04-02 14:28                           ` Luke Dashjr
2024-04-02 15:13                             ` Gloria Zhao
2024-04-02 15:39                               ` Luke Dashjr
2024-04-03 15:03                                 ` Murch
2024-04-02  8:18                     ` Michael Folkson
2024-04-02 14:24                     ` nvk
2024-04-11 14:22                       ` Sergi Delgado Segura
2024-04-15 17:50                         ` Matt Corallo
2024-04-16 12:34                           ` Tim Ruffing
2024-04-16 13:32                             ` NVK
2024-04-16 17:08                         ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-17 23:58                           ` 'nsvrn' via Bitcoin Development Mailing List
2024-04-19 22:32                           ` Olaoluwa Osuntokun
2024-04-20 19:14                           ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-20 19:48                             ` NVK
2024-04-20 19:59                             ` Michael Folkson
2024-04-20 20:59                               ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-20 20:46                             ` Steve Lee
2024-04-20 21:08                               ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-20 21:11                                 ` Steve Lee
2024-04-20 21:37                                   ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-20 22:03                                     ` Steve Lee
2024-04-20 22:47                                       ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-22  2:44                                         ` Steve Lee
2024-04-20 22:21                                 ` Michael Folkson
2024-04-20 23:05                                   ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-21 11:43                                     ` Michael Folkson
2024-04-21 16:39                                       ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-21 17:57                                         ` Michael Folkson
2024-04-21 18:47                                           ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-21 19:18                                             ` Michael Folkson
2024-04-21 20:48                                             ` Antoine Riard
2024-04-21 23:01                             ` Matt Corallo
2024-04-22  0:06                               ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-22  4:28                             ` Ali Sherief
2024-04-23 22:15                             ` Anthony Towns
2024-04-25  6:42                               ` Antoine Riard
2024-03-29 22:17               ` Keagan McClelland
2024-03-30  4:04               ` Peter Todd
2024-04-01 18:42               ` Jonas Nick
2024-03-27 23:54           ` Matt Corallo
2024-03-28 15:50             ` Brandon Black
2024-03-28 19:42               ` Antoine Riard [this message]
2024-03-28 20:04               ` Matt Corallo
2024-04-02 13:17                 ` [bitcoindev] Time for an update to BIP2? Tim Ruffing
2024-04-03 19:44                   ` Pieter Wuille
2024-04-04  5:00                     ` Anthony Towns
2024-04-04  9:09                       ` Niklas Goegge
2024-04-04 12:58                         ` [bitcoindev] Adding New BIP Editors 0xB10C
2024-05-13 18:33                       ` [bitcoindev] Time for an update to BIP2? Murch
2024-09-18 18:25                         ` Murch
2024-09-19  7:47                           ` Antoine Riard
2024-09-19 18:48                             ` Murch
2024-04-01 18:41             ` [bitcoindev] Re: Adding New BIP Editors Murch
2024-03-31 17:01           ` 'Ava Chow' via Bitcoin Development Mailing List
2024-04-01  6:21             ` /dev /fd0
2024-04-01 11:58             ` Michael Folkson
2024-04-03 16:58             ` Juan Galt
2024-04-03 17:24               ` Vasil Dimov
2024-04-03 18:34                 ` 'Fabian' via Bitcoin Development Mailing List
2024-03-07 22:39     ` Keagan McClelland
2024-02-27 21:33 ` [bitcoindev] " 'Antoine Poinsot' via Bitcoin Development Mailing List
2024-02-27 21:48   ` Greg Tonoski
2024-02-27 23:10 ` [bitcoindev] " /dev /fd0
2024-02-28  4:22 ` /dev /fd0
2024-03-09 10:46 ` Michael Folkson
2024-03-10 17:27   ` Bitcoin Error Log
2024-03-11 16:48   ` Jon A
2024-04-05 19:18 ` Larry Ruane

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=CALZpt+E8DohYEJ9aO+FiF6+EKMCP5oEbHSKSXpq0VKVBhJLhrw@mail.gmail.com \
    --to=antoine.riard@gmail.com \
    --cc=bitcoindev@googlegroups.com \
    --cc=freedom@reardencode.com \
    --cc=lf-lists@mattcorallo.com \
    --cc=murch@murch.one \
    /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