From: Bitcoin Error Log <bitcoinerrorlog@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: Adding New BIP Editors
Date: Sun, 10 Mar 2024 10:27:48 -0700 (PDT) [thread overview]
Message-ID: <ad284018-e99c-4552-88ca-11b9ed340661n@googlegroups.com> (raw)
In-Reply-To: <27a5460c-518b-45dd-b48b-570c1681887dn@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 3549 bytes --]
I'd support Atak, Bishop, or Somsen, fwiw.
On Sunday, March 10, 2024 at 5:12:16 PM UTC Michael Folkson wrote:
> +1 on Kanzure and RubenSomsen
>
> I would put my name forward if Kanzure, RubenSomsen weren't willing to do
> it and I was concerned about who it might be. I don't think it should be
> someone the Bitcoin dev community isn't familiar with and hasn't proven
> themselves over a long period of time like Kanzure, RubenSomsen have. There
> is the opportunity for a new BIP editor to cause chaos if they were of the
> wrong temperament and weren't willing to acknowledge opposing views and
> perspectives. Both Kanzure and RubenSomsen have proved over a long period
> of time that although they have their own personal views (like anyone else)
> they won't censor transcripts of presentations or emails to the bitcoin-dev
> mailing list that contain opposing views to their own. I'm not sure if any
> of the other candidates putting themselves forward here tick the same boxes
> as Kanzure and RubenSomsen. I also don't think BIP editors should be Luke
> Dashjr's personal fiefdom even though overall I personally think Luke has
> done an excellent job over many years as BIP editor in sometimes difficult
> circumstances.
>
> Thanks
> Michael
>
> On Tuesday, February 27, 2024 at 7:27:57 PM UTC Ava Chow wrote:
>
>> Hi All,
>>
>> Following on the recent [discussion][1] about BIP process friction, and
>> admissions from Luke that he has not had the time to actively work on
>> the BIPs repo ([2], [3]), I think it is prudent for us to look at adding
>> more BIPs editors. These people would have the same permissions and
>> responsibilities that Luke has, i.e. can assign BIP numbers, merge PRs
>> adding new BIPs, merge PRs to fix existing BIPs,and all other
>> responsibilities as described in [BIP 2][4]. I think this would
>> significantly help get through the backlog of BIPs PRs, and responding
>> to them in a timely manner to significantly reduce the friction of
>> getting BIPs changes merged. Of course, this would require that all BIP
>> editors agree on the numbering scheme so that BIPs continue to be
>> numbered consistently.
>>
>> Considering the responsibilities of these tasks, I think any new BIP
>> editors should be people who have a history of following and being
>> involved in Bitcoin development, as well as being known to evaluate
>> proposals objectively, and of course, are willing to do the job. With
>> that in mind, I think both Kanzure and RubenSomsen are very good
>> candidates to be BIP editors, and having both of them working on the
>> BIPs repo would greatly benefit all of us.
>>
>> Thanks,
>> Ava
>>
>> [1]:
>>
>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/022289.html
>> [2]:
>>
>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/022291.html
>> [3]: https://twitter.com/LukeDashjr/status/1761127972302459000
>> [4]:
>>
>> https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#user-content-BIP_Editor_Responsibilities__Workflow
>>
>>
--
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/ad284018-e99c-4552-88ca-11b9ed340661n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 5682 bytes --]
next prev parent reply other threads:[~2024-03-12 10:20 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 18:53 [bitcoindev] " '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
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-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 [this message]
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=ad284018-e99c-4552-88ca-11b9ed340661n@googlegroups.com \
--to=bitcoinerrorlog@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.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