Delivery-date: Sat, 30 Mar 2024 14:13:31 -0700 Received: from mail-qt1-f189.google.com ([209.85.160.189]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rqg15-00008Y-6i for bitcoindev@gnusha.org; Sat, 30 Mar 2024 14:13:31 -0700 Received: by mail-qt1-f189.google.com with SMTP id d75a77b69052e-430c139c096sf29692091cf.3 for ; Sat, 30 Mar 2024 14:13:30 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1711833204; cv=pass; d=google.com; s=arc-20160816; b=jGIM7gRUA/en/1dWR2z2OUOGRUwnGCOoT3T6YVUc24KRiz7iphOymFcamw10LJRvNT ogi4/VfYtjQHW29PGmPVfYNOPRHn+Z+/t6+F/7ELMBptZS6zRMYXvhd3cvV/oOo5LvQg U72jOKasvgFTf33Htbo8KbxqZti2RWB38uDVFtJkRvafJWUP+xAfIjplxtOAcIr17OZS 9LhSXL6wqhe3/FXBlW6Ip0mOvdgHwdpzne5zXyd/PWNcpYph/k7d8uFTxqY/eJ8cYWoU SHQDBNtpPs8crvSLLeBzkLUF25/Jolly7g4lnLxOmhPn3HnajVJMoRQ8WEU0WAaz8Qxr ulaQ== 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:content-transfer-encoding:cc:to :subject:message-id:date:from:in-reply-to:references:mime-version :sender:dkim-signature:dkim-signature; bh=IW8Z30hFiqg1ArRCfcbl0+yxWaJOS+GfhA7Oe1I5ZVE=; fh=aLk1xK3mTa4Utd/nC7oz1IZcnts+yIfGBpVKp8ePNks=; b=chhNUnCTWQv0K8ShZO2wMzvQCXi3qgmw8QXZ0n1/b2DsvcZypXZf4x5nxr50PyuXzx xh8aPqJRh3VOtVq2Gv50Y3L29MNgp7wngVXO99IOsCzhdCb2rlEEYyyVyO9KsMk748ps gIf6jZcebXwuan6wST0htKQJycRBmdABeZJu+kBx0aBmha2dkp73RiStJvGVYCC7bm6y M2IMsuBF6QjsAKxhZma0agE8KC+DSQST63Z4AA1RkHXiPmb+3bU9FucaJshtWXNURIMV mDjhIW6asdCspkVgqhsPwv21mHRO11A8c6XvN04LwJlVpq5/Cb3/Y/XkVNkOIWzR+ACj MZHQ==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=kvLoR22s; spf=pass (google.com: domain of michaelfolkson@gmail.com designates 2a00:1450:4864:20::131 as permitted sender) smtp.mailfrom=michaelfolkson@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=1711833204; x=1712438004; 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:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version:sender :from:to:cc:subject:date:message-id:reply-to; bh=IW8Z30hFiqg1ArRCfcbl0+yxWaJOS+GfhA7Oe1I5ZVE=; b=fhGv2LsJXbn3pSssesgPtj59lT0nwS4aWIVumTJvtxk74crLi/JX6WpoZ4Zj0okkmJ TmsxYyL6zwmuH8pEdQq8/7qR5sOp511/CV2MrAnd1Gl/234dn0yEzzD+eI64UNErdVH6 HUVc0o2AcOu6tqHTGW5u+R/0XojCoR++TTqXJqvZqPXJjiedU7PU7aaI+l3E3StmXl03 fB49Qacxure8bA1wllVB7Ko8H1srVZtprOd4aDkHpIIMorFrgcBFHr2rPcW/eUkn8cES JCfOPzZLRyIz3mrMNRBL1TT0OM52Y8355djhS9LdiKfEfEnLaOq/klCApzxRSgdOWlFX jvFQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711833204; x=1712438004; 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:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version:from:to:cc :subject:date:message-id:reply-to; bh=IW8Z30hFiqg1ArRCfcbl0+yxWaJOS+GfhA7Oe1I5ZVE=; b=ejfYa8U2rhwhrYK5DjopU343Xs5IFf81zmkAB0jJqkGgUB5Uq/h18lkg1liM6LDOI6 vhSvPtvMwWsvIHA0X0kPliJ0lYzRWH/EgYGVj9Y2kqsgy6R6KbNkHyXi2DoeA+VUDSKe RmjecDNxOc9HmWCxfLxstipdFngd6FzgawNTnnOVEW8F3ypuvwIdCqBdgmktLEP/5hvc YjyO3g/g80RfHCMs8ixW3GezXA2WHt5d/oQBhsGATUdGIyRzvmVif0vUwHVJ2REZ7gsI rQ7adjX4vOQaBIg1EfPgXlLYK/qX2liLjBKZTfROCjqTA7tVemLO1BUu5MrwZPOYzMir fYgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711833204; x=1712438004; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-transfer-encoding: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=IW8Z30hFiqg1ArRCfcbl0+yxWaJOS+GfhA7Oe1I5ZVE=; b=MwJMaPPFlFGpU+zei+j7Imd9OnvaN5hULVQ98Astm95eHIzRMX7dkP4Buf4Urb/qS/ Vd0I3JDWpaZ9IB0y0pcDeFFgzEAU7ZdIADZVzTRSdBQSaAjcka7JGc3ruQGA5ziyyc6c QujvVphJtEThZTImx0OBxTkkJmEBXq86yYOVwf0EazVkH2hqr9S5Vh48rR/kL3qaKaxy d6dVvHSlwpGXV142cQc96xlqXtsycWGJIXsitFqXc5mNqgatbqSe4P8310dEjAQcBUaF kJf0cY5im4jF5nI/NmjTc0SokUt5nT8zEiFaC/cSd57rjubZ96hsuMKPJTCuXbpSUoMZ /GqA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=2; AJvYcCXwgNwIrGubImkiXBlTM9aYS8Evpw3JiQWM9Yn2R+pLOmzkMc/grQMzv5Ow8ChzYl587Hn230RmwekMTV8IUiwtRbEYqvE= X-Gm-Message-State: AOJu0YxGk14EwjuGN+T7iv1gFa554yx+cLEy2O6MYQlAfbz6yIsYcP9N umyV/0ULCBgkDsYb5vLa166T7vdZvYkmTqVVKdZUK4FS8uO9AKg5 X-Google-Smtp-Source: AGHT+IGMCAvY4KeohN7hAsPWuJ9ADZJJtuMkjmRmCkxYaVZym/08FwImLxsieuo+KHm3bRAy18s+Zg== X-Received: by 2002:ac8:7e83:0:b0:432:a563:cdaa with SMTP id w3-20020ac87e83000000b00432a563cdaamr5947817qtj.32.1711833204230; Sat, 30 Mar 2024 14:13:24 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a05:622a:1886:b0:431:7333:7aea with SMTP id v6-20020a05622a188600b0043173337aeals4021649qtc.1.-pod-prod-06-us; Sat, 30 Mar 2024 14:13:23 -0700 (PDT) X-Received: by 2002:a05:620a:46a5:b0:78b:c211:b18e with SMTP id bq37-20020a05620a46a500b0078bc211b18emr80284qkb.1.1711833203114; Sat, 30 Mar 2024 14:13:23 -0700 (PDT) Received: by 2002:a05:620a:4107:b0:78a:4f40:42f5 with SMTP id af79cd13be357-78bc5b58a94ms85a; Sat, 30 Mar 2024 04:52:05 -0700 (PDT) X-Received: by 2002:a05:6512:a95:b0:516:9fdc:2621 with SMTP id m21-20020a0565120a9500b005169fdc2621mr852979lfu.0.1711799523460; Sat, 30 Mar 2024 04:52:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1711799523; cv=none; d=google.com; s=arc-20160816; b=y/AXy7qoX2wyJBDzJbDZ9o7W1AcrLZTir6tE8qSkmeeyjF8bbHa5dgWnnAPwNpdnbq JKo/oYQUJPBaqy9EXhAs9mVVUzU7PIBdzlMEDisjr77zc/YqMrTehXdfMvjJVaWGo1yY GkPyZkGnxvQ6qkjLJjDOYFc4hMQntttgNZ0kugfPbSs/IWCHB2o6dwsVk+a225N1soRZ MsgaFLB+/of3PEmu3SvP9hWevHozZZaGHa96IJxwIlcW+EyWUgkxp9KKQjoaHXF/tERt tPCbmROPhjXzBF0MVINBm80kjmKWw9iKb8oklqvfkme3x/s03pyOodEBZ/XbDQLGsPbc CpJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=IMWi5Op8nz1K7fTzi41TAa1nU9gQUR8Aes+QETzzVHw=; fh=sapDHqhE46zLmMBeB1lkoe0zq8J9+V3Afx71/j8kvug=; b=W0YVuJmd7fkqq2J+xZHjfwNxR+0pZsWrp2quaO2wIopnYoQnITiKotIrJRmQzvKnuT 8zv0Xk+m/Ehms0sM62d3TwCndeAW75RqqhwTMzr8PZIOS4gYXIvbdNEq0hfVPF4Zw4Sf 7V8hc96mRgkOwlR2b08b2q/sE0PlpTwrQVLSb2sGHcUwwdceER/7u1eCvv2YFc3XYAuq 2ApE3SOrEUCDr81b8yO54z4FXfhKOPFfVMjs8SMlR4G4dTxB5/dusHFVCdQS1jmXtSYZ BVZ9snG2CpIPUwHfvHXUAPA1hVGlL51c6+ILqfSySuYTK4XAN23ps76nKqyYEkQCvGpy 6HdQ==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=kvLoR22s; spf=pass (google.com: domain of michaelfolkson@gmail.com designates 2a00:1450:4864:20::131 as permitted sender) smtp.mailfrom=michaelfolkson@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com. [2a00:1450:4864:20::131]) by gmr-mx.google.com with ESMTPS id br38-20020a056512402600b00515aa2b9262si163303lfb.2.2024.03.30.04.52.03 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 30 Mar 2024 04:52:03 -0700 (PDT) Received-SPF: pass (google.com: domain of michaelfolkson@gmail.com designates 2a00:1450:4864:20::131 as permitted sender) client-ip=2a00:1450:4864:20::131; Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-515c3eeea5dso2930873e87.1 for ; Sat, 30 Mar 2024 04:52:03 -0700 (PDT) X-Received: by 2002:a05:6512:3ba9:b0:515:b83e:88bd with SMTP id g41-20020a0565123ba900b00515b83e88bdmr3894732lfv.63.1711799522718; Sat, 30 Mar 2024 04:52:02 -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: Michael Folkson Date: Sat, 30 Mar 2024 11:51:51 +0000 Message-ID: Subject: Re: [bitcoindev] Re: Adding New BIP Editors To: Antoine Riard Cc: Bitcoin Development Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Original-Sender: michaelfolkson@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=kvLoR22s; spf=pass (google.com: domain of michaelfolkson@gmail.com designates 2a00:1450:4864:20::131 as permitted sender) smtp.mailfrom=michaelfolkson@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 (/) > In a world where both Core and BIP repository are living under a single G= ithub organization, I don't think in matters that much as the highest privi= lege 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 geographi= cally and culturally diverse BIP editors. As if the role is ensuring high-q= uality and readability of the terminology of the standards, we might have h= ighly-skilled technical BIP champions which are not English native. With th= e current set of proposed BIP editors, to the best of my knowledge, at leas= t we have few langages spoken by the candidates: Dutch, French, German, Spa= nish. 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 technical= ly > useful > > I think one of the aim of the BIP process is to harmonize common mechanis= ms among Bitcoin clients of different langages breeds or at different layer= s (wallet / full-node). > Having someone among BIP editors with a proven track record of contributi= ng 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 som= e point in the future and I'm not sure a BIP editor should also be a Core m= aintainer 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 G= ithub organization, I don't think in matters that much as the highest privi= lege account will be able to > override any BIP merging decision, or even remove on the flight BIP edito= rs rights in case of conflicts or controversies. If you're raising the issu= e 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 geographi= cally and culturally diverse BIP editors. As if the role is ensuring high-q= uality and readability of the terminology of the standards, we might have h= ighly-skilled technical BIP champions which are not English native. With th= e current set of proposed BIP editors, to the best of my knowledge, at leas= t we have few langages spoken by the candidates: Dutch, French, German, Spa= nish. 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 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 Corallo wr= ote: >>> >>> 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 wrot= e: >>> > >>> > 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 overlo= ok 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 proposed so people know = who >>> > > they should be thinking about. >>> > >>> > -- >>> > You received this message because you are subscribed to the Google Gr= oups "Bitcoin Development >>> > Mailing List" group. >>> > To unsubscribe from this group and stop receiving emails from it, sen= d an email to >>> > bitcoindev+...@googlegroups.com . >>> > To view this discussion on the web visit >>> > https://groups.google.com/d/msgid/bitcoindev/4c1462b7-ea1c-4a36-be81-= 7c3719157fabn%40googlegroups.com . > > -- > 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/msgi= d/bitcoindev/f8fa1a55-644f-4cf1-b8c1-4fdef22d1869n%40googlegroups.com. --=20 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/CAFvNmHQiXFbjMxHWeWYb4J5TDDpYT0o4CexYdcOjrUAaCt4f6w%40mail.gmail= .com.