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 24EE09A32 for ; Mon, 11 Jun 2012 14:24:13 +0000 (UTC) Received: (qmail 19840 invoked by uid 500); 11 Jun 2012 14:24:12 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 19798 invoked by uid 500); 11 Jun 2012 14:24:12 -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 19789 invoked by uid 99); 11 Jun 2012 14:24:12 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2012 14:24:12 +0000 Received: from localhost (HELO mail-wi0-f169.google.com) (127.0.0.1) (smtp-auth username bdelacretaz, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2012 14:24:12 +0000 Received: by wibhn14 with SMTP id hn14so3230351wib.0 for ; Mon, 11 Jun 2012 07:24:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.211.131 with SMTP id w3mr6370218weo.163.1339424650334; Mon, 11 Jun 2012 07:24:10 -0700 (PDT) Received: by 10.223.81.73 with HTTP; Mon, 11 Jun 2012 07:24:10 -0700 (PDT) In-Reply-To: References: Date: Mon, 11 Jun 2012 16:24:10 +0200 Message-ID: Subject: Re: Review after first months of Apache Flex, new guidelines and keeping Flex alive From: Bertrand Delacretaz To: flex-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jun 5, 2012 at 6:54 PM, Alex Harui wrote: > On 6/5/12 7:59 AM, "Bertrand Delacretaz" wrote: >> Although the JIRA import problems need to be solved, I don't see what >> prevents people from using the existing instance at >> https://issues.apache.org/jira/browse/FLEX to go forward without >> having to wait for that.... >> I assume issues created there can be linked to existing issues in the >> Adobe Flex JIRA if that's still up, and if that's not the case we can >> fairly easily host a static copy of that somewhere so that people can >> find the required information.... > What does it take to host a static copy, and, if we can have a standalone > copy, why does it have to be static? =C2=A0I know it is a trade-off, but = having > our own JIRA instance still seems to have more pro's than con's... A static copy of the current Adobe JIRA can be hosted alongside http://incubator.apache.org/flex/ with minimal work. Hosting a dedicated JIRA instance for Flex can be done on a server or virtual machine that ASF infra would provide, but the Flex PPMC then has full responsibility for maintaining it. How's that going to work medium to long term? Who's going to be on call for maintenance issues? I hear there might be progress on INFRA-4380 after the recent JIRA upgrades, but if that doesn't happen I'm far from convinced that a dedicated instance is the right thing to do - a static copy of the Adobe JIRA would be much easier to manage IMO, and would naturally lead to forgetting about irrelevant/old issues which might actually help. -Bertrand