From: Jon A <jonnyatack@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: BIP-85 Champion Unreachable? Please weigh in.
Date: Thu, 27 Jun 2024 10:37:52 -0700 (PDT) [thread overview]
Message-ID: <bbfcc19e-d2a7-4d93-af00-199672fd0fe8n@googlegroups.com> (raw)
In-Reply-To: <b05398c7-a416-4f86-b871-a7a34c6465d3n@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1871 bytes --]
Hi Aneesh,
ACK, for my part, on your initiative. The original author, Ethan
Kosakovsky, appears to have no GitHub activity since 2021:
https://github.com/ethankosakovsky.
Cheers.
On Wednesday, June 26, 2024 at 11:59:37 AM UTC-6 Aneesh Karve wrote:
> Greetings,
>
> I submitted a pull request <https://github.com/bitcoin/bips/pull/1600> to
> correct some inaccuracies and inconsistencies in BIP-85
> <https://github.com/bitcoin/bips/blob/master/bip-0085.mediawiki> but the
> original author (Ethan Kosakovsky) is unreachable via both email and
> GitHub <https://github.com/ethankosakovsky>.
>
> With guidance from Mark Erhardt
> <https://github.com/bitcoin/bips/pull/1600#issuecomment-2191817502>I am
> asking if any of you are able to reach Ethan?
>
> If Ethan is unreachable or unwilling to maintain BIP-85, I volunteer as a
> champion for BIP-85, as afforded by BIP-2:
>
> *It occasionally becomes necessary to transfer ownership of BIPs to a new
> champion... A good reason to transfer ownership is because the original
> author no longer has the time or interest in updating it or following
> through with the BIP process, or has fallen off the face of the 'net (i.e.
> is unreachable or not responding to email).*
>
> I'm a computer scientist who has implemented BIP-85, BIP-32, and BIP-39
> here <https://github.com/akarve/bipsea>. I use BIP-85 and have written
> about its potential in other posts on this list.
>
>
--
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/bbfcc19e-d2a7-4d93-af00-199672fd0fe8n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3611 bytes --]
prev parent reply other threads:[~2024-06-27 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 17:55 [bitcoindev] " Aneesh Karve
2024-06-27 17:37 ` Jon A [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=bbfcc19e-d2a7-4d93-af00-199672fd0fe8n@googlegroups.com \
--to=jonnyatack@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