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 72AC69CD4 for ; Thu, 19 Jan 2012 22:07:58 +0000 (UTC) Received: (qmail 12398 invoked by uid 500); 19 Jan 2012 22:07:58 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 12234 invoked by uid 500); 19 Jan 2012 22:07:57 -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 12226 invoked by uid 99); 19 Jan 2012 22:07:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2012 22:07:57 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of peter.elst@gmail.com designates 209.85.216.175 as permitted sender) Received: from [209.85.216.175] (HELO mail-qy0-f175.google.com) (209.85.216.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2012 22:07:51 +0000 Received: by qcsp14 with SMTP id p14so237126qcs.6 for ; Thu, 19 Jan 2012 14:07:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=zYZH+YKJhufyJX+xBZ/JiJm996YTCU831puSCenC0Lk=; b=Zv5/0zSDJ/LjluNVCetphHtLK0kX5tYfe8pvHNrWHeT0xFixrFSSDegPuAmKH5BULQ lIjxWZnTUHGDMLZjkFqI8OMK+xT0W+ReD43TAzcT+jRGzXkghYUhAuglMwYgdaUanBh6 abHEhr4N/EruWo+ylgxcw+9dZw7PKota5dIV8= Received: by 10.224.111.77 with SMTP id r13mr3501028qap.71.1327010850509; Thu, 19 Jan 2012 14:07:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.133.207 with HTTP; Thu, 19 Jan 2012 14:07:09 -0800 (PST) Reply-To: peter.elst@gmail.com In-Reply-To: References: <6B0DD3B4-E307-46C1-8498-8EF2DA251965@gmail.com> <9C8AE3BE-4482-42DC-92D3-0098CC632845@gmail.com> From: Peter Elst Date: Thu, 19 Jan 2012 22:07:09 +0000 Message-ID: Subject: Re: Proposal: Code Example / Application Development Procedure (was: Re: Non-core code, contrib and samples (was: Goal for Flex: Strengthening large-scale Flex applications...)) To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=20cf3074b5945b93fe04b6e8ca35 --20cf3074b5945b93fe04b6e8ca35 Content-Type: text/plain; charset=UTF-8 > The flex-dev list should be responsible for building > the "car parts" (Flex SDK). But they should not take > care which type of "car" (Flex app) we build, and, > how we'd drive that thing. > > The flex-users list should take care which type of "car" > (Flex app) we build, and, how we'd drive that thing. My personal take on this is not to turn the flex-user list into a discussion back channel, but something for users of Apache Flex releases to ask questions about specific issues related to those releases - i.e. users of software If your more involved in the development and feel the urge to discuss best practices you can talk to fellow developers active in the project rather than end users on the flex-dev list. The idea about a contrib / samples area sounds perfect IMHO. There would be actual code people can delve into rather than a back and forth on personal coding style preferences and architectural choices. - Peter --20cf3074b5945b93fe04b6e8ca35--