Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B5C4EDFC9 for ; Mon, 18 Jun 2012 14:37:56 +0000 (UTC) Received: (qmail 15315 invoked by uid 500); 18 Jun 2012 14:37:56 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 15240 invoked by uid 500); 18 Jun 2012 14:37:56 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 15232 invoked by uid 99); 18 Jun 2012 14:37:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jun 2012 14:37:55 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.160.175] (HELO mail-gh0-f175.google.com) (209.85.160.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jun 2012 14:37:47 +0000 Received: by ghbz2 with SMTP id z2so3367550ghb.6 for ; Mon, 18 Jun 2012 07:37:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:content-type:x-gm-message-state; bh=VuNafQcM+7pVbK5YFtmsFHXjewxRzi9oDjk3drzncrU=; b=Q3PdWDozLRyZ1m9Hjuw+UZ5f9l/Hvg883ZauApkfGaHQCdZN7e+2xp/b29LILy6oGz mDwi0akI9KG4rc7CMgrkQFpr/SxMuoJ2YaBfmeRWgf06sXhRVfCnJ+GkARm9xoaa9fdF R+SInKCWgDnYrsQt+XG2Vrh8zrvUO5nBAXb/VJKXPL0T/5MfjM2UClqtWnzOyYmiRWoW yCq5TMzgiF4x1sNtaGKXLg5FC3/KnRcHV4pKXweXOJ8TbmHntnS1CvIV/Oi7IJpFCgJa 7FML7tiBi1ta3ga+7zIA8V+9yb1mOsrTw+aKLFZT+4fp3MuUiZPfOB5ib/037ehRSzuq sA/A== Received: by 10.50.159.135 with SMTP id xc7mr790389igb.9.1340030246117; Mon, 18 Jun 2012 07:37:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.129.98 with HTTP; Mon, 18 Jun 2012 07:36:52 -0700 (PDT) X-Originating-IP: [69.181.218.197] In-Reply-To: References: From: Doug McCune Date: Mon, 18 Jun 2012 07:36:52 -0700 Message-ID: Subject: Re: What is on-topic? Was: Painful story... To: flex-dev@incubator.apache.org Content-Type: multipart/mixed; boundary=14dae9399de1cedfc804c2c01aff X-Gm-Message-State: ALoCoQkn6foNSWJgbfoo/Jw5xEhUv8VmMdz/SUo+gBA2PnYMpYa/GdxAfjjfUGgJdS3ez+lIsINq --14dae9399de1cedfc804c2c01aff Content-Type: multipart/alternative; boundary=14dae9399de1cedfbc04c2c01afd --14dae9399de1cedfbc04c2c01afd Content-Type: text/plain; charset=ISO-8859-1 > > This is a fairly high-traffic list. This has come up in many people's discussions over the past few days. It used to be true, it's not anymore [1]. For better or worse, the mailing list activity has died down incredibly. If you are using an email client that groups by thread, there are *very* few topics being discussed at the moment. I count a total of 34 threads being discussed in the last week. That's not to say that 34 conversations isn't a decent bunch, but it takes all of about 30 seconds to scan the headlines for an entire week of content and figure out if any of it is interesting to you. And then of course there's the flex-users list, which has never been used, as in not a single message [2]. I think getting flex-users going would be great, but let's be honest about the fact that this is the *only* active Apache Flex list/forum/whatever at the moment. Telling people to go post their topics in the echoing silence of the flex-users list, which for all intents and purposes isn't alive, seems a bit silly. So yes, by all means let's get the Flex uses list going, but in the meantime, given the declining traffic on this list, the stalled progress of the project as a whole, and the fact that nearly all the current discussion is focused on infrastructure/build stuff, does it really do so much harm to have a few extra conversations here? [1] see attachment [2] http://markmail.org/search/+list:org.apache.incubator.flex-users --14dae9399de1cedfbc04c2c01afd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
This is a fairly = high-traffic list.=A0

This has come up in m= any people's discussions over the past few days. It used to be true, it= 's not anymore [1]. For better or worse, the mailing list activity has = died down incredibly. If you are using an email client that groups by threa= d, there are *very* few topics being discussed at the moment. =A0I count a = total of 34 threads being discussed in the last week. That's not to say= that 34 conversations isn't a decent bunch, but it takes all of about = 30 seconds to scan the headlines for an entire week of content and figure o= ut if any of it is interesting to you.

And then of course there's the flex-users list, whi= ch has never been used, as in not a single message [2].=A0I think getting f= lex-users going would be great, but let's be honest about the fact that= this is the *only* active Apache Flex list/forum/whatever at the moment. T= elling people to go post their topics in the echoing silence of the flex-us= ers list, which for all intents and purposes isn't alive, seems a bit s= illy.=A0

So yes, by all means let's get the Flex uses list g= oing, but in the meantime, given the declining traffic on this list, the st= alled progress of the project as a whole, and the fact that nearly all the = current discussion is focused on infrastructure/build stuff, does it really= do so much harm to have a few extra conversations here?

[1] see attachment
--14dae9399de1cedfbc04c2c01afd-- --14dae9399de1cedfc804c2c01aff--