Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E9E367BFC for ; Wed, 23 Nov 2011 13:20:53 +0000 (UTC) Received: (qmail 90850 invoked by uid 500); 23 Nov 2011 13:20:53 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 90721 invoked by uid 500); 23 Nov 2011 13:20:53 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Delivered-To: moderator for general@incubator.apache.org Received: (qmail 23931 invoked by uid 99); 22 Nov 2011 03:51:14 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Date: Mon, 21 Nov 2011 19:50:40 -0800 (PST) From: Chris Hostetter To: "general@incubator.apache.org" , Joe Schaefer Subject: Re: should podlings have informal chairs? In-Reply-To: <1321923808.40552.YahooMailNeo@web160905.mail.bf1.yahoo.com> Message-ID: References: <46183E72-B786-4298-B14A-848A6D362D9B@apache.org> <1321894027.61167.YahooMailNeo@web160915.mail.bf1.yahoo.com> <1321901706.58942.YahooMailNeo@web16091 9.mail.bf1.yahoo.com> <1321902709.42027.YahooMailNeo@web160904.mail.bf1.yahoo.com> <1321923808.40552.YahooMailNeo@web160905.mail.bf1.yahoo.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-1795589768-1321933843=:14225" --8323328-1795589768-1321933843=:14225 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT : We should be reporting to the board about OUR work, not the work of : the podlings.� Podlings should only be brought in for a few specific : examplesto mention.� That's the first thing to correct. While I generally agree with everything you suggest, your entire premise seems to be in direct conflict with everything that I've ever seen/heard brought up regarding the point of Board Reports and the argument against "Umbrella Projects" -- notably .... * Umbrella Projects add a layer of indirection that make it hard for the board to know when there are problems in the individual (sub/leaf) projects. * The Board needs regular status updates on all the projects in the ASF (where podlings are considered projects) While it seems to be historically accepted that the Incubator is one the exception/exemption to the "No Umbrella" rule, I seem to recall it being argued that that exemption doesn't change the fact the individual podling reports are suppose to propogate all the way up to the board to. (but i could be wrong) That said: (Even if i am remembering correctly) Things change. If the new world order is that the Membership is cool with the IPMC acting as a proxy for the Board, and that the Board doens't need to "lay hands" on direct reports from each project/podling, then so be it .... just makes me wonder if that means there should be some re-consideration of the Umbrella rule in general -- Because another way to help scale the governance of the ASF as a whole would be to add some Umbrella management for groups of projects that have a lot of overlap) -Hoss --8323328-1795589768-1321933843=:14225 Content-Type: text/plain; charset=us-ascii --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org --8323328-1795589768-1321933843=:14225--