Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-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 F2E008DC0 for ; Tue, 13 Sep 2011 19:17:26 +0000 (UTC) Received: (qmail 44002 invoked by uid 500); 13 Sep 2011 19:17:26 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 43695 invoked by uid 500); 13 Sep 2011 19:17:24 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 43676 invoked by uid 99); 13 Sep 2011 19:17:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Sep 2011 19:17:24 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dennis.hamilton@acm.org designates 75.98.160.130 as permitted sender) Received: from [75.98.160.130] (HELO a2s15.a2hosting.com) (75.98.160.130) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Sep 2011 19:17:16 +0000 Received: from 63-226-210-225.tukw.qwest.net ([63.226.210.225] helo=Astraendo) by a2s15.a2hosting.com with esmtpa (Exim 4.69) (envelope-from ) id 1R3YTW-0003yT-TT; Tue, 13 Sep 2011 15:16:55 -0400 Reply-To: From: "Dennis E. Hamilton" To: Cc: "'Donald Whytock'" References: <20110901140009.1C6DB8002@minotaur.apache.org> <00bd01cc7222$03f6c420$0be44c60$@acm.org> <00e701cc7232$a6a16cb0$f3e44610$@apache.org>

In-Reply-To: Subject: RE: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org) Date: Tue, 13 Sep 2011 12:16:55 -0700 Organization: NuovoDoc Message-ID: <016701cc7249$b448c9f0$1cda5dd0$@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKX+QPht+Zi4rprZ09CuOD0Ui7igwEkFwpzAYhQ1LMBzqNmlQJMXsk5Ama1PsCTayh2sA== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2s15.a2hosting.com X-AntiAbuse: Original Domain - incubator.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - acm.org I've responded to your questions in-line. With regard to detail, this is probably the longest report already. For = context, look at the complete set of reports so far, . They tend to the terse. Previous monthly reports since the Apache OOo Podling has been reporting = are these: and . Thanks Don, all of your questions are valuable. - Dennis -----Original Message----- From: Donald Whytock [mailto:dwhytock@gmail.com]=20 Sent: Tuesday, September 13, 2011 10:09 To: ooo-dev@incubator.apache.org Subject: Re: Incubator PMC/Board report for September 2011 = (ooo-dev@incubator.apache.org) I'd like to suggest this be more detailed, so it's clear where the problems are. That way it's easier to determine what ASF can provide that isn't provided already. >>> The current committers are not equipped to fully resource the = migration of >>> OpenOffice.org sites and services under Apache OOo incubation. Does "current committers" refer to people working on the Oracle site, or the current pool of committers in the podling? Current committers are the committers on the podling. I can say "podling = committers." The IPMC and Board will understand. Does "resource" mean supply time, gain access, provide equipment, have = skill? I meant resources in terms of what the Project itself, those of us on = the PPMC and ooo-dev, are equipped to bring to bear. I will get the = buzzword out of there. It is all of the above except for provide = equipment and running platforms. Apache Infrastructure has provided the = necessaries. >>> Preservation of the Wiki is in doubt because of resource and = support >>> limitations. Is this preservation of the wiki in its current form because the Oracle servers are going away? Preservation of the wiki data because it's not being done in a timely manner? Preservation of the wiki relates to our capability in terms of available = expertise. There is a functioning test instance, but some fixes are = needed. It is a MediaWiki and there is no identified expertise in = server-level and configuration work available to the project. >>> Cutover of mailing-list and registration/forwarding systems >>> is not resourced at all. "Resourced" as in people designated/volunteering to do it, no comparable Apache facility, no plan, no access? Yes on all of that, although Apache facilities are generally not the = issue so long as able people volunteering are available to determine = what facilities are required. That is a project responsibility. >>> The ability to make anticipatory modifications >>> of OpenOffice.org in preparation for staging is also limited, with >>> volunteer support and administration of the live system possibly = eroding. Specific problems with access, skill level, available people, timetable? Yes, and here it has to do with the live site on Oracle systems. = Although there is a fear of Oracle pulling the plug, I don't believe = that is imminent. On the other hand, working with Oracle for how long = there system needs to be up so staging can be risk-managed would be = good. That may be happening. It is not visible and I suspect the = project needs to identify its needs in a practical way. Am I overestimating what has to be in a podling report? I think precision is called for, and your questions help with that. = There's not a lot of quantitative detail. There are no charts, numbers, = and roadmaps to point at, though there are proposed pieces on the = OOOUSER Wiki. Don