This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/vcl-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 6726cf0  Updated site from master 
(451b1805a6eaed9587e3d526c731c8eb2118c984)
6726cf0 is described below

commit 6726cf04906ae4d0f1dfa916dbdfdd5e56134377
Author: jenkins <bui...@apache.org>
AuthorDate: Thu Apr 16 15:11:21 2020 +0000

    Updated site from master (451b1805a6eaed9587e3d526c731c8eb2118c984)
---
 .../comm/boardreports/apache-vcl-board-report.html | 38 +++++++++++++---------
 1 file changed, 23 insertions(+), 15 deletions(-)

diff --git a/content/comm/boardreports/apache-vcl-board-report.html 
b/content/comm/boardreports/apache-vcl-board-report.html
index 7ebb4cf..6e565ef 100644
--- a/content/comm/boardreports/apache-vcl-board-report.html
+++ b/content/comm/boardreports/apache-vcl-board-report.html
@@ -5,7 +5,7 @@
 
   <link href="/css/vcl.css" rel="stylesheet" type="text/css">
   <link href="/css/code.css" rel="stylesheet" type="text/css">
-  <title>Apache VCL - 2012-08-15 Apache VCL Board Report</title>
+  <title>Apache VCL - 2012-09-19 Apache VCL Board Report</title>
   <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 </head>
 
@@ -76,7 +76,7 @@
   </div>
   
   <div id="content">
-    <h1 class="title">2012-08-15 Apache VCL Board Report</h1>
+    <h1 class="title">2012-09-19 Apache VCL Board Report</h1>
     
        <h3 id="description">DESCRIPTION</h3>
 <p>VCL is a modular cloud computing platform which dynamically provisions and
@@ -86,22 +86,32 @@ self-service web portal is used to request resources and for
 administration. VCL became a TLP on June 20, 2012.</p>
 <h3 id="current-activity">CURRENT ACTIVITY</h3>
 <ul>
-<li>The community has completed most of the post-graduation tasks with the
-help of Infrastructure. <a href="#1">[1]</a></li>
-<li>A CMS website has been created. <a href="#2">[2]</a>
-We are working to migrate content from Confluence to the CMS.</li>
-<li>A VCL 2.3.1 bugfix branch has been created. This will be released in a
-few months.</li>
-<li>Development is beginning for VCL 2.4 features.</li>
+<li>The community has completed the post-graduation tasks.</li>
+<li>Work continues to migrate content from Confluence to the new CMS website
+and to improve the design.</li>
+<li>Several commits have been made to the VCL 2.3.1 bugfix branch to address
+minor problems with VCL 2.3, which was released in July. VCL 2.3.1 will be
+released this fall.</li>
+<li>Traffic on the lists has been fairly high, mostly due to questions
+related to recently released VCL 2.3.</li>
+<li>Development is still in the beginning stage for the VCL 2.4 features.
+Most development has been devoted to bug fixes.</li>
+<li>One of the committers is working to develop code to provide a VCL block
+in Moodle. Some licensing concerns arose from this due to Moodle&rsquo;s GPL
+license. <a href="#1">[1]</a>
+Guidance was provided by legal-discuss. It was decided for this to be a
+separate non-ASF project independent of the Apache VCL.</li>
 </ul>
 <h3 id="releases">RELEASES</h3>
 <ul>
-<li>VCL 2.3 was released on 2012-07-20</li>
+<li>None</li>
 </ul>
 <h3 id="community">COMMUNITY</h3>
 <ul>
-<li>Subscribers to the user list: 150</li>
-<li>Subscribers to the dev list: 143</li>
+<li>Subscribers to the user list: 154</li>
+<li>Posts to user list, 8/2012: 130</li>
+<li>Subscribers to the dev list: 144</li>
+<li>Posts to dev list, 8/2012: 159</li>
 <li>Committers: 9</li>
 <li>PMC members: 6</li>
 </ul>
@@ -110,9 +120,7 @@ few months.</li>
 <li>There are no issues requiring board attention at this time.</li>
 </ul>
 <p><a name="1" />
-[1] <a 
href="https://issues.apache.org/jira/browse/INFRA-4761";>https://issues.apache.org/jira/browse/INFRA-4761</a><br>
-<a name="2" />
-[2] <a href="http://vcl.apache.org";>http://vcl.apache.org</a></p>
+[1] <a 
href="http://markmail.org/thread/leb6jw5e3d45lswy";>http://markmail.org/thread/leb6jw5e3d45lswy</a></p>
 
 
   </div>

Reply via email to