blob: f146d511372cddd6d025b287a5b4e07fb7eaadf1 (
plain)
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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <nils@nilsschneider.net>) id 1RGHBA-0000R7-3S
for bitcoin-development@lists.sourceforge.net;
Tue, 18 Oct 2011 21:26:32 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of
nilsschneider.net designates 217.11.48.105 as permitted sender)
client-ip=217.11.48.105; envelope-from=nils@nilsschneider.net;
helo=ngcobalt05.manitu.net;
Received: from ngcobalt05.manitu.net ([217.11.48.105])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1RGHB8-00041y-OT for bitcoin-development@lists.sourceforge.net;
Tue, 18 Oct 2011 21:26:32 +0000
Received: from ngcobalt05.manitu.net (localhost [127.0.0.1])
by ngcobalt05.manitu.net (8.10.2/8.10.2) with ESMTP id p9ILQQv27832
for <bitcoin-development@lists.sourceforge.net>;
Tue, 18 Oct 2011 23:26:26 +0200
X-manitu-Original-Sender-IP: 127.0.0.1
X-manitu-Original-Receiver-Name: ngcobalt05.manitu.net
Received: from [192.168.97.167] (static-ip-188-138-99-157.inaddr.ip-pool.com
[188.138.99.157]) (Authenticated sender: u8956)
by ngcobalt05.manitu.net (Postfix) with ESMTPSA id E72505B46D3
for <bitcoin-development@lists.sourceforge.net>;
Tue, 18 Oct 2011 23:26:25 +0200 (CEST)
Message-ID: <4E9DEEFE.9040301@nilsschneider.net>
Date: Tue, 18 Oct 2011 23:26:22 +0200
From: Nils Schneider <nils@nilsschneider.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CABsx9T0xjz2bO0PKX7VBka_j_MpGky9scHhkyM=b9MbtPAwx=A@mail.gmail.com>
In-Reply-To: <CABsx9T0xjz2bO0PKX7VBka_j_MpGky9scHhkyM=b9MbtPAwx=A@mail.gmail.com>
X-Enigmail-Version: 1.4a1pre
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ngcobalt05.manitu.net
id p9ILQQv27832
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1RGHB8-00041y-OT
Subject: Re: [Bitcoin-development] BIP process
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 18 Oct 2011 21:26:32 -0000
> =95 I propose that BIPs be wiki pages, with a social convention that th=
e
> Author gets final word if any editing wars break out.
That's a good idea. What about using GitHub's Wiki feature for BIPs?
They support MarkDown which is easy to read in text editors so we could
someday create a repo with all finalized BIPs. That's a lot easier than
importing a mediawiki dump. The last time en.bitcoin.it went down I
tried to setup a static mirror and that was nearly impossible without a
full LAMP stack. Also, BIPs should only contain images when absolutely
necessary.
> =95 If he's willing, I propose that Amir take the role of BIP editor.
ack
> =95 I think bitcoin is still too small to have a specialized
> "bitcoin-ideas" mailing list; I propose that new potential BIPs be
> discussed either here or on the bitcoin-dev mailing list.
ack
|
