public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Douglas Huff <dhuff@jrbobdobbs.org>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] The forums...
Date: Sat, 16 Jul 2011 20:16:55 -0500	[thread overview]
Message-ID: <83816D44-004A-43C4-AFFE-ED1BABD90144@jrbobdobbs.org> (raw)
In-Reply-To: <CA+8xBpduc=vn_Q7Kw0m+VkuHjz0FTxjDZB+hOPLnRJcuh49gJw@mail.gmail.com>

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

On Jul 16, 2011, at 6:35 PM, Jeff Garzik wrote:

> On Sat, Jul 16, 2011 at 7:20 AM, John Smith <witchspace81@gmail.com> wrote:
>> I know most of the people actively working on bitcoin (and active on this
>> list) ignore the forums, for good reason. But there's a lot of people
>> (everyone new?) that think the most active members of the forum have a major
>> influence on the project's direction. Which is making us as developers look
>> really bad. As if we're some political faction that wants to bring down
>> world governments and unleash a global anarchistic doomsday scenario.
>> 
>> It really needs to be more down-to-earth. Ideally, the forum would simply be
>> a way to communicate with the *actual* users. For example, I use it for
>> soliciting user feedback on UI features.
> 
> I agree completely.
> 
> While the owner of the forums and bitcoin.org is Missing In Action and
> has not responded to emails in more than a week, we do have access to
> change the main www.bitcoin.org home page, to link to another forum.
> 
> Or we could simply de-link the current forum, as a first step.

I say just kill the forum.bitcoin.org DNS entry along with it.

-- 
Douglas Huff



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 881 bytes --]

  reply	other threads:[~2011-07-17  1:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16  9:34 [Bitcoin-development] The forums John Smith
2011-07-16 10:54 ` Matt Corallo
2011-07-16 11:07   ` John Smith
2011-07-16 11:20     ` John Smith
2011-07-16 23:35       ` Jeff Garzik
2011-07-17  1:16         ` Douglas Huff [this message]
2011-07-17  2:00           ` Jeff Garzik
2011-07-17  2:12             ` Robert McKay
2011-07-17 10:46               ` Matt Corallo
2011-07-17 17:12                 ` Douglas Huff
2011-07-18  4:36                   ` John Smith
     [not found]               ` <CAJNQ0suMJAApg-fK70BBAHRT_41jc4-HMwxaHHccg0O+MOvV0A@mail.gmail.com>
2011-07-17 10:59                 ` John Smith
2011-07-17 12:30                   ` Luke-Jr
2011-07-18 20:08 Chris Acheson
2011-07-19  6:54 ` John Smith
2011-07-19 17:07 ` Chris Acheson
2011-08-12 17:32   ` Vladimir Marchenko

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=83816D44-004A-43C4-AFFE-ED1BABD90144@jrbobdobbs.org \
    --to=dhuff@jrbobdobbs.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@exmulti.com \
    /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