public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: John Smith <witchspace81@gmail.com>
To: Matt Corallo <bitcoin-list@bluematt.me>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] The forums...
Date: Sat, 16 Jul 2011 11:07:02 +0000	[thread overview]
Message-ID: <CAJNQ0st1hv4k-11EHOPDqkkXCGQh41ysKhUmT6qgLu8uaGng=Q@mail.gmail.com> (raw)
In-Reply-To: <1310813679.2195.0.camel@Desktop666>

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

On Sat, Jul 16, 2011 at 10:54 AM, Matt Corallo <bitcoin-list@bluematt.me>wrote:

> If we had the moding power, yes, but we don't have nearly enough people
> who could mod such a forum.
>


I think a simpler forum would also be easier to moderate. Main criterion: is
it helpful to users? If not, lock/remove it.

Two categories: Technical Support, Development (which can be split up
between client work, and other software/websites integrating bitcoin).

Those two can be replicated per language if a large enough group exists in
that country that is also willing to maintain order.

I have no problems with volunteering some time moderating, but not on the
current forums.

If this is really a capacity issue then IMO we should simply remove the link
and come up with an alternative medium to address user issues (such as a
moderated mailing list).  But I don't really believe this. There's a ton of
successful forums that did pick the right structure and helpful moderators,
and a lot of them are volunteer-driven.

JS

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

  reply	other threads:[~2011-07-16 11:07 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 [this message]
2011-07-16 11:20     ` John Smith
2011-07-16 23:35       ` Jeff Garzik
2011-07-17  1:16         ` Douglas Huff
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='CAJNQ0st1hv4k-11EHOPDqkkXCGQh41ysKhUmT6qgLu8uaGng=Q@mail.gmail.com' \
    --to=witchspace81@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=bitcoin-list@bluematt.me \
    /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