As per #25560, I suggested that new maintainers should be added with a call for maintainer process as outlined below.
“Call for Maintainer” (C4M) by one of the existing maintainers or regular contributors. C4Ms should specify if the call is for a General Maintainer, or for a Scoped Maintainer. If the role is for a Scoped Maintainer, the C4M should describe the need for a new maintainer, and link to some Pull Requests (or other material) that would be relevant for such a maintainer to be responsible for.
The doc has not been adopted. However, bitcoin is a permissionless project, so I am opening a C4M that is just of my own personal initiative.
Do we need a new scoped maintainer?
From IRC on August 12th, 2022, where @laanwj also stepped down:
0<bytes1440000> I see a need for "janitorial maintainer" who understands the importance of privacy in core and privacy of contributors. Since [#25560](/bitcoin-bitcoin/25560/) is still open and intent of reviewers doesn't look they want to improve anything in the process, there is no "call for maintainers" thing.
1<bytes1440000> I would prefer someone who has already contributed to bitcoin privacy and privacy in general, not living in first world countries and not funded by brink.
2<vasild> #proposedmeetingtopic vasild for a new maintainer with a focus on P2P/networking
3<vasild> I volunteer, if there is a perceived need for that.
4<bytes1440000> vasild: thanks for volunteering and i think you are the best candidate for p2p/privacy. I wish we had one for mempool/privacy and wallet/privacy as well.
In Today’s IRC Meeting, August 18th 2022. For the sake of the new process, please consider that ACKs here are ACKs on the person but are included here as demonstrating ACKs on the need for such a new maintainer & the role. Note also that vasild is not explicitly stating privacy, as bytes1440000 requested initially, which has been clarified below in this discussion to be out-of-scope for this proposed maintainer. (Please see the complete logs for all discussion, this is not a full excerpy).
0<vasild_> Two maintainers stepped down recently (sipa and laanwj) and there is no dedicated maintainer for P2P/networking. So I step in coz I think I can help the project in that way. That's it.
1<laanwj> i think it would make some sense, you've been the most active in P2P development for quite a while
2<jarolrod> concept ack, i think vasild_ is very qualified for such a role. And has contributed important changes to the p2p code. He also has done extensive reviews, and catching issues others don't catch
3<michaelfolkson> +1
4<hebasto> concept ack
5<achow101> ack
6<lightlike> ack vasild
7<jonatack> a thought: the past few years vasild, laanwj, and myself have been working on or reviewing a large-ish chunk of net code that few others have been. i believe sipa knows the code well, too, along with (maybe) a couple others. laanwj has been merging these changes. so it makes sense to me that one of these would maintain.
Relevant Evamples of PRs such a maintainer might focus on
which includes things that impact privacy in P2P
But does not include non P2P/Networking Privacy code like:
Nominees
I will keep this synced with nominees from the below thread / other maintainers feel free to edit to keep synchronized. Feel free to self nominate. As per #25560, nomination period + Q&A is “open” for 2 weeks, after which a decision may be made if desired.
Current Nominees:
