<oembed><type>rich</type><version>1.0</version><author_name>npub1gg0pysd236d4em7pts906ev9kf6f30j8werd40j2vwpes7fqdn4qtt7uvk</author_name><author_url>https://nostr.ae/npub1gg0pysd236d4em7pts906ev9kf6f30j8werd40j2vwpes7fqdn4qtt7uvk</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2021-04-23&#xA;📝 Original message:ACK.&#xA;&#xA;p.&#xA;&#xA;&#xA;On Fri, Apr 23, 2021 at 10:09 AM Luke Dashjr via bitcoin-dev &lt;&#xA;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt; Unless there are objections, I intend to add Kalle Alm as a BIP editor to&#xA;&gt; assist in merging PRs into the bips git repo.&#xA;&gt;&#xA;&gt; Since there is no explicit process to adding BIP editors, IMO it should be&#xA;&gt; fine to use BIP 2&#39;s Process BIP progression:&#xA;&gt;&#xA;&gt; &gt; A process BIP may change status from Draft to Active when it achieves&#xA;&gt; &gt; rough consensus on the mailing list. Such a proposal is said to have&#xA;&gt; &gt; rough consensus if it has been open to discussion on the development&#xA;&gt; &gt; mailing list for at least one month, and no person maintains any&#xA;&gt; &gt; unaddressed substantiated objections to it.&#xA;&gt;&#xA;&gt; A Process BIP could be opened for each new editor, but IMO that is&#xA;&gt; unnecessary. If anyone feels there is a need for a new Process BIP, we can&#xA;&gt; go&#xA;&gt; that route, but there is prior precedent for BIP editors appointing new&#xA;&gt; BIP&#xA;&gt; editors, so I think this should be fine.&#xA;&gt;&#xA;&gt; Please speak up soon if you disagree.&#xA;&gt;&#xA;&gt; Luke&#xA;&gt; _______________________________________________&#xA;&gt; bitcoin-dev mailing list&#xA;&gt; bitcoin-dev at lists.linuxfoundation.org&#xA;&gt; https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210423/0849a63a/attachment.html&gt;</html></oembed>