public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Closing issues on github
Date: Sun, 4 Dec 2011 16:31:01 +0100	[thread overview]
Message-ID: <CA+s+GJB197G+NaRgxG0VbUdbLS=SdoYjdmtaApQiALvn=+n73g@mail.gmail.com> (raw)
In-Reply-To: <201112040922.13744.luke@dashjr.org>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

>
>
> I think it would be ideal if someone wanted to take up wxBitcoin. Maybe
> after
> backporting to wx 2.8...
>

Indeed, someone could do this if they're interested in it, in their own
fork. That's what I said too. But it's no longer our issue.


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


With the "main project" here I mean the issue list of bitcoin/bitcoin
project on github, which only deals with that project (and not that of the
forks, which have their own issue lists). You can argue the "main"-ness but
it's just a mailing list message and not some official document deciding
about the future of bitcoin, so I did not feel like specifying it to that
level of detail.

JS

[-- Attachment #2: Type: text/html, Size: 1320 bytes --]

      reply	other threads:[~2011-12-04 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-04 10:24 [Bitcoin-development] Closing issues on github John Smith
2011-12-04 14:22 ` Luke-Jr
2011-12-04 15:31   ` Wladimir [this message]

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='CA+s+GJB197G+NaRgxG0VbUdbLS=SdoYjdmtaApQiALvn=+n73g@mail.gmail.com' \
    --to=laanwj@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=luke@dashjr.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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