bval-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1050165 - in /websites/staging/bval/trunk/content: ./ board-reports/2019-09.html
Date Mon, 16 Sep 2019 15:37:18 GMT
Author: buildbot
Date: Mon Sep 16 15:37:18 2019
New Revision: 1050165

Log:
Staging update by buildbot for bval

Modified:
    websites/staging/bval/trunk/content/   (props changed)
    websites/staging/bval/trunk/content/board-reports/2019-09.html

Propchange: websites/staging/bval/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Sep 16 15:37:18 2019
@@ -1 +1 @@
-1867006
+1867007

Modified: websites/staging/bval/trunk/content/board-reports/2019-09.html
==============================================================================
--- websites/staging/bval/trunk/content/board-reports/2019-09.html (original)
+++ websites/staging/bval/trunk/content/board-reports/2019-09.html Mon Sep 16 15:37:18 2019
@@ -133,80 +133,32 @@ under the License.
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
-<h2 id="apache-bval-report-june-2019">Apache BVal Report June 2019<a class="headerlink"
href="#apache-bval-report-june-2019" title="Permanent link">&para;</a></h2>
-<ul>
-<li>The Apache BVal project implements the Java EE Bean Validation
-   specification(s) and related extensions, and became a top-level project of
-   the foundation on February 15, 2012.</li>
-</ul>
+<h2 id="description">Description:<a class="headerlink" href="#description" title="Permanent
link">&para;</a></h2>
+<p>The mission of BVal is the creation and maintenance of software related to 
+Apache BVal: JSR-303 Bean Validation Implementation and Extensions</p>
 <h2 id="issues">Issues:<a class="headerlink" href="#issues" title="Permanent link">&para;</a></h2>
-<ul>
-<li>There are no issues requiring board attention at this time.</li>
-</ul>
-<h2 id="activity">Activity:<a class="headerlink" href="#activity" title="Permanent
link">&para;</a></h2>
-<ul>
-<li>
-<p>Over the past quarter the team has managed to put out a needed point
-   release, despite a precipitous drop in the availability of the chair.</p>
-</li>
-<li>
-<p>We have accumulated a new committer/PMC member.</p>
-</li>
-<li>
-<p>Finally, we have seen recent community participation that during the next
-   quarter will, in all likelihood, result in releases on both the 1.x and
-   2.x development lineages.</p>
-</li>
-<li>
-<p>It remains an open task to certify Apache BVal as an implementation of
-   the 2.0 BV specification.</p>
-</li>
-</ul>
-<h2 id="health-report">Health report:<a class="headerlink" href="#health-report"
title="Permanent link">&para;</a></h2>
-<ul>
-<li>We retain a small core of developers with the desire to keep this project
-   afloat. It is not clear how to attract additional hands other than to
-   trust that the right people for this niche project will find their way.</li>
-</ul>
-<h2 id="pmc-changes">PMC changes:<a class="headerlink" href="#pmc-changes" title="Permanent
link">&para;</a></h2>
-<ul>
-<li>Currently 14 PMC members. </li>
-<li>Thomas Andraschko was added to the PMC on Wed May 15 2019 </li>
-</ul>
-<h2 id="committer-base-changes">Committer base changes:<a class="headerlink" href="#committer-base-changes"
title="Permanent link">&para;</a></h2>
-<ul>
-<li>Currently 15 committers. </li>
-<li>Thomas Andraschko was added as a committer on Thu May 16 2019 </li>
-</ul>
-<h2 id="releases">Releases:<a class="headerlink" href="#releases" title="Permanent
link">&para;</a></h2>
-<ul>
-<li>2.0.2 was released on Wed May 15 2019 </li>
-</ul>
-<h2 id="mailing-list-activity">Mailing list activity:<a class="headerlink" href="#mailing-list-activity"
title="Permanent link">&para;</a></h2>
-<ul>
-<li>
-<p>These numbers reflect the recent flurry of activity:</p>
-</li>
-<li>
-<p>dev@bval.apache.org:  </p>
-<ul>
-<li>42 subscribers (up 0 in the last 3 months): </li>
-<li>85 emails sent to list (49 in previous quarter) </li>
-</ul>
-</li>
-<li>
-<p>user@bval.apache.org:  </p>
-<ul>
-<li>54 subscribers (up 0 in the last 3 months): </li>
-<li>1 emails sent to list (1 in previous quarter) </li>
-</ul>
-</li>
-</ul>
-<h2 id="jira-activity">JIRA activity:<a class="headerlink" href="#jira-activity"
title="Permanent link">&para;</a></h2>
-<ul>
-<li>5 JIRA tickets created in the last 3 months </li>
-<li>3 JIRA tickets closed/resolved in the last 3 months </li>
-</ul>
+<p>No issues requiring board attention at this time.</p>
+<h2 id="membership-data">Membership Data:<a class="headerlink" href="#membership-data"
title="Permanent link">&para;</a></h2>
+<p>Apache BVal was founded 2012-02-14 (8 years ago)
+There are currently 15 committers and 14 PMC members in this project.
+The Committer-to-PMC ratio is roughly 8:7.</p>
+<p>Community changes, past quarter:
+- No new PMC members. Last addition was Thomas Andraschko on 2019-05-15.
+- No new committers. Last addition was Thomas Andraschko on 2019-05-16.</p>
+<h2 id="project-activity">Project Activity:<a class="headerlink" href="#project-activity"
title="Permanent link">&para;</a></h2>
+<p>Apache BVal 2.0.3 was released on 2019-08-19. A maintenance release
+along the 1.1.x branch of activity is planned for the near future.</p>
+<h2 id="community-health">Community Health:<a class="headerlink" href="#community-health"
title="Permanent link">&para;</a></h2>
+<p>With last quarter's addition of a new volunteer to the PMC and
+committer roster, our capacity to keep up with maintenance tasks has
+increased. Our mailing list traffic is low; as noted in the past
+our usual model is frenzied activity for a spec-compliant release,
+then the maintenance cycle, much like the proverbial "periods of
+boredom punctuated by periods of terror" commonly attributed to war.
+Our JIRA activity also reflects this: two issues opened and closed
+with patches provided, accepted, and applied during the quarter.
+Another issue opened to request a release of those changes on a
+dormant line of development (the aforementioned 1.1.3 release).</p>
 
   </div>
 



Mime
View raw message