1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
|
Return-Path: <prayank@tutanota.de>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 7DDBCC000D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Sep 2021 12:18:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 67D61605C4
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Sep 2021 12:18:00 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001,
RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=tutanota.de
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id A5XG2a9T8zRx
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Sep 2021 12:17:59 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162])
by smtp3.osuosl.org (Postfix) with ESMTPS id 6928A6058A
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Sep 2021 12:17:59 +0000 (UTC)
Received: from w3.tutanota.de (unknown [192.168.1.164])
by w1.tutanota.de (Postfix) with ESMTP id 731CDFA01AC;
Tue, 14 Sep 2021 12:17:57 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1631621877;
s=s1; d=tutanota.de;
h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender;
bh=JCpz60HiywkNkyFQzT9v5vkj8VgKmOOOnQJA2zhoEeI=;
b=w4oRhFJCfF1VHb0dz2Javau6N3KxzGufvJaAtuOgk0r1WJBFA4DzoJCUmVJhSOMR
U4iFYfmpunsTMwjP0SCfij+WAHGCcUDXtE7ytUG8e2jdU7ZQ/vOfLAKINqvrk4cKTw8
hBhv2Y+4ZzLWnXybH/tNAIUyUqMAVcWSgNYVPYEzOATQ7sBBT2sejMjMtELuqu2MSBM
q6EYIFAD2I0D71hzpPxIMAnaz+chgVt+XQEpmt2NfijhIdqMt3ySz4mlG36D3cxait2
MSD9VqOk0NbGGNAvSBu05WABuq/Awpo14GCCAt3TfpO+xf8GyCtQj3ViRgBikgc6+OG
afUfinjNGA==
Date: Tue, 14 Sep 2021 14:17:57 +0200 (CEST)
From: Prayank <prayank@tutanota.de>
To: Michael Folkson <michaelfolkson@gmail.com>
Message-ID: <MjZEVeZ--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_666610_3359306.1631621877457"
X-Mailman-Approved-At: Tue, 14 Sep 2021 12:20:28 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP process meeting - Tuesday September 14th
23:00 UTC on #bitcoin-dev Libera IRC
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, 14 Sep 2021 12:18:00 -0000
------=_Part_666610_3359306.1631621877457
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi Michael,
Thanks for sharing the details about the meeting.
Wishlist has some interesting points. I would like to suggest few things:
1.BIP process:=20
A. Plan and document a proposal
B. Open PR in=C2=A0https://github.com/bitcoin/bips and edit everything pro=
perly
C. BIP is assigned a number and merged
D. Share the proposal on bitcoin dev mailing list
bitcoin-dev mailing list link can be considered a BIP and saved in a BIP di=
rectory. Anyone can create such directories. So BIP is nothing but a propos=
al shared on bitcoin-dev mailing list.
Who implements the BIP? When is it implemented? How is it implemented? Opin=
ions on proposal etc. will be different for each BIP. This will avoid the '=
bitcoin/bips' repository being considered as some BIP authority that approv=
es BIPs and proposals can improve Bitcoin without using the repository. Rep=
ository will only be helpful in documenting BIP correctly.
2. Bot in `bitcoin/bips` repository that notifies about pull requests based=
on different things. This will help maintainer(s) and contributors.
3. BIP Gallery: I tried sharing things in a different way so that newbies c=
an understand importance of BIPs in Bitcoin and relate to it:=C2=A0https://=
prayank23.github.io/BIPsGallery/=C2=A0however couldn't complete it with all=
the BIPs because not many people considered it helpful. There were few sug=
gestions to improve it by adding some text for each BIP and better image ga=
llery. Maybe someone else can create a better project.=C2=A0
--=20
Prayank
A3B1 E430 2298 178F
------=_Part_666610_3359306.1631621877457
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=3DUTF-8=
">
</head>
<body>
<div>Hi Michael,<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">Tha=
nks for sharing the details about the meeting.<br></div><div dir=3D"auto"><=
br></div><div dir=3D"auto">Wishlist has some interesting points. I would li=
ke to suggest few things:<br></div><div dir=3D"auto"><br></div><div dir=3D"=
auto">1.BIP process: <br><br>A. Plan and document a proposal<br></div><div =
dir=3D"auto"><br></div><div dir=3D"auto"> B. Open PR in https://github=
.com/bitcoin/bips and edit everything properly<br></div><div dir=3D"auto"><=
br></div><div dir=3D"auto"> C. BIP is assigned a number and merged<br></div=
><div dir=3D"auto"><br></div><div dir=3D"auto"> D. Share the proposal on bi=
tcoin dev mailing list<br></div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">bitcoin-dev mailing list link can be considered a BIP and saved in a BIP=
directory. Anyone can create such directories. So BIP is nothing but a pro=
posal shared on bitcoin-dev mailing list.<br></div><div dir=3D"auto"><br></=
div><div dir=3D"auto">Who implements the BIP? When is it implemented? How i=
s it implemented? Opinions on proposal etc. will be different for each BIP.=
This will avoid the 'bitcoin/bips' repository being considered as some BIP=
authority that approves BIPs and proposals can improve Bitcoin without usi=
ng the repository. Repository will only be helpful in documenting BIP corre=
ctly.<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">2. Bot in `bit=
coin/bips` repository that notifies about pull requests based on different =
things. This will help maintainer(s) and contributors.<br></div><div dir=3D=
"auto"><br></div><div dir=3D"auto">3. BIP Gallery: I tried sharing things i=
n a different way so that newbies can understand importance of BIPs in Bitc=
oin and relate to it: https://prayank23.github.io/BIPsGallery/ ho=
wever couldn't complete it with all the BIPs because not many people consid=
ered it helpful. There were few suggestions to improve it by adding some te=
xt for each BIP and better image gallery. Maybe someone else can create a b=
etter project. <br></div><div dir=3D"auto"><br></div><div><br></div><d=
iv>-- <br></div><div>Prayank<br></div><div><br></div><div dir=3D"auto">A3B1=
E430 2298 178F<br></div> </body>
</html>
------=_Part_666610_3359306.1631621877457--
|
