From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Sat, 30 Mar 2024 14:13:50 -0700 Received: from mail-oo1-f63.google.com ([209.85.161.63]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rqg1N-00008p-2i for bitcoindev@gnusha.org; Sat, 30 Mar 2024 14:13:50 -0700 Received: by mail-oo1-f63.google.com with SMTP id 006d021491bc7-5a486a8e1fdsf2990772eaf.2 for ; Sat, 30 Mar 2024 14:13:48 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1711833223; cv=pass; d=google.com; s=arc-20160816; b=uY52SPZQfMvY0Sd+iRBf1I0z9ULKfzr3le9USYtrMcQNi3TjxzIQvaHQR0/kd3Kav7 Ds/O26ztWtF7oLdVOou+JclFaScZiD/KYKlaLfcllq3s+fNzyJ8cxBjwX6qaXHpxNjlr jhd5FEkyB0JJOS9IZZlrmGrxsZ0ZAiKHNF1bQ8+FBW6/+agy6hGQ+GHaQzWtQOOvv4Qs 4Mq0HvXee2h+Z30TLa0BBn/bT35keqOqbKbgIESEv7UYXcJtNVdZBr8nlnc+ZUiGi1YJ HFQ42Ss8DgT4XGUmvWLRET1MpUKj7fOnCpwlfJTiTbi3tHURwcOE1TP4S+GOQyI1HB56 bD4g== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:sender:dkim-signature :dkim-signature; bh=kiHGr6XlUXkJ/rw+UmMSZhN/JE5xcai61BamX+f/6LA=; fh=aSSklehSGFj8eH/m89SmLXBp+ssYyzdkLG07O1gsRfI=; b=sHoxKrlb5QUaqGmx7Fu+BXgJTQ1wszkkxXk2xACDPn6YpAUo0i98/0DWi3W6s/0mRr EsyglGYvbsZUKGLcmAYryrqNo2+x+APDzMM6whcdIeKGXsllilf/fKF6fVHcVTlZahBm +jE5NtvhHC8DotxFduBHQ/x2t0I9jYXnzSOS7aoF1d1TmHsYv9FULJyU32KXHFTozycZ 6uURAnB5ajrRdLvEY3RvB9HhSAaOPGu3jLM/xU8rHfNzhjN5M+qktHKew/iCtqgX7KWh Kw2Jxse3i5+TucVqWqjpeOfXydvGXDec3V/OH/7cA6ceFIrT1hTyprM3jzjZ2hf+dj71 iYeg==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=ZcYFmnCt; spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::d2d as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1711833223; x=1712438023; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:sender:from:to:cc:subject:date:message-id :reply-to; bh=kiHGr6XlUXkJ/rw+UmMSZhN/JE5xcai61BamX+f/6LA=; b=cmly9UslWj0NLQ2tk2LRcLB/W9PHbtWhITo6/EW2D/NM+mrFB1pGSnynjBm5dBPuZu DdsMzBmVqdiAhtkCz6b+30Vc222Z+PVECinSjlANkv0H5mjKNbHF2JuRo8fq8OynWP1g 5JrC3HUQFtKXTBjjSirjxQadQRaCdhZiKjVpy1/bnkYmvdszmH7ramKa9stDfKuvdIkW 2xXjLdZLSV406cqqXpXt8qIucBXgd9QEr7MKsfL7M3RXlt1ldmovhipI9d/HLcISuWcH dt/N51Sy2uFXqFZ8zfkpnf0iqx+i34jb2i4jbDWaqVqjypDDMfM6CHXAXGAV6uli9qej 92KA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711833223; x=1712438023; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to; bh=kiHGr6XlUXkJ/rw+UmMSZhN/JE5xcai61BamX+f/6LA=; b=SXpoA0b7TJkto49qNbUp/zbmug9lawFkn8/93ABXKIWzqxS0zV5Sk4qRv5Rthx+xIh S5fUsotp4emCYSw9ufhMJk5k8BMVMSnwwvG9UEsW2eufzwLz2okpHRSHH81SNNpuED2J AjTZDPXAUT9mnXtAohSV8Nj5Vk9oOuAgjYSxeEIA5AgUUqAb8szstARBqBbwl4M07iFb t8bSi7ChvdJcHsdgZyzK19BZWyfUUWj1ZGtLX+ZK7rWY1HRdXUT4gqFfezFmcs+v3fZd XUaa83GaNxxiQclnyeR7SIT2VoEK1zrcdl4742TnMXs3H30OnoldnU4vPShYvu5Ktnsf SB+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711833223; x=1712438023; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-beenthere:x-gm-message-state:sender:from :to:cc:subject:date:message-id:reply-to; bh=kiHGr6XlUXkJ/rw+UmMSZhN/JE5xcai61BamX+f/6LA=; b=qWHCSFLgxitisxPrO1j21zErEvHPQcSieWRda+jasa3bxoU9dest9H76dszVNH8EyA Vm4v4m2iirK8l1oz+qrBUW4Z5zfqMjVm0ngdA4LUBghQbscd4hIaTyq0j71uxLqEKBuS 74Zb6GPBUcOJblie3hwFJriziAIb3IRwVeEBoPr3eigpZdGuXsP4FhqmuE5VRKuydanP /meS4IgTCTYGLiUur+QfJZH819DuRuRNp2iyWHO5ulfGj2mwepSuZ0IErtoYjEn6C98q X7JlsD7bkvQWoi8UENPjQer5JCShHl6BApMOLnByLcW5ibZcPL1qMCKmI1RkbjtiK2bX PjXg== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=2; AJvYcCVyoFA6pDxKA3c8ccxFR/v00iqGMD5vkQJquLZ7MRDKhlL4saNN+vH33Q4Of/8q1l0ZJ/7I+5MC9Rds6ABXxdS0QxX3rco= X-Gm-Message-State: AOJu0YwJ12yBI5R9h564MUwJP5ajyURBvIgy5/FfuOq11RUGeLERvyE+ j1IyHuyATex0uCj+DXyk94dOOc8b+L0SvbcJNe/Rj6ya18zVBeTX X-Google-Smtp-Source: AGHT+IG1cvXqpRHBiRm9Kp7zNKkwdsrezkglpyzqoQEYAI0twsGkK1YyLVKC9109QlRuln55zFwLHw== X-Received: by 2002:a05:6820:218:b0:5a1:a7b3:3d0 with SMTP id bw24-20020a056820021800b005a1a7b303d0mr5536108oob.4.1711833222947; Sat, 30 Mar 2024 14:13:42 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a4a:a405:0:b0:5a4:b452:a5ad with SMTP id v5-20020a4aa405000000b005a4b452a5adls873468ool.2.-pod-prod-00-us; Sat, 30 Mar 2024 14:13:42 -0700 (PDT) X-Received: by 2002:a05:6820:1614:b0:5a5:2923:30c7 with SMTP id bb20-20020a056820161400b005a5292330c7mr366528oob.0.1711833222283; Sat, 30 Mar 2024 14:13:42 -0700 (PDT) Received: by 2002:a05:6808:1995:b0:3c4:fbd:32d with SMTP id 5614622812f47-3c40fbd0503msb6e; Sat, 30 Mar 2024 13:01:42 -0700 (PDT) X-Received: by 2002:a17:90b:11c5:b0:29f:6bfa:207d with SMTP id gv5-20020a17090b11c500b0029f6bfa207dmr4668684pjb.29.1711828900985; Sat, 30 Mar 2024 13:01:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1711828900; cv=none; d=google.com; s=arc-20160816; b=Jp4Ep63Jh0xe+O4DfkKRm8nHgN2Tb7QdqtZ7Ci62IvbRDl8krLTYH+qlkZvDPeL/Si ZxrrErpTxnhSbH1EKeCNXg+K7aIt3g3RlKwWjPG+VyhC8xRFiQ3Rlj87GXBn8Vtj4PPy d56hcg06tKfCG8H3h5YGAqt+jO+J5W92jbT6CON6gRDmDEFpwXHAVwLJNScp2/Z2uWWe CK/NqPMD0A/AyThRIik41abnhVSWQotQ8ZGcVQrkErFoMH3MtUNe5l5RmVjgYFCuX7gu hnPV2ecRarQvujNN22J/V35qJkz+9avFUZYr1R8+3x+OlWNFHITsAy0Se5s/wUYat8c5 lttA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=gKkwncWn2lqGePcalgBKtwPYQ9Lbd+j+JSSCpfl6nAc=; fh=gNZB6R3gE0GWmgYCZFlcuq+Q7ciK/nQdnDvSFJ8wRPo=; b=uRWMQtz1h1A/3emmeyAXL1bEiQXsO53WcQBVneaErJDHKdezYjV23yHmPERrY4pw3d C2h9u69BRJbnbx9gP8e8kioU9rfemewxocw/NXggmHcEp9lVEhhjNNTisn3mE/srQNO0 k16puZhpw58izmOmmUOE1xG9zj8sx+kisgLF+1E41lpjYg7jZm7lVOQOs6HN0IwoES1w RVp3FqF/PHHskUwqy6GVYR1LtA9VCVPtUaBfZaek0Al97Eb01qkmipLhXNLi9vnq+vxG JEgINESqnVC7K4pVL6KUv8VeNEB6FfwdglGnS0KsL8Kf6WL0bNcD+Sds9lJwkxOjxaPe PwYg==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=ZcYFmnCt; spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::d2d as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com. [2607:f8b0:4864:20::d2d]) by gmr-mx.google.com with ESMTPS id h22-20020a17090ac39600b0029bbd2c38d1si791531pjt.0.2024.03.30.13.01.40 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 30 Mar 2024 13:01:40 -0700 (PDT) Received-SPF: pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::d2d as permitted sender) client-ip=2607:f8b0:4864:20::d2d; Received: by mail-io1-xd2d.google.com with SMTP id ca18e2360f4ac-7c7ee7fa1d8so94245339f.1 for ; Sat, 30 Mar 2024 13:01:40 -0700 (PDT) X-Received: by 2002:a05:6602:2111:b0:7d0:35bf:1b03 with SMTP id x17-20020a056602211100b007d035bf1b03mr6651984iox.8.1711828900121; Sat, 30 Mar 2024 13:01:40 -0700 (PDT) MIME-Version: 1.0 References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> <9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org> <42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de> <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one> <84309c3f-e848-d333-fd28-bdd55899b713@netpurgatory.com> <9baa15e4-062d-478f-8c87-8ff19ab79989@murch.one> <4c1462b7-ea1c-4a36-be81-7c3719157fabn@googlegroups.com> <6806b22d-043d-4201-841a-95e17cd8d542@mattcorallo.com> <846b668f-8386-4869-a3b1-55d346efbea1n@googlegroups.com> In-Reply-To: From: Antoine Riard Date: Sat, 30 Mar 2024 20:01:28 +0000 Message-ID: Subject: Re: [bitcoindev] Re: Adding New BIP Editors To: Michael Folkson Cc: Bitcoin Development Mailing List Content-Type: multipart/alternative; boundary="0000000000008216e70614e63949" X-Original-Sender: antoine.riard@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=ZcYFmnCt; spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::d2d as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) --0000000000008216e70614e63949 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Michael, > In the past there have been disagreements between Core maintainers and > BIP editors (e.g. Luke with Taproot activation params) and those Core > maintainers haven't merged pull requests in the BIPs repo or removed > him as a BIP editor. As long as that continues it isn't necessary to > create a new GitHub organization for the BIPs repo. They are separate > repos with different maintainers/editors but under the same > organization and everyone knows where it is located. Indeed, avoiding new conflicts like we have seen with Luke with Taproot activation params is a good reason to separate repositories in my opinion. Beyond, "security through distrusting" [0] is a very legitimate security philosophy including for communication space infrastructure. [0] https://www.qubes-os.org/news/2017/12/11/joanna-rutkowska-black-hat-europe-= 2017/ > It seems like you want to create some kind of United Nations for the > BIP process. As I said previously this is almost entirely an > administrative task. Going to a committee of 10 people with different > nationalities and languages to decide whether something should get a > BIP number is absurd. If you think Luke is slow to respond wait until > your United Nations of the BIP process has to all agree to assign a > BIP number. Please don't try to make this unnecessarily bureaucratic > and political for no reason. There's enough of that outside of > Bitcoin. No, I wish to ensure that if the aim of the BIP is ensuring high-quality and readability of standards those ones are well-written, including when the original standard is contributed by someone non-native. I can only remember numerous times when my english technical texts have been kindly corrected by other contributors. Having editors understanding multiple languages helps in quality redaction. Beyond, from reading conversations it sounds there is a disagreement if it's an administrative task (i.e "assigning numbers") or editorial one (i.e "high-quality, well-written standards"). If we wish to make things less bureaucratic, we might actually separate the two tasks with different groups of BIP process maintainers : - assign temporary numbers for experimentation - wait for more-or-less finalized drafts written in a quality fashion - assign final numbers for standard candidate deployment If you see other ways to dissociate the roles and make things less bureaucratic ? E.g having people only in charge of triage. If I remember correctly the IETF does not assign RFC numbers for draft proposals, and you generally have years of experimentation. Best, Antoine PS: By the way, even at the United Nations, unanimity is not the rule, it's two-third of the general assembly. I think your analogy is not valid. Le sam. 30 mars 2024 =C3=A0 11:52, Michael Folkson a =C3=A9crit : > > In a world where both Core and BIP repository are living under a single > Github organization, I don't think in matters that much as the highest > privilege account will be able to > override any BIP merging decision, or even remove on the flight BIP > editors rights in case of conflicts or controversies. If you're > raising the issue that the BIP repository should be moved to its own > GH repository I think it's a valuable point. > > In the past there have been disagreements between Core maintainers and > BIP editors (e.g. Luke with Taproot activation params) and those Core > maintainers haven't merged pull requests in the BIPs repo or removed > him as a BIP editor. As long as that continues it isn't necessary to > create a new GitHub organization for the BIPs repo. They are separate > repos with different maintainers/editors but under the same > organization and everyone knows where it is located. > > > Beyond, I still think we should ensure we have a wider crowd of > geographically and culturally diverse BIP editors. As if the role is > ensuring high-quality and readability of the terminology of the standards= , > we might have highly-skilled technical BIP champions which are not Englis= h > native. With the current set of proposed BIP editors, to the best of my > knowledge, at least we have few langages spoken by the candidates: Dutch, > French, German, Spanish. This can be very helpful to translate concepts > devised in language A to technical english. > > It seems like you want to create some kind of United Nations for the > BIP process. As I said previously this is almost entirely an > administrative task. Going to a committee of 10 people with different > nationalities and languages to decide whether something should get a > BIP number is absurd. If you think Luke is slow to respond wait until > your United Nations of the BIP process has to all agree to assign a > BIP number. Please don't try to make this unnecessarily bureaucratic > and political for no reason. There's enough of that outside of > Bitcoin. > > On Fri, Mar 29, 2024 at 9:14=E2=80=AFPM Antoine Riard > wrote: > > > > > Roasbeef's work on alternative clients and lightning make him > technically > > useful > > > > I think one of the aim of the BIP process is to harmonize common > mechanisms among Bitcoin clients of different langages breeds or at > different layers (wallet / full-node). > > Having someone among BIP editors with a proven track record of > contributing to other full-node codebase beyond C++ can be valuable in th= at > sense. > > Especially for all matters related to compatibility and deployment. > > > > > For example I think Jon Atack would make a great Core maintainer at > some point in the future and I'm not sure a BIP editor should also be a > Core maintainer given the > > > independence sometimes required between Core and the BIP process > > > > In a world where both Core and BIP repository are living under a single > Github organization, I don't think in matters that much as the highest > privilege account will be able to > > override any BIP merging decision, or even remove on the flight BIP > editors rights in case of conflicts or controversies. If you're raising t= he > issue that the BIP repository should be moved to its own GH repository I > think it's a valuable point. > > > > Beyond, I still think we should ensure we have a wider crowd of > geographically and culturally diverse BIP editors. As if the role is > ensuring high-quality and readability of the terminology of the standards= , > we might have highly-skilled technical BIP champions which are not Englis= h > native. With the current set of proposed BIP editors, to the best of my > knowledge, at least we have few langages spoken by the candidates: Dutch, > French, German, Spanish. This can be very helpful to translate concepts > devised in language A to technical english. > > > > Best, > > Antoine > > > > > > Le vendredi 29 mars 2024 =C3=A0 12:33:09 UTC, /dev /fd0 a =C3=A9crit : > >> > >> Justification: > >> > >> 1. Jon Atack: Good at avoiding controversies and technical > documentation. > >> 2. Roasbeef: Since BIPs are not just related to bitcoin core, it's goo= d > to have btcd maintainer as a BIP editor. > >> > >> On Friday, March 29, 2024 at 1:47:41=E2=80=AFAM UTC+5:30 Matt Corallo = wrote: > >>> > >>> Please provide justification rather than simply saying "I like Bob!". > >>> > >>> Matt > >>> > >>> On 3/28/24 12:09 PM, /dev /fd0 wrote: > >>> > I support Jon Atack and Roasbeef from this list. > >>> > > >>> > On Thursday, March 28, 2024 at 6:57:53=E2=80=AFPM UTC+5:30 Murch wr= ote: > >>> > > >>> > I just went through the thread, previously mentioned were: > >>> > > >>> > - Kanzure > >>> > - Ruben Somsen > >>> > - Greg Tonoski > >>> > - Jon Atack > >>> > - Roasbeef > >>> > - Seccour > >>> > > >>> > And Matt just suggested me for the role. Hope I didn=E2=80=99t over= look > anyone. > >>> > > >>> > On 3/27/24 19:39, John C. Vernaleo wrote: > >>> > > That said, I would find it helpful if someone could go through th= e > >>> > > thread and list all the people who've been proposed so people kno= w > who > >>> > > they should be thinking about. > >>> > > >>> > -- > >>> > 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+...@googlegroups.com bitcoindev+...@googlegroups.com>. > >>> > To view this discussion on the web visit > >>> > > https://groups.google.com/d/msgid/bitcoindev/4c1462b7-ea1c-4a36-be81-7c37= 19157fabn%40googlegroups.com > < > https://groups.google.com/d/msgid/bitcoindev/4c1462b7-ea1c-4a36-be81-7c37= 19157fabn%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter > >. > > > > -- > > 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/f8fa1a55-644f-4cf1-b8c1-4fde= f22d1869n%40googlegroups.com > . > > > > -- > Michael Folkson > Personal email: michaelfolkson@gmail.com > --=20 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 e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/= bitcoindev/CALZpt%2BEU4JzbDepsu4Wz-6e0XB4VuKCqatiRnb1nKXe%2B%2BjF%2BRw%40ma= il.gmail.com. --0000000000008216e70614e63949 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Michael,

> In the past there have= been disagreements between Core maintainers and
> BIP editors (e.g. = Luke with Taproot activation params) and those Core
> maintainers hav= en't merged pull requests in the BIPs repo or removed
> him as a = BIP editor. As long as that continues it isn't necessary to
> cre= ate a new GitHub organization for the BIPs repo. They are separate
> = repos with different maintainers/editors but under the same
> organiz= ation and everyone knows where it is located.

= Indeed, avoiding new conflicts like we have seen with Luke with Taproot act= ivation params is a good reason to separate repositories in my opinion.
Beyond, "security through distrusting" [0] is a very legit= imate security=C2=A0philosophy including for communication space infrastruc= ture.


> It seems like you want to create some kind of United= Nations for the
> BIP process. As I said previously this is almost e= ntirely an
> administrative task. Going to a committee of 10 people w= ith different
> nationalities and languages to decide whether somethi= ng should get a
> BIP number is absurd. If you think Luke is slow to = respond wait until
> your United Nations of the BIP process has to al= l agree to assign a
> BIP number. Please don't try to make this u= nnecessarily bureaucratic
> and political for no reason. There's = enough of that outside of
> Bitcoin.

No,= I wish to ensure that if the aim of the BIP is ensuring high-quality and r= eadability=C2=A0of standards those=C2=A0ones are well-written, including wh= en the original standard is contributed by someone non-native.
I = can only remember numerous times when my english technical texts have been = kindly corrected by other contributors. Having editors understanding multip= le languages helps in quality redaction.

