From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Closing issues on github
Date: Sun, 4 Dec 2011 09:22:11 -0500 [thread overview]
Message-ID: <201112040922.13744.luke@dashjr.org> (raw)
In-Reply-To: <CAJNQ0ssW4od3tA5vdASEs4KxZ7-UsxEjWT7NSc0dcWEzrkcH9w@mail.gmail.com>
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.
next prev parent reply other threads:[~2011-12-04 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 10:24 John Smith
2011-12-04 14:22 ` Luke-Jr [this message]
2011-12-04 15:31 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201112040922.13744.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox