path: root/17/2c8a348132e4f01bf3fe98c95681d2e214ffa4

Return-Path: <ryan@breen.xyz>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 6B7D5C0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  7 Nov 2023 22:30:18 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 1ED994023F
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  7 Nov 2023 22:30:18 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 1ED994023F
Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key,
 unprotected) header.d=breen.xyz header.i=@breen.xyz header.a=rsa-sha256
 header.s=sig1 header.b=a7WBSTOO
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.298
X-Spam-Level: 
X-Spam-Status: No, score=-0.298 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FROM_SUSPICIOUS_NTLD=0.499,
 HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, PDS_OTHER_BAD_TLD=1.999,
 RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001,
 RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
 autolearn=no autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id VxV2uhWpJ_eu
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  7 Nov 2023 22:30:17 +0000 (UTC)
X-Greylist: delayed 341 seconds by postgrey-1.37 at util1.osuosl.org;
 Tue, 07 Nov 2023 22:30:16 UTC
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org D89C040182
Received: from qs51p00im-qukt01072702.me.com (qs51p00im-qukt01072702.me.com
 [17.57.155.17])
 by smtp2.osuosl.org (Postfix) with ESMTPS id D89C040182
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  7 Nov 2023 22:30:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=breen.xyz; s=sig1;
 t=1699395874; bh=Mn7TIbCiX7R8WyXttdkEFsLwxuRvKYL4JNIW6InyH3g=;
 h=Content-Type:From:Mime-Version:Subject:Date:Message-Id:To;
 b=a7WBSTOOB4oBd+1r5ertp9rRvjND9NUF/WEP6z7PNqZFbuhKhMPzF6mJ/WEBOcL4w
 UnLy4vudTOQ/T9mYnb5Er7LeaFT4FwHIpLlvI5kwVDaLHBwcKVqhxNfgWStDwne70Y
 sq03Q/+KgwG5GraIA/KI90S3fUtoQMZLnoZyqcG6ZcaFMDztCj4UX2DWSRTwXAXU31
 ud21CVUpp9gmqsHgnmatFR9X0iKm7IMD62XKZmE/UXW51rgXXzKxaVwj7rDmZkJbbg
 X6WLP+sI8wHxh97XS3NE+3AlDRu0oVmwKF9DKvYDG+j+V1fMFohY4A7yinPpc2ybuZ
 EiM5bAXSNlaTA==
Received: from smtpclient.apple (qs51p00im-dlb-asmtp-mailmevip.me.com
 [17.57.155.28])
 by qs51p00im-qukt01072702.me.com (Postfix) with ESMTPSA id 6F66516801F2;
 Tue,  7 Nov 2023 22:24:33 +0000 (UTC)
Content-Type: multipart/alternative;
 boundary=Apple-Mail-922F3C10-97B1-4CA8-A8B3-530F0B6B5C14
Content-Transfer-Encoding: 7bit
From: Ryan Breen <ryan@breen.xyz>
Mime-Version: 1.0 (1.0)
Date: Tue, 7 Nov 2023 17:24:20 -0500
Message-Id: <2DB3414E-07CA-4D02-BA6E-96F29A0DFED3@breen.xyz>
References: <CACrqygA0+CLxfkhv2ehuQ7hYmisH60FB+CHWUyromjnyq9LyHg@mail.gmail.com>
In-Reply-To: <CACrqygA0+CLxfkhv2ehuQ7hYmisH60FB+CHWUyromjnyq9LyHg@mail.gmail.com>
To: Christopher Allen <ChristopherA@lifewithalacrity.com>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
X-Mailer: iPhone Mail (21A360)
X-Proofpoint-ORIG-GUID: QdGwu3OdCn3OlNaN_ZXIqQAopKjLVTEl
X-Proofpoint-GUID: QdGwu3OdCn3OlNaN_ZXIqQAopKjLVTEl
X-Proofpoint-Virus-Version: =?UTF-8?Q?vendor=3Dfsecure_engine=3D1.1.170-22c6f66c430a71ce266a39bfe25bc?=
 =?UTF-8?Q?2903e8d5c8f:6.0.138,18.0.790,17.0.605.474.0000000_definitions?=
 =?UTF-8?Q?=3D2022-01-12=5F02:2020-02-14=5F02,2022-01-12=5F02,2020-01-23?=
 =?UTF-8?Q?=5F02_signatures=3D0?=
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0
 clxscore=1030 spamscore=0
 phishscore=0 suspectscore=0 mlxscore=0 adultscore=0 malwarescore=0
 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1
 engine=8.12.0-2308100000 definitions=main-2311070184
X-Mailman-Approved-At: Tue, 07 Nov 2023 22:46:30 +0000
Subject: Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2023 22:30:18 -0000


--Apple-Mail-922F3C10-97B1-4CA8-A8B3-530F0B6B5C14
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

I think GitHub Discussions is a great idea. If we are considering proprietar=
y options like Google Groups, then we should definitely consider Discussions=
.

1. Guaranteed that nearly everyone participating here already has a GH accou=
nt.
2. Offers many moderation options.
3. Good formatting abilities(tables!).
4. Can @ people.
5. Ability to categorize, close, lock discussions, etc.
6. Many great potential opportunities for automation via Actions.
7. Comes with added benefits such as a wiki, issues, etc.

My one catch is that I do not know what kind of interactions you can have wi=
th Discussions via email. This seems to be an important feature for many. Wh=
at level of email notifications can you receive? Can you respond via email?

> On Nov 7, 2023, at 3:16=E2=80=AFPM, Christopher Allen via bitcoin-dev <bit=
coin-dev@lists.linuxfoundation.org> wrote:
>=20
> =EF=BB=BF
> As Bitcoin-Core already uses GitHub, another possibility is to use the new=
 GitHub discussions feature. We increasingly have been using this at Blockch=
ain Commons as everyone is using already using GitHub. We have also created s=
ome GitHub actions to backup discussions so that GitHub will not be a centra=
l point of failure -should be possible to create a static page archive using=
 GitHub pages (but have not had budget for that).
>=20
> For instance, here is the GitHub discussion area for wallet developers wor=
king together on Bitcoin wallet interoperability specifications:=20
> https://github.com/BlockchainCommons/Gordian-Developer-Community
>=20
> =E2=80=94 Christopher Allen
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

--Apple-Mail-922F3C10-97B1-4CA8-A8B3-530F0B6B5C14
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr">I t=
hink GitHub Discussions is a great idea. If we are considering proprietary o=
ptions like Google Groups, then we should definitely consider Discussions.</=
div><div dir=3D"ltr"><br></div><div dir=3D"ltr">1. Guaranteed that nearly ev=
eryone participating here already has a GH account.</div><div dir=3D"ltr">2.=
 Offers many moderation options.</div><div dir=3D"ltr">3. Good formatting ab=
ilities(tables!).</div><div dir=3D"ltr">4. Can @ people.</div><div dir=3D"lt=
r">5. Ability to categorize, close, lock discussions, etc.</div><div dir=3D"=
ltr">6. Many great potential opportunities for automation via Actions.</div>=
<div dir=3D"ltr">7. Comes with added benefits such as a wiki, issues, etc.</=
div><div dir=3D"ltr"><br></div><div dir=3D"ltr">My one catch is that I do no=
t know what kind of interactions you can have with Discussions via email. Th=
is seems to be an important feature for many. What level of email notificati=
ons can you receive? Can you respond via email?</div><div dir=3D"ltr"><br><b=
lockquote type=3D"cite">On Nov 7, 2023, at 3:16=E2=80=AFPM, Christopher Alle=
n via bitcoin-dev &lt;bitcoin-dev@lists.linuxfoundation.org&gt; wrote:<br><b=
r></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<di=
v dir=3D"auto">As Bitcoin-Core already uses GitHub, another possibility is t=
o use the new GitHub discussions feature. We increasingly have been using th=
is at Blockchain Commons as everyone is using already using GitHub. We have a=
lso created some GitHub actions to backup discussions so that GitHub will no=
t be a central point of failure -should be possible to create a static page a=
rchive using GitHub pages (but have not had budget for that).</div><div dir=3D=
"auto"><br></div><div dir=3D"auto">For instance, here is the GitHub discussi=
on area for wallet developers working together on Bitcoin wallet interoperab=
ility specifications:&nbsp;<div><a href=3D"https://github.com/BlockchainComm=
ons/Gordian-Developer-Community">https://github.com/BlockchainCommons/Gordia=
n-Developer-Community</a></div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>=E2=80=94 Christopher Allen</div></div>
<span>_______________________________________________</span><br><span>bitcoi=
n-dev mailing list</span><br><span>bitcoin-dev@lists.linuxfoundation.org</sp=
an><br><span>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev<=
/span><br></div></blockquote></body></html>=

--Apple-Mail-922F3C10-97B1-4CA8-A8B3-530F0B6B5C14--