public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org,
	"Karl-Johan Alm" <karljohan-alm@garage.co.jp>
Subject: Re: [bitcoin-dev] Absent authors and BIP updates
Date: Thu, 25 Jul 2019 03:06:24 +0000	[thread overview]
Message-ID: <201907250306.26113.luke@dashjr.org> (raw)
In-Reply-To: <CALJw2w7rjLPtkR6hNyprR208yMOtajch4fTLinmw79FNqw_3hQ@mail.gmail.com>

On Tuesday 23 July 2019 15:09:02 Karl-Johan Alm via bitcoin-dev wrote:
> People come in as Bitcoin developers all the time, but sometimes
> people also leave permanently. In the case of BIP authors, when a user
> leaves and does not respond to (reasonable) requests to change their
> BIPs, we are sort of stuck right now.

BIP 2 allows assigning a new champion.

https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#Transferring_BIP_Ownership


      reply	other threads:[~2019-07-25  3:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 15:09 [bitcoin-dev] Absent authors and BIP updates Karl-Johan Alm
2019-07-25  3:06 ` Luke Dashjr [this message]

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=201907250306.26113.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=karljohan-alm@garage.co.jp \
    /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