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 39AE39CAD for ; Mon, 5 Mar 2012 23:29:50 +0000 (UTC) Received: (qmail 41146 invoked by uid 500); 5 Mar 2012 23:29:49 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 40866 invoked by uid 500); 5 Mar 2012 23:29:49 -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 Received: (qmail 40858 invoked by uid 99); 5 Mar 2012 23:29:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2012 23:29:49 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com designates 209.85.212.175 as permitted sender) Received: from [209.85.212.175] (HELO mail-wi0-f175.google.com) (209.85.212.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2012 23:29:41 +0000 Received: by wibhq12 with SMTP id hq12so2387226wib.6 for ; Mon, 05 Mar 2012 15:29:21 -0800 (PST) Received-SPF: pass (google.com: domain of jukka.zitting@gmail.com designates 10.180.101.72 as permitted sender) client-ip=10.180.101.72; Authentication-Results: mr.google.com; spf=pass (google.com: domain of jukka.zitting@gmail.com designates 10.180.101.72 as permitted sender) smtp.mail=jukka.zitting@gmail.com; dkim=pass header.i=jukka.zitting@gmail.com Received: from mr.google.com ([10.180.101.72]) by 10.180.101.72 with SMTP id fe8mr18829614wib.4.1330990161206 (num_hops = 1); Mon, 05 Mar 2012 15:29:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=XABuUIPHwzX6SMQmIK63Vl2ACVQd+hBwVLSFioYhbRI=; b=B/zjnRQrr4kqs8lM07cXGQ9LHZU8d5MFYbfUgKrIvOwADXJbvWSzHu5z/XHcifDlQB bPEe6Avwe55tymwRnL6OhwwWjG/LxB/ySaq7O7FnNqVDMIT0HFR8sxr3uLfT/A58CGim Xpgolyq/+1LT/Bhzh3xbrXNOjiVGJPNvQ44lZ3UnbZbAKzjLuIx9JXM4Li7MjKk8U3ED w7n73dbQjOMesyj7e5u78Ss9NS9UwAtAV2Gqy5bgHhOEbkZxU/fW6P83vNlDhFQ/7NWi AcbS427HtYni484F/qJpkT+qKE9o/tYeY6Hnpk1e0FGLPAg0mIrC2pv0pwPy/DsF5P3P uy2A== Received: by 10.180.101.72 with SMTP id fe8mr14963055wib.4.1330990161114; Mon, 05 Mar 2012 15:29:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.102.134 with HTTP; Mon, 5 Mar 2012 15:29:01 -0800 (PST) From: Jukka Zitting Date: Tue, 6 Mar 2012 00:29:01 +0100 Message-ID: Subject: Thoughts on Incubator board reports To: general Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi, During the February board meeting there was a discussion about what the directors would like to see in Incubator reports. The feedback we got on this ranged from providing just an "executive summary" of all Incubator activity to doing that *and* including all the podling reports. While there was no clear single message, the overall impression I got was that the board expects the Incubator PMC to provide better and more active oversight on podlings. At the same time many directors also wanted to hear directly from the podlings themselves. After thinking about this for a while, here's what I think we should do: First of all I think we should keep including the individual podling reports in the Incubator board report. The main reason for doing this is that I think we should get the podlings up to the habit of reporting to the board instead of just to the IPMC right from the beginning. The IPMC will provide extra review and feedback to help the podlings, but ultimately all the reports are addressed to the ASF board. This approach should also be in line with the ideas of scaling back the the Incubator and making podlings more autonomous. Second, to address concerns about oversight within the Incubator as a whole and to provide enough information to directors who may not be interested in all the details of individual podling reports, the IPMC should also provide a report summary along the lines of what we did last month. In addition to basic classification of podlings based on their progress, we should also highlight any notable issues or other topics the board may want to focus on. Finally, and crucially since the above isn't too different from what we've been doing all along, we'll take some time to discuss the podling reports that need some clarification or for which some other kind of feedback should be given. As you've seen, I've already started doing some of that and I'm hoping to set an example for others to follow. Iterate for a few months, and I believe the result should be a notable increase in report quality, graduation focus and more generally the awareness within the IPMC of how the podlings are doing. BR, Jukka Zitting --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org