Beyond, f= rom reading conversations it sounds there is a disagreement if it's an = administrative task (i.e "assigning numbers") or editorial one (i= .e "high-quality, well-written standards").

If we wish to make things less bureaucratic, we might actually sepa= rate the two tasks with different groups of BIP process maintainers :
=
- assign temporary numbers for experimentation
- wait for mo= re-or-less finalized drafts written in a quality fashion
- assign= final numbers for standard candidate deployment

I= f you see other ways to dissociate the roles and make things less bureaucra= tic ? E.g having people only in charge of triage.
If I remember c= orrectly the IETF does not assign RFC numbers for draft proposals, and you = generally have years of experimentation.

Best,=
Antoine

PS: By the way, even at the Uni= ted Nations, unanimity is not the rule, it's two-third of the general a= ssembly. I think your analogy is not valid.

Le=C2=A0sam. 30 mars 2024 = =C3=A0=C2=A011:52, Michael Folkson <michaelfolkson@gmail.com> a =C3=A9crit=C2=A0:
> In a world where both Core and BIP repository are living u= nder a single Github organization, I don't think in matters that much a= s the highest privilege account will be able to
override any BIP merging decision, or even remove on the flight BIP
editors rights in case of conflicts or controversies. If you're
raising the issue that the BIP repository should be moved to its own
GH repository I think it's a valuable point.

In the past there have been disagreements between Core maintainers and
BIP editors (e.g. Luke with Taproot activation params) and those Core
maintainers haven't merged pull requests in the BIPs repo or removed him as a BIP editor. As long as that continues it isn't necessary to create a new GitHub organization for the BIPs repo. They are separate
repos with different maintainers/editors but under the same
organization and everyone knows where it is located.

> Beyond, I still think we should ensure we have a wider crowd of geogra= phically and culturally diverse BIP editors. As if the role is ensuring hig= h-quality and readability of the terminology of the standards, we might hav= e highly-skilled technical BIP champions which are not English native. With= the current set of proposed BIP editors, to the best of my knowledge, at l= east we have few langages spoken by the candidates: Dutch, French, German, = Spanish. This can be very helpful to translate concepts devised in language= A to technical english.

It seems like you want to create some kind of United Nations for the
BIP process. As I said previously this is almost entirely an
administrative task. Going to a committee of 10 people with different
nationalities and languages to decide whether something should get a
BIP number is absurd. If you think Luke is slow to respond wait until
your United Nations of the BIP process has to all agree to assign a
BIP number. Please don't try to make this unnecessarily bureaucratic and political for no reason. There's enough of that outside of
Bitcoin.

On Fri, Mar 29, 2024 at 9:14=E2=80=AFPM Antoine Riard <antoine.riard@gmail.com>= wrote:
>
> > Roasbeef's work on alternative clients and lightning make him= technically
> useful
>
> I think one of the aim of the BIP process is to harmonize common mecha= nisms among Bitcoin clients of different langages breeds or at different la= yers (wallet / full-node).
> Having someone among BIP editors with a proven track record of contrib= uting to other full-node codebase beyond C++ can be valuable in that sense.=
> Especially for all matters related to compatibility and deployment. >
> > For example I think Jon Atack would make a great Core maintainer = at some point in the future and I'm not sure a BIP editor should also b= e a Core maintainer given the
> > independence sometimes required between Core and the BIP process<= br> >
> In a world where both Core and BIP repository are living under a singl= e Github organization, I don't think in matters that much as the highes= t privilege account will be able to
> override any BIP merging decision, or even remove on the flight BIP ed= itors rights in case of conflicts or controversies. If you're raising t= he issue that the BIP repository should be moved to its own GH repository I= think it's a valuable point.
>
> Beyond, I still think we should ensure we have a wider crowd of geogra= phically and culturally diverse BIP editors. As if the role is ensuring hig= h-quality and readability of the terminology of the standards, we might hav= e highly-skilled technical BIP champions which are not English native. With= the current set of proposed BIP editors, to the best of my knowledge, at l= east we have few langages spoken by the candidates: Dutch, French, German, = Spanish. This can be very helpful to translate concepts devised in language= A to technical english.
>
> Best,
> Antoine
>
>
> Le vendredi 29 mars 2024 =C3=A0 12:33:09 UTC, /dev /fd0 a =C3=A9crit :=
>>
>> Justification:
>>
>> 1. Jon Atack: Good at avoiding controversies and technical documen= tation.
>> 2. Roasbeef: Since BIPs are not just related to bitcoin core, it&#= 39;s good to have btcd maintainer as a BIP editor.
>>
>> On Friday, March 29, 2024 at 1:47:41=E2=80=AFAM UTC+5:30 Matt Cora= llo wrote:
>>>
>>> Please provide justification rather than simply saying "I= like Bob!".
>>>
>>> Matt
>>>
>>> On 3/28/24 12:09 PM, /dev /fd0 wrote:
>>> > I support Jon Atack and Roasbeef from this list.
>>> >
>>> > On Thursday, March 28, 2024 at 6:57:53=E2=80=AFPM UTC+5:3= 0 Murch wrote:
>>> >
>>> > I just went through the thread, previously mentioned were= :
>>> >
>>> > - Kanzure
>>> > - Ruben Somsen
>>> > - Greg Tonoski
>>> > - Jon Atack
>>> > - Roasbeef
>>> > - Seccour
>>> >
>>> > And Matt just suggested me for the role. Hope I didn=E2= =80=99t overlook anyone.
>>> >
>>> > On 3/27/24 19:39, John C. Vernaleo wrote:
>>> > > That said, I would find it helpful if someone could = go through the
>>> > > thread and list all the people who've been propo= sed so people know who
>>> > > they should be thinking about.
>>> >
>>> > --
>>> > You received this message because you are subscribed to t= he Google Groups "Bitcoin Development
>>> > Mailing List" group.
>>> > To unsubscribe from this group and stop receiving emails = from it, send an email to
>>> > bitcoindev+...@googlegroups.com <mailto:bitcoindev+...@goo= glegroups.com>.
>>> > To view this discussion on the web visit
>>> > https://groups.google.com/d/msgid/bitcoindev/4c1462b7-ea= 1c-4a36-be81-7c3719157fabn%40googlegroups.com <https://groups.google.com/d/msgid/bitcoindev/4c1462b= 7-ea1c-4a36-be81-7c3719157fabn%40googlegroups.com?utm_medium=3Demail&ut= m_source=3Dfooter>.
>
> --
> You received this message because you are subscribed to the Google Gro= ups "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/f8fa1a55-644f-4cf1-b8c1-4fdef22d1869n%40googlegroups.com.



--
Michael Folkson
Personal email: michaelfolkson@gmail.com

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://gro= ups.google.com/d/msgid/bitcoindev/CALZpt%2BEU4JzbDepsu4Wz-6e0XB4VuKCqatiRnb= 1nKXe%2B%2BjF%2BRw%40mail.gmail.com.
--0000000000008216e70614e63949--