From: Sjors Provoost <sjors@sprovoost•nl>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposed BIP editor: Kalle Alm
Date: Mon, 26 Apr 2021 17:02:06 +0200 [thread overview]
Message-ID: <54852E33-080B-4C44-AD75-F0902B420280@sprovoost.nl> (raw)
In-Reply-To: <202104230209.05373.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]
ACK for adding Kalle.
Recent drama aside, having a single editor is not ideal. There's currently 110 open pull requests to the BIPs repo.
- Sjors
> Op 23 apr. 2021, om 04:09 heeft Luke Dashjr via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> het volgende geschreven:
>
> Unless there are objections, I intend to add Kalle Alm as a BIP editor to
> assist in merging PRs into the bips git repo.
>
> Since there is no explicit process to adding BIP editors, IMO it should be
> fine to use BIP 2's Process BIP progression:
>
>> A process BIP may change status from Draft to Active when it achieves
>> rough consensus on the mailing list. Such a proposal is said to have
>> rough consensus if it has been open to discussion on the development
>> mailing list for at least one month, and no person maintains any
>> unaddressed substantiated objections to it.
>
> A Process BIP could be opened for each new editor, but IMO that is
> unnecessary. If anyone feels there is a need for a new Process BIP, we can go
> that route, but there is prior precedent for BIP editors appointing new BIP
> editors, so I think this should be fine.
>
> Please speak up soon if you disagree.
>
> Luke
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-26 15:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
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-25 20:29 ` [bitcoin-dev] Reminder on the Purpose of BIPs Matt Corallo
2021-04-25 21:00 ` Luke Dashjr
2021-04-25 21:14 ` Matt Corallo
2021-04-25 21:22 ` Luke Dashjr
2021-04-25 21:31 ` Matt Corallo
2021-04-26 19:43 ` David A. Harding
2021-04-26 20:04 ` Greg Maxwell
2021-04-27 19:43 ` Melvin Carvalho
2021-04-27 9:04 ` W. J. van der Laan
2021-04-27 11:49 ` Erik Aronesty
2021-04-27 11:33 ` John Newbery
2021-04-27 12:16 ` Jorge Timón
2021-04-26 15:02 ` Sjors Provoost [this message]
2021-04-26 16:56 ` [bitcoin-dev] Proposed BIP editor: Kalle Alm James O'Beirne
2021-04-26 18:13 ` W. J. van der Laan
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
2021-04-30 16:58 ` Jameson Lopp
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=54852E33-080B-4C44-AD75-F0902B420280@sprovoost.nl \
--to=sjors@sprovoost$(echo .)nl \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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