Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAGw=_twPUgzcS0TRrAEMYEeKF0gM5N7a6zu96xq8ixktTxhOrQ@mail.gmail.com>
References: 
 <CAAnCuG8v2hBwYjvHpZyKr2QwviLtcs7QoNC5YpWvqFB-udBEbw@mail.gmail.com>
	<CAGw=_twPUgzcS0TRrAEMYEeKF0gM5N7a6zu96xq8ixktTxhOrQ@mail.gmail.com>
Date: Mon, 18 Jun 2012 09:23:55 -0400
Message-ID: 
 <CALorpXf9ds0H9tDZxNowBh4Dpp2Kkh8ym_eQ1jg0zC4uwhdgdw@mail.gmail.com>
Subject: Re: What is on-topic? Was: Painful story...
From: Nicholas Kwiatkowski <nicholas@spoon.as>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=000e0cdf90f2eb500904c2bf13b7

--000e0cdf90f2eb500904c2bf13b7
Content-Type: text/plain; charset=ISO-8859-1

This "Flex-Dev" list is specifically for the creation, maintenance and
advancement of the Apache Flex SDK and associated tools.  We've been pretty
lax about the discussions allowed on here up to now (more to foster the
community, etc), but in the future, you can expect us to ask more
discussions to other lists.

The "Flex-Users" list is for users of the Apache Flex SDK.  This includes
help on building applications, intro topics, and general banter.

The reason for the separation is so that the general public (those who are
not compiler hackers, etc), don't get bothered by very intricate details on
how the framework works, along with the opposite, so those of us who want
to concentrate on the bits and pieces of the SDK don't get a bunch of "Help
me make a hello world app" messages.

Both lists are open to the public, and anybody can post to them.  But in
order to manage the traffic, we do have two lists for very specific
purposes.

-Nick Kwiatkowski
 Apache Flex PPMC
 quetwo@apache.org

On Mon, Jun 18, 2012 at 5:47 AM, Alain Ekambi
<jazzmatadazz@googlemail.com>wrote:

> Who exactly  decides what s appropritate and what s not ?
> If  one dont like a given  topic  she should just ignore it.
> Simple s that.
> Personally I dont like the idea of telling people what and where they
> should or should not write stuff.
>
> 2012/6/18 John Fletcher <fletchgqc@gmail.com>
>
> > 2012/6/15 Jeffry Houser <jeffry@dot-com-it.com>:
> > >
> > >  I don't believe I was being unfriendly.  This is mailing list
> explicitly
> > > related to building the Apache Flex SDK.  Your experiences / pains on
> > > building HTML apps has no place here.
> >
> > +1 Jeffry.
> >
> > No-one is trying to attack the OP nor the ensuing participants in the
> > discussion, so let's take out the personal side. Questioning what is
> > appropriate content for this mailing list is valid.
> >
> > It's fair to say that there were many such discussions on this list
> > about 3-6 months ago, for example discussions along the lines of "Is
> > Flex dead?" Initially I was interested but later I almost unsubscribed
> > a number of times. I just want to be kept up to date with the main
> > points of development like the JIRA import, 4.8 release, how to
> > compile and run the latest apache Flex version, how to contribute,
> > general direction and feelings of the development team. To solve my
> > own problem I even almost suggested a "dev announcements" list or
> > similar where people like me could hear about the important stuff and
> > none of the fluff. What kept me subscribed is the fact that in the
> > last few months I felt the conversation increasingly narrowing to the
> > critical points and there was less of the sideline discussion. But how
> > many others like me have already unsubscribed?
> >
> > This is a fairly high-traffic list. We want to attract the maximum
> > amount of people who are really interested in contributing to
> > subscribe, because I think people that are subscribed are more likely
> > to contribute and in particular are more likely to contribute quality
> > because they are in touch with the latest info. But the high-traffic
> > nature of the list is discouraging to people whose time is short
> > and/or valuable. The best way to solve this is to keep the content
> > highly focussed.
> >
> > What is the stated purpose of this list? Currently: "This is where the
> > project community hangs out. This list is used to coordinate
> > activities and ensure we are all pulling in the same direction. This
> > is a high traffic list." This description is quite vague (particularly
> > the first sentence) and therefore permits the post that kicked off
> > this discussion. I would recommend tightening this description. And
> > the easist way to enforce it is to have a specific place to send the
> > non-conforming discussions. Since we have a "Flex Users" list with an
> > even more permissive description (essentially "to discuss Flex"), this
> > would seem like the ideal place to redirect discussions which don't
> > fit our tight description.
> >
> > If people would like to participate in discussions about Flex
> > development AND Flex in general, then they can subscribe to both
> > lists. If not, just subscribe to one. Everyone is happy.
> >
> > John
> >
>

--000e0cdf90f2eb500904c2bf13b7--