community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r804035 - /websites/staging/community/trunk/content/comdevboardreports.html
Date Mon, 06 Feb 2012 22:40:25 GMT
Author: buildbot
Date: Mon Feb  6 22:40:25 2012
New Revision: 804035

Staging update by buildbot for comdev


Modified: websites/staging/community/trunk/content/comdevboardreports.html
--- websites/staging/community/trunk/content/comdevboardreports.html (original)
+++ websites/staging/community/trunk/content/comdevboardreports.html Mon Feb  6 22:40:25 2012
@@ -121,17 +121,44 @@ involved with Apache projects
 <h2 id="project-status">Project Status</h2>
 <p>No issues require board attention at this time.</p>
 <h2 id="gsoc">GSoC</h2>
+<p>GSoC 2012 was announced at FOSDEM on 4th February. ComDev has commenced 
+our organisation. We've already had two experienced admins step forwards, 
+with a further two newcomers expressing interest. This is very encouraging.</p>
   * Publish the GSoC Admin guidelines
   * Verify that new mentor selection process is documented for GSoC
   * Verify infra is OK with temporary accounts for GSoC</p>
+<p>New Tasks:
+  * Submit ASF to GSoC
+  * Work with projects to identify suitable GSoC tasks</p>
 <h2 id="events-and-speakers">Events and Speakers</h2>
+<p>Ross (ComDev chair) met face to face with Nick Burch (ConCom chair) to discuss
+a stronger relationship between ConCom and ComDev. As a result Nick has done
+a little work on the speakers application. The intention is to make a number 
+of web widgets (via the Wookie podling) available for hosting via the CMS that can be embedded
in project 
+and foundation pages. Work is ongoing.</p>
+<p>Nick and Ross also discussed the potential relationship relating to events.
+Nick has shelved this work in preference to working on the RFP for producers.</p>
   * Agree scope of ConCom and ComDev collaboration on event support
   * Raise awareness of Speaker and Event support materials
   * Integrate speaker app with Lanyrd (hosts all ApacheCon NA12 slidedecks)</p>
 <h2 id="website">Website</h2>
-<h2 id="objectives-for-next-period">Objectives for next period</h2>
+<p>There was considerable discussion about the use of org.apache package names on 
+apache-extras. This has now been clarified in the FAQ and Guidelines.</p>
+<p>In the last few days before this report there has been a great deal of 
+discussion on general@incubator.a.o It seems that reform is in the air and
+many people are suggesting that some of the key functions move to ComDev.
+However, there is no consensus in the IPMC about what the future should look
+like and thus no clarity around what ComDev is expected to pick up.</p>
+<p>Some members of ComDev are involved with the discussion, but until there is
+more clarity in the IPMC there seems little point in taking the discussion to
+ComDev lists.</p>
+<h2 id="tasks">Tasks</h2>
+<li>Work with the IPMC to clarify any future role for ComDev in the incubation 
+    process</li>
 <p><a name="ComDevBoardReports-SubmittedReports"></a></p>
@@ -165,7 +192,7 @@ PMC for discussion during the next repor
   * Raise awareness of Speaker and Event support materials</p>
 <h2 id="website_1">Website</h2>
 <p>No major changes this month, just a few minor tweaks to the Speakers section.</p>
-<h2 id="objectives-for-next-period_1">Objectives for next period</h2>
+<h2 id="objectives-for-next-period">Objectives for next period</h2>
 <li>propose opportunities for further collaboration between ConCom and ComDev
     with respect to events.</li>
@@ -231,7 +258,7 @@ what an ASF project looks like.</p>
 coordinated through ComDev. The EU project which was supposed to be 
 sending people our way is currently evaluating why students did not come 
 to us (report due before next board report).</p>
-<h2 id="objectives-for-next-period_2">Objectives for next period</h2>
+<h2 id="objectives-for-next-period_1">Objectives for next period</h2>
 <p>Raise awareness of Speaker and Event support materials</p>
@@ -263,7 +290,7 @@ extension projects that cannot use the A
 dependencies. </p>
 <p>There is some work underway to formally document Apaches expectations 
 that projects will be run independently of company affiliation.</p>
-<h2 id="objectives-for-next-period_3">Objectives for next period</h2>
+<h2 id="objectives-for-next-period_2">Objectives for next period</h2>
 <p>Complete GSoC and make an appropriate press release upon completion.</p>
 <p>Improve documentation about independence of Apache projects</p>
@@ -296,7 +323,7 @@ career advantages experience with ASF pr
 "community game" which will introduce students to the idea of engaging in public.</p>
 <p> was launched. As agreed the committee is hands off on the 
 management of this site. There are currently 89 projects listed.</p>
-<h2 id="objectives-for-next-period_4">Objectives for next period</h2>
+<h2 id="objectives-for-next-period_3">Objectives for next period</h2>
 <li>Coordinate Google Summer of Code</li>
 <li>Analyse use of</li>
@@ -338,7 +365,7 @@ ASF.</p>
 <p>An increasing number of volunteers are becoming engaged with Community
 Development PMC and contact from external participants is increasing
 (although still low).</p>
-<h2 id="objectives-for-next-period_5">Objectives for next period</h2>
+<h2 id="objectives-for-next-period_4">Objectives for next period</h2>
 <li>Gain support from at least 5 PMCs for the mentoring programme</li>
 <li>Formally launch mentoring programme</li>
@@ -382,7 +409,7 @@ felt the mentors decision was fair and t
 at fault. A minor tweak relating to the communication of our expectations
 to the students has been implemented. Full details can be reviewed at</p>
-<h2 id="objectives-for-next-period_6">Objectives for next period</h2>
+<h2 id="objectives-for-next-period_5">Objectives for next period</h2>
 <li>Gain support from at least 5 PMCs for the mentoring programme</li>
 <li>Launch the mentoring programme in September (no press at this stage)

View raw message