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 6317198FC for ; Thu, 5 Apr 2012 20:37:42 +0000 (UTC) Received: (qmail 21299 invoked by uid 500); 5 Apr 2012 20:37:41 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 21272 invoked by uid 500); 5 Apr 2012 20:37:41 -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 21262 invoked by uid 99); 5 Apr 2012 20:37:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2012 20:37:41 +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.33 as permitted sender) Received: from [64.18.1.33] (HELO exprod6og114.obsmtp.com) (64.18.1.33) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2012 20:37:31 +0000 Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob114.postini.com ([64.18.5.12]) with SMTP ID DSNKT34CdWHTlxuLHc6A1obJr/a40GfPRwKY@postini.com; Thu, 05 Apr 2012 13:37:10 PDT Received: from inner-relay-4.eur.adobe.com (inner-relay-4.adobe.com [193.104.215.14]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q35KZ2J0009129 for ; Thu, 5 Apr 2012 13:35:03 -0700 (PDT) Received: from nacas03.corp.adobe.com (nacas03.corp.adobe.com [10.8.189.121]) by inner-relay-4.eur.adobe.com (8.12.10/8.12.9) with ESMTP id q35KapYu025162 for ; Thu, 5 Apr 2012 13:37:07 -0700 (PDT) Received: from NAMBX02.corp.adobe.com ([10.8.127.96]) by nacas03.corp.adobe.com ([10.8.189.121]) with mapi; Thu, 5 Apr 2012 13:36:57 -0700 From: Alex Harui To: "flex-dev@incubator.apache.org" Date: Thu, 5 Apr 2012 13:36:53 -0700 Subject: Re: Board report, "Apache internals are starting to become a problem" ? Thread-Topic: Board report, "Apache internals are starting to become a problem" ? Thread-Index: Ac0TTmRB1kUSxRMAQFaGnosBjrbGeQAHXFef Message-ID: In-Reply-To: <689299E2-5EE5-4C73-95BB-471F7C85B97E@comcast.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-Entourage/13.11.0.110726 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 On 4/5/12 10:05 AM, "Dave Fisher" wrote: >=20 > Please, Apache is a volunteer organization. The secretary is a volunteer.= Did > you give the ASF secretary a heads up that the signature was coming and y= ou > wanted an expedited approval? I did not give the secretary advanced warning. I will in the future. Bein= g new to Apache, it isn't clear what turnaround times you can expect. I got quick response from the secretary when filing my ICLA. >=20 > How would 1000 separate SVN servers work? >=20 My half-baked thinking (and I don't really understand server-side issues) i= s that you would assign a server to flex.apache.org at it would have enough horsepower to host SVN and JIRA and a web-site. Infrastructure's job would be narrowed to backups and maintenance of the servers and answering questions, but administration would be mostly pushed to the podling. Carol practiced the import on her own SVN instance, I practiced the JIRA import o= n my own JIRA instance. We did so in order to be comfortable that what we sent to Apache would work. We learned enough to be able to do the imports ourselves if we could just have access. Thinking about it more, how are backups managed? If you have to restore something can you do it without blowing away changes in another project? I= s it really a good idea for an SVN server failure to halt every Apache project? >=20 > I think that you can certainly reword the report to indicate that delays = in > importing the large JIRA database are a concern. >=20 > The main scalability is the number of paid Infrastructure consultants. AF= AIK > this is now 3.5 people in addition to numerous volunteers. This is for 10= 0+ > TLPs and over 50 podlings. I don't think that it helps to call into quest= ion > scalability of volunteers. It helps to understand that it will always be = an > issue. >=20 > The report should focus on the podling's concerns. The IPMC can then note= that > you need attention that will help. >=20 I really think if Infra could promote Carol and/or I to be volunteers for our portion of the SVN and JIRA servers, that would be more scalable. Of course they won't do that because of the risk given that there are single instances and a mistake could take down the entire foundation. That's why = I want the message to be to consider having each podling have its own server. --=20 Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui