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>
Subject: Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
Precedence: list


--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--