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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1RXCxY-0007Iv-W3
for bitcoin-development@lists.sourceforge.net;
Sun, 04 Dec 2011 14:22:28 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([173.242.112.54])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1RXCxT-0005Qc-L1 for bitcoin-development@lists.sourceforge.net;
Sun, 04 Dec 2011 14:22:28 +0000
Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net
[184.4.160.40]) (Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id 02650204298;
Sun, 4 Dec 2011 14:22:18 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Sun, 4 Dec 2011 09:22:11 -0500
User-Agent: KMail/1.13.7 (Linux/3.1.0-gentoo; KDE/4.6.5; x86_64; ; )
References: <CAJNQ0ssW4od3tA5vdASEs4KxZ7-UsxEjWT7NSc0dcWEzrkcH9w@mail.gmail.com>
In-Reply-To: <CAJNQ0ssW4od3tA5vdASEs4KxZ7-UsxEjWT7NSc0dcWEzrkcH9w@mail.gmail.com>
X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583
X-PGP-Key-ID: 665FC11DD53E9583
X-PGP-Keyserver: x-hkp://subkeys.pgp.net
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201112040922.13744.luke@dashjr.org>
X-Spam-Score: -1.2 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1RXCxT-0005Qc-L1
Subject: Re: [Bitcoin-development] Closing issues on github
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: Sun, 04 Dec 2011 14:22:29 -0000
On Sunday, December 04, 2011 5:24:08 AM John Smith wrote:
> I've also closed some issues that deal purely with Wx UI issues like this
> one:
>
> https://github.com/bitcoin/bitcoin/issues/425
>
> I think my statement is valid, that we no longer support the old UI? Or
> maybe some people want to take up maintenance of the old UI?
I think it would be ideal if someone wanted to take up wxBitcoin. Maybe after
backporting to wx 2.8...
That being said, I have no interest, as I hate wx, and prefer Qt in general ;)
> I don't think that has very high priority, and should probably not be in the
> main project.
Please be careful to avoid the centralization mindset. There is no "main
project"; there is bitcoind, wxBitcoin, Bitcoin-Qt, MultiBit, and many other
non-functional clients, which should be given equal footing (before
considering their differences). There shouldn't be given any special treatment
to bitcoind and Bitcoin-Qt just because "Gavin et al" happen to maintain it.
> Some of the older issues are absolutely still relevant, but 150+ open
> issues is not something to be proud of, and I wonder how other open source
> projects deal with this without too much stepping on people's toes :-)
KDE literally just closed a bug of mine that I reported in 2002, because the
component with the bug hasn't been part of KDE since 2008.
|
