Return-Path: X-Original-To: apmail-community-commits-archive@minotaur.apache.org Delivered-To: apmail-community-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EFE2F7DA8 for ; Tue, 15 Nov 2011 03:45:00 +0000 (UTC) Received: (qmail 943 invoked by uid 500); 15 Nov 2011 03:44:58 -0000 Delivered-To: apmail-community-commits-archive@community.apache.org Received: (qmail 832 invoked by uid 500); 15 Nov 2011 03:44:45 -0000 Mailing-List: contact commits-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list commits@community.apache.org Received: (qmail 814 invoked by uid 99); 15 Nov 2011 03:44:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2011 03:44:43 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2011 03:44:38 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 1C46C2388A64 for ; Tue, 15 Nov 2011 03:44:17 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r798685 - /websites/staging/community/trunk/content/boardreport.html Date: Tue, 15 Nov 2011 03:44:17 -0000 To: commits@community.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20111115034417.1C46C2388A64@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Tue Nov 15 03:44:16 2011 New Revision: 798685 Log: Staging update by buildbot Modified: websites/staging/community/trunk/content/boardreport.html Modified: websites/staging/community/trunk/content/boardreport.html ============================================================================== --- websites/staging/community/trunk/content/boardreport.html (original) +++ websites/staging/community/trunk/content/boardreport.html Tue Nov 15 03:44:16 2011 @@ -125,43 +125,45 @@ the first of the month)
  • Update board report ready for submission
  • Post mail to developer list asking for a review of the draft report
  • Incorporate feedback from community
  • -
  • PMC chair submits board report via board.at.apache.org with subject of "[REPORT](report.html) +
  • PMC chair submits board report via board.at.apache.org with subject of "[REPORT] project name" (copy to project private or dev list as appropriate)
  • Board Report Template
    Status report for the Apache FOO project - MONTH YEAR -
    Project Status
    ---------------
    +
    A couple of sentences about the purpose of the project.
     
    -A sentence or two describing the current status of the project. Most importantly, highlight any issues that require board 
    -attention. This is the projects opportunity to ask for assistance from the board should there be any sticky issues that need 
    -addressing.
    +Project Status
    +--------------
     
    -Community
    ----------
    +A sentence or two describing the current status of the project. Most importantly, highlight any issues that require board 
    +attention. This is the projects opportunity to ask for assistance from the board should there be any sticky issues that need 
    +addressing.
     
    -A slightly more detailed look at the project community. It should still be brief, issues to think about include:
    +Community
    +---------
     
    -* Is the project community active? 
    -* Is the user community growing/shrinking? 
    -* Are there any legal, infrastructure, cross-project or personal issues that need to be addressed?
    -* Are issues on the user/developer list being addressed?
    -* Have any new committers been voted in? Any changes in the PMC?
    +A slightly more detailed look at the project community. It should still be brief, issues to think about include:
     
    -Community Objectives
    ---------------------
    +* Is the project community active? 
    +* Is the user community growing/shrinking? 
    +* Are there any legal, infrastructure, cross-project or personal issues that need to be addressed?
    +* Are issues on the user/developer list being addressed?
    +* Have any new committers been voted in? Any changes in the PMC?
     
    -This section indicates what the community considers to be its highest priorities for the coming quarter. This is only intended 
    -as a record of likley actions to address any issues the community may have. The project should not feel limited to (or by) 
    -these objectives.
    +Community Objectives
    +--------------------
     
    -* What are the projects main plans and expectations for the community in the next period?
    +This section indicates what the community considers to be its highest priorities for the coming quarter. This is only intended 
    +as a record of likley actions to address any issues the community may have. The project should not feel limited to (or by) 
    +these objectives.
     
    -Releases
    ---------
    +* What are the projects main plans and expectations for the community in the next period?
     
    -Have there been any releases from the project in the last quarter? If notwhen is the next one likely to be made?
    +Releases
    +--------
    +
    +Have there been any releases from the project in the last quarter? If notwhen is the next one likely to be made?