Return-Path: X-Original-To: apmail-flex-dev-archive@www.apache.org Delivered-To: apmail-flex-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7E271D539 for ; Tue, 28 May 2013 16:19:46 +0000 (UTC) Received: (qmail 40323 invoked by uid 500); 28 May 2013 16:19:46 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 39820 invoked by uid 500); 28 May 2013 16:19:45 -0000 Mailing-List: contact dev-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list dev@flex.apache.org Received: (qmail 39786 invoked by uid 99); 28 May 2013 16:19:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 16:19:43 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aharui@adobe.com designates 64.18.1.238 as permitted sender) Received: from [64.18.1.238] (HELO exprod6og122.obsmtp.com) (64.18.1.238) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 May 2013 16:19:37 +0000 Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob122.postini.com ([64.18.5.12]) with SMTP ID DSNKUaTZBEidfS5v+qgCtdoHar9LLRh7mPAn@postini.com; Tue, 28 May 2013 09:19:17 PDT Received: from inner-relay-2.corp.adobe.com ([153.32.1.52]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r4SGFwD8012618 for ; Tue, 28 May 2013 09:15:58 -0700 (PDT) Received: from nacas02.corp.adobe.com (nacas02.corp.adobe.com [10.8.189.100]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r4SG8D0w008146 for ; Tue, 28 May 2013 09:19:15 -0700 (PDT) Received: from NAMBX02.corp.adobe.com ([10.8.127.96]) by nacas02.corp.adobe.com ([10.8.189.100]) with mapi; Tue, 28 May 2013 09:18:58 -0700 From: Alex Harui To: "dev@flex.apache.org" Date: Tue, 28 May 2013 09:18:56 -0700 Subject: Re: [PROPOSAL] Swiz Framework Donation to Apache Flex Thread-Topic: [PROPOSAL] Swiz Framework Donation to Apache Flex Thread-Index: Ac5bvw5r2J0oL/N9Q56kE3awOe+ffA== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.0.121105 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org On 5/28/13 8:39 AM, "Greg Reddin" wrote: >On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga >wrote: > >> On 28 May 2013 17:33, dude wrote: >> >> > Good luck, but I'd rather see Parsley integrated into Apache Flex. >> > >> > >> >> Personally, the above response shows exactly the reason why I think >>there >> shouldn't be any >> application framework integrated into Apache Flex. Too many opinions on >> the matter... >> > >But, there's no reason we can't integrate it as a sub-project or incubate >it. If it develops a community it can become its own TLP. Greg, do you think donations like these need to have a goal of being integrated with Apache Flex or becoming its own project? Personally, I'd be ok with Apache Flex being a warehouse of all kinds of Flex-related code even if there is no active development for it. That way folks looking for the latest code can know that they can come to Apache to get a legal copy and ask questions on the mailing list that have a chance of being answered. Or do we have to commit to releasing this code on occasion? I agree with not wanting to "integrate" any application-level framework with the Apache Flex SDK releases. I don't think we want to appear to be promoting one over the other. That said, I believe somewhere in the archives, the person behind Parsley announced that he was no longer maintaining it. Maybe it could also be donated to Apache. Also, does a donation like Swiz need a whole Software Grant or is an email trail sufficient? -Alex