This was extracted (@ 2024-04-17 21:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Project Status: Current project status: Dormant Issues for the board: none ## Membership Data: Apache BVal was founded 2012-02-14 (12 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: Current activity consists of maintenance with the usual cast of PMC members committed and available for voting. ## Community Health: Nothing has changed in this aspect; the stable nature and well-defined scope of the project represent a lack of attractive work for new contributors.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Project Status: Current project status: Ongoing-low/dormant Issues for the board: none ## Membership Data: Apache BVal was founded 2012-02-14 (12 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: Version 3.0.0 of Apache BVal was released this quarter, hence the "ongoing" status. Qualified as "low" due to the relatively "maintenance" nature of the release. "Dormant" is the usual and anticipated-future state of the project. ## Community Health: Community health remains unchanged overall. Things that need to get done are getting done, typically by more recent participants in the community which perhaps says something positive about the evolution of the community composition. Small increases in commit/PR/email traffic look huge in comparison to the near-zero levels we usually observe, but all told things are business as usual.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Project Status: Current project status: Apache BVal's development has been dormant this quarter. Issues for the board: There are no issues requiring board attention at this time. ## Membership Data: Apache BVal was founded 2012-02-14 (12 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: There has been no significant committer activity to the project this period. ## Community Health: There has been no new interest registered; however, there are no signs that our voting quorum of "obligated" PMC members is in any sort of jeopardy.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Project Status: Current project status: Dormant Issues for the board: none. ## Membership Data: Apache BVal was founded 2012-02-14 (11 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: Recent activity has been limited to responding to automated dependency upgrade suggestions. ## Community Health: No changes in community health, which is to say our community remains small and "reactive." We do continue to have a sufficient number of PMC members who will perform required tasks out of duty if nothing else. As part of the suite of implementations of Java Community Specifications as implemented at the ASF, we see BVal as being essential and thus plan to maintain it in dormant state indefinitely.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: There are no issues requiring board attention. ## Membership Data: Apache BVal was founded 2012-02-14 (11 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: We have seen a modest increase in activity, primarily arising from migration of API concerns from the Java to Jakarta namespace, this quarter. ## Community Health: Our normal mode continues to be that of maintenance and performing what tasks *need* to be done. As well, the metrics are perhaps artificially inflated due to the "participation" of dependabot which has generated several pull requests on the project.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache BVal was founded 2012-02-14 (11 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: The missing release keys issue identified during the last reporting cycle has been addressed. ## Community Health: In all honesty the community is quite anemic, with next to no email activity and no commits beyond the fixes to our KEYS file. There is just not a lot to do between specification releases.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache BVal was founded 2012-02-14 (11 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: Apache BVal 2.0.6 was released on June 13 and addressed compatibility issues arising from the migration of the Java specification process to the Eclipse foundation. This was the extent of BVal project activity. ## Community Health: We continue to subsist in maintenance mode, with evident stability. To our discredit, we have failed thus far to effect for the purpose of catalyzing community involvement any of the suggestions presented by the board (Rich) in response to our Q2 report.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache BVal was founded 2012-02-14 (10 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: Jean-Louis Monteiro has undertaken the lion's share of the effort to modify Apache BVal to function in the post-Jakarta Java EE ecosystem and the vote to release his changes is currently underway. The pursuit of official TCK certification is planned for the near term, as well. ## Community Health: Our community remains sparse as ever. Board feedback from our most recent previous report included some recommendations for improving this situation, and it is on the PMC (chair) that none of these has yet been investigated.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: Automated tools show our project's health as requiring urgent attention, but for our purposes no news is often good news. ## Membership Data: Apache BVal was founded 2012-02-14 (10 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: We received this quarter a report of a possible issue which turned out to be the result of a downstream consumer relying on implementation-specific behavior of the Java Bean Validation specification's reference implementation. There was nothing that Apache BVal, as a good-faith implementor of the specification, was/is bound to do to address the issue. We could jump in with a contribution to the downstream OSS project, but it may be just as valuable to remain a "voice of reason" in remaining, out of the box at least, a neutral implementation pure to the letter of the specification. ## Community Health: We have had no newcomers to the project. It is not clear whether or why our imperative is to perennially grow the membership, nor, if that is indeed our mandate, how to attract new blood.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: Project statistics tool gives us a negative community health score. ## Membership Data: Apache BVal was founded 2012-02-14 (10 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: Being an implementation of a Java Community specification, it is not uncommon for Apache BVal to be in a dormant state for relatively long periods of time. With that in mind, we have recently been arguably less active than usual. Admittedly it would be better if we could collectively devote a bit more time to the project as there is at least one recently demonstrated failure in specification compatibility that has as yet gone unaddressed; at the same time we remain confident that we can continue to keep abreast of any sweeping updates to our target specification. ## Community Health: As noted in the "issues" section, statistics-based estimates of community health are not flattering to the team. If (paraphrasing) "bad code yields good communities" we can at least take the metrics as a backhanded compliment (which is by no means intended to imply that our code has no areas that could benefit from improvement). We are more than willing to consider any suggestions for improving community engagement.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache BVal was founded 2012-02-14 (10 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: Activity remains low as per usual. There is typically no call for development outside the scope of a new release of the Java Bean Validation specification. Last release was in October 2020. ## Community Health: Community is responding to one recent bug report and retains the personnel to make necessary decisions on patch releases, etc. Quiet mailing lists reflect, hopefully, the stable nature of the project.
No report was submitted.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: There are no issues requiring board attention. ## Membership Data: Apache BVal was founded 2012-02-14 (9 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: This has been a very quiet quarter for the Apache BVal project, with neither commits nor releases having been made. As stated numerous times in the past, we expect these lulls in activity since our mission is to implement an open specification. We have appreciated the assistance (i.e. having completely taken on the job) provided this quarter by Dave Fisher/infra in the conversion and migration of our project site from the Apache CMS. ## Community Health: We retain a core of PMC members engaged to support essential changes and related releases.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: No issues requiring board attention at this time. ## Membership Data: Apache BVal was founded 2012-02-14 (9 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17. ## Project Activity: Low, as usual: community members have this past quarter engaged in discussion of a single new, as yet unresolved, project feature. ## Community Health: Vital signs remain faint but stable. Our issue tracking and email activity experienced a false positive "spike" due to a rash of JIRA spam.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: No issues requiring board attention at this time. ## Membership Data: Apache BVal was founded 2012-02-14 (9 years ago) There are currently 16 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - Jean-Louis Monteiro was added to the PMC on 2020-11-29 - Jean-Louis Monteiro was added as committer on 2020-11-17 ## Project Activity: Apache BVal 2.0.5 was released on October 26. Additionally, we have recently welcomed Jean-Louis Monteiro to the PMC in recognition of his participation and assistance with our last few releases. ## Community Health: Our activity metrics for this quarter were raised across the board. This is partially due to the community activity that led to our recent release. Additionally, we have just begun exploring new opportunities for extending the base specification for improved compatibility with CDI frameworks, which was another contributing factor.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache BVal was founded 2012-02-14 (9 years ago) There are currently 15 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 8:7. 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. ## Project Activity: Maintenance release 2.0.4 was made in July. We are currently working to migrate our project website off the Apache CMS. ## Community Health: Our roster of engaged PMC members remains sufficient for making releases and carrying out necessary upkeep.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: There are no issues requiring board attention at this time. ## Membership Data: 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. 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. ## Project Activity: No urgent tasks have needed doing since our last report. ## Community Health: We have had a slight rise in issue tracker activity this quarter but none of these have yet resulted in anything requiring developer attention. We consider this normal for Apache BVal.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: Please accept our apologies for having failed to submit a timely report for last month's board meeting as scheduled. There are no issues requiring board attention at this time. ## Membership Data: 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. 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. ## Project Activity: Apache BVal 2.0.3 was released on 2019-08-19. We are currently in one of our characteristic quiescent cycles, having successfully implemented the latest version of the specification an AL-licensed implementation of which it is our mission to provide. We are in pure reactive mode with no issues reported of late. ## Community Health: Automated tools score us negatively on health, yet we are as healthy as we need to/can be given the nature of the project.
No report was submitted.
@Dave: pursue a report for BVal
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: No issues requiring board attention at this time. ## Membership Data: 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. 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. ## Project Activity: Apache BVal 2.0.3 was released on 2019-08-19. Last quarter we reported a planned 1.1.x maintenance release but there has not yet been significant forward movement on that. ## Community Health: We have had a very quiet quarter, with a single issue reported and subsequently closed having verified the issue was not with Apache BVal itself. Our (low) capacity continues to exceed our (lower) demand.
## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Issues: No issues requiring board attention at this time. ## Membership Data: 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. 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. ## Project Activity: 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. ## Community Health: 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).
## Apache BVal Report June 2019 ##
- 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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- 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.
- We have accumulated a new committer/PMC member.
- 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.
- It remains an open task to certify Apache BVal as an implementation of
the 2.0 BV specification.
## Health report:
- 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.
## PMC changes:
- Currently 14 PMC members.
- Thomas Andraschko was added to the PMC on Wed May 15 2019
## Committer base changes:
- Currently 15 committers.
- Thomas Andraschko was added as a committer on Thu May 16 2019
## Releases:
- 2.0.2 was released on Wed May 15 2019
## Mailing list activity:
- These numbers reflect the recent flurry of activity:
- dev@bval.apache.org:
- 42 subscribers (up 0 in the last 3 months):
- 85 emails sent to list (49 in previous quarter)
- user@bval.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (1 in previous quarter)
## JIRA activity:
- 5 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
## Apache BVal Report March 2019 ##
- 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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- We have lately been working to support our 2.0.0 release from last fall.
Most notably this release, which rewrote a large portion of the codebase,
is quite slow compared to the reference implementation of the Java Bean
Validation (BV) specification so our near-term efforts will revolve around
making improvements in that regard.
- The 2.0.1 release described in last quarter's report as being in planning
has not yet occurred. To remind the reader, one of the main purposes of
the release would be to enable the proper tooling to certify Apache BVal
as an implementation of the 2.0 BV specification.
## Health report:
- We retain a small core of developers with the desire to keep this project
afloat. It must be admitted that the available time for this project
among this pool of resources is suboptimal; we continue to do what we can.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013
## Committer base changes:
- Currently 14 committers.
- No new changes to the committer base since last report.
## Releases:
- Last release was 2.0.0 on Sat Oct 27 2018
## Mailing list activity:
- dev@bval.apache.org:
- 42 subscribers (up 0 in the last 3 months):
- 49 emails sent to list (118 in previous quarter)
- user@bval.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (5 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
## Apache BVal Report December 2018 ##
- 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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- During the past quarter we released Apache BVal 2.0.0 which delivers an
implementation of the latest 2.0 Bean Validation JSR specification.
- The recent release included code that, unless deliberately circumvented,
would prevent the behavior at the core of the security vulnerability reported
during Q2.
- The Bean Validation EG leadership has reached out to encourage us to obtain
official status as a conforming implementation. This is primarily a matter
of configuration tooling which we hope to address in a forthcoming point
release.
- We have received a small number of post-release bug reports which we intend
to address in the immediate future when the team's non-volunteer workload
permits.
## Health report:
- We retain a small core of developers with the desire to keep this project
afloat.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013
## Committer base changes:
- Currently 14 committers.
- No new changes to the committer base since last report.
## Releases:
- 2.0.0 was released on Sat Oct 27 2018
## Mailing list activity:
- Activity this quarter reflects the release process of version 2.0.0 and an
accompanying JIRA cleanup. Post-release saw some activity in response.
- dev@bval.apache.org:
- 42 subscribers (down -4 in the last 3 months):
- 118 emails sent to list (26 in previous quarter)
- user@bval.apache.org:
- 54 subscribers (down -2 in the last 3 months):
- 5 emails sent to list (2 in previous quarter)
## JIRA activity:
- 11 JIRA tickets created in the last 3 months
- 21 JIRA tickets closed/resolved in the last 3 months
## Apache BVal Report September 2018 ## - 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. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Apache BVal community members working in Apache Commons have recently succeeded in pushing the 2.0 release of the Apache Commons Weaver component upon which we depend. - Our immediate plans are to push the release of the Apache licensed bean validation 2.0 specification artifact through the Apache Geronimo project and then to release Apache BVal 2.0. - The security issue mentioned last quarter is incurred at the specification level and has been deemed low priority by the bean validation community as a whole, any vulnerability requiring deliberate and naive custom code on the part of the application developer. The Apache BVal community continue to ponder what actions we might take to reduce the likelihood of such naive exposures. ## Health report: - We retain a small core of developers with the desire to keep this project afloat. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013 ## Committer base changes: - Currently 14 committers. - No new changes to the committer base since last report. ## Releases: - Last release was 1.1.2 on Wed Nov 02 2016 ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months
## Apache BVal Report June 2018 ## - 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. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - The (new) Apache BVal 2.0 codebase now passes the Java Bean Validation 2.0 TCK. - Apache BVal 2.0 has a dependency on the Apache Commons Weaver component and is awaiting a release compatible with Java 8. - In the past week we have received a report of a security issue which a member of the community has begun to triage. ## Health report: - We retain a small core of developers with the desire to keep this project afloat. ## PMC changes: - Currently 13 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013 ## Committer base changes: - Currently 14 committers. - No new changes to the committer base since last report. ## Releases: - Last release was 1.1.2 on Wed Nov 02 2016 ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 2 JIRA tickets closed/resolved in the last 3 months
## Apache BVal Report March 2018 ##
- 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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The Apache BVal project has taken the task of implementing Java Bean
Validation 2.0 as an opportunity for a major overhaul of the underlying
structure of the codebase. This is more or less complete and the team is
currently focused on meeting the requirements of the technology
compatibility kit (TCK) for certification as a compliant implementation
of the latest specification.
## Health report:
- We retain a small core (or corps, even) of developers with the desire to
keep this project afloat.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013
## Committer base changes:
- Currently 14 committers.
- No new changes to the committer base since last report.
## Releases:
- Last release was 1.1.2 on Wed Nov 02 2016
## Mailing list activity:
- dev@bval.apache.org:
- 46 subscribers (up 0 in the last 3 months):
- 11 emails sent to list (19 in previous quarter)
- user@bval.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (4 in previous quarter)
## Apache BVal Report December 2017 ##
- 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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Project moved from Subversion to git for source control during this quarter.
- Development continues on implementing Java Bean Validation 2.0 in Apache BVal
2.0. With luck a release can be made next quarter.
## Health report:
- BVal continues to be maintained by obligation. However, there are several
exciting new features in the latest version of the specification and this
may foster new activity in the community.
## PMC changes:
- Currently 14 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013
## Committer base changes:
- Currently 14 committers.
- No new changes to the committer base since last report.
## Releases:
- Last release was 1.1.2 on Wed Nov 02 2016
## Mailing list activity:
- dev@bval.apache.org:
- 46 subscribers (up 1 in the last 3 months):
- 19 emails sent to list (10 in previous quarter)
- user@bval.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 4 emails sent to list (0 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
## Apache BVal Report September 2017 ## - 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. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - Version 2.0 of the Java Bean Validation specification was finalized during the past quarter; work progresses on the corresponding Apache BVal version 2.0 as resources are available. ## Health report: - BVal continues to be maintained by obligation; this remains tenable as not a great many issues have arisen requiring urgent attention. ## PMC changes: - Currently 14 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013 ## Committer base changes: - Currently 14 committers. - No new changes to the committer base since last report. ## Releases: - Last release was 1.1.2 on Wed Nov 02 2016 ## JIRA activity: - 2 JIRA tickets created in the last 3 months - 1 JIRA tickets closed/resolved in the last 3 months
## Apache BVal Report June 2017 ## - 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. ## Issues: - There are no issues requiring board attention at this time. ## Activity: - We have begun work on the necessary changes to implement the forthcoming 2.0 version of the Java Bean Validation specification. We should have quite heightened activity over the next cycle or two while this work proceeds. ## Health report: - BVal continues to be maintained by obligation; this remains tenable. ## PMC changes: - Currently 14 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013 ## Committer base changes: - Currently 14 committers. - No new changes to the committer base since last report. - Last committer addition was Romain Manni-Bucau on Sun Jun 23 2013 ## Releases: - Last release was 1.1.2 on Wed Nov 02 2016 ## JIRA activity: - 1 JIRA tickets created in the last 3 months - 0 JIRA tickets closed/resolved in the last 3 months
## Apache BVal Report March 2017 ##
- 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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- None to speak of this quarter, which is normal for BVal: occasionally
there is a frenzy of activity to effect a release, but these are
punctuated by relative silence. As mentioned in previous reports, the
specification process for Java Bean Validation 2.0 proceeds and seems to
be nearing completion. There will be a resumption of activity in this
project in response to that.
## Health report:
- The project staff remains busy elsewhere, for the most part. BVal is
curated on a obligation basis more than anything else at this point. It
is perhaps not the ideal scenario for project health, but it remains
tenable.
## PMC changes:
- Currently 14 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013
## Committer base changes:
- Currently 14 committers.
- No new changes to the committer base since last report.
- Last committer addition was Romain Manni-Bucau on Sun Jun 23 2013
## Releases:
- Last release was 1.1.2 on Wed Nov 02 2016
## Mailing list activity:
- The following statistics reflect the ebb in activity subsequent to the
previous release.
- dev@bval.apache.org:
- 44 subscribers (up 1 in the last 3 months):
- 7 emails sent to list (75 in previous quarter)
- user@bval.apache.org:
- 53 subscribers (up 2 in the last 3 months):
- 4 emails sent to list (3 in previous quarter)
## JIRA activity:
- N/A
## Apache BVal Report December 2016 ##
- 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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The community pulled together to get some improvements out the door for
inclusion into Apache TomEE 7.0.2. A parallel effort was made to clean up
the JIRA backlog, closing issues that had inadvertently become obsolete,
etc.
## Health report:
- The BVal project continues on limited manpower.
## PMC changes:
- Currently 14 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013
## Committer base changes:
- Currently 14 committers.
- No new changes to the committer base since last report.
## Releases:
- Apache BVal 1.1.2 was released on Wed Nov 02 2016
## Mailing list activity:
- The run-up to the 1.1.2 release is reflected by the mailing list
statistics:
- dev@bval.apache.org:
- 43 subscribers (down -1 in the last 3 months):
- 75 emails sent to list (15 in previous quarter)
- user@bval.apache.org:
- 51 subscribers (up 0 in the last 3 months):
- 3 emails sent to list (2 in previous quarter)
## JIRA activity:
- 6 JIRA tickets created in the last 3 months
- 22 JIRA tickets closed/resolved in the last 3 months
## Apache BVal Report September 2016 ## 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. ### Releases ### No new releases; last BVal release (v1.1.1) was released February 2016. ### Activity ### Some activity in JIRA and on developer list this quarter. The specification process for Bean Validation v2.0 proceeds; this will inevitably trigger a round of future activity for us to make a compliant release. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 Last quarter the board asked whether BV 2.0 might afford opportunities to identify and onboard new personnel to the project. That is possible but probably not especially likely; the PMC would be happy to consider suggestions to enhance the vitality of the project. However, because BVal is incorporated into Apache TomEE and Apache Geronimo, it is to be expected that one or both of these projects might provide manpower when necessary to ensure the availability of a compliant and compatibly-licensed implementation of the Bean Validation specification.
## Apache BVal Report June 2016 ## 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. ### Releases ### No new releases; last BVal release (v1.1.1) was released February 2016. ### Activity ### No activity to speak of this quarter. The specification process for Bean Validation v2.0 is beginning to get underway which will inevitably trigger a round of activity for Apache BVal to make a compliant release. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
The Apache BVal project implements the Java EE Bean Validation specifications (v1 and 1.1) and related extensions, and became a top-level project of the foundation on February 15, 2012. ### Releases ### Last BVal release (v1.1.1) was released on Feb, 2016. ### Activity ### Few direct activity but some indirect thanks to Apache TomEE mainly which gave feedback on 1.1.x releases. Since there is no new version of the Bean Validation specification the project is until next one mainly in maintenance and enhancement modes. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
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. ### Releases ### No new releases. Apache BVal 1.1.0 was released on June 10, 2015. ### Activity ### Some light JIRA and mailing list activity this quarter. Unfortunately none of us has had quite enough time to respond to these fairly recent reports as yet. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
## Apache BVal Report September 2015 ## 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. ### Releases ### Apache BVal 1.1.0 was released on June 10, 2015. ### Activity ### Some light JIRA and mailing list activity this quarter. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
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. ### Releases ### The Apache BVal 1.1.0 release vote passed on June 9, 2015. The formal release process continues. ### Activity ### A small flurry of activity has brought the 1.1.0 release to pass. Because Apache BVal's semantic version numbers are intended to track the version of the Bean Validation specification targeted, this has resulted in the 1.1.0 release (implementing Bean Validation 1.1) actually having preceded a 1.0.0 release, which remains outstanding. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
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. ### Releases ### No new releases. Last release was v0.5 in September 2012. ### Activity ### Our activity level certainly does not mark us as a glamorous project; there has been a single commit since the report of Q4 2014. Mailing list traffic is nonexistent. Once again, there is little reason to fear we would be unable to release from a voting perspective, but our current level of developer "steam" is such that a release vote is not a concern for the immediate future. All hope is not lost but volunteer burnout is certainly a factor. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
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. ### Releases ### No new releases. Last release was v0.5 in September 2012. ### Activity ### The Commons Weaver quasi-dependency bottleneck has as long last been resolved and BVal development has resumed. We continue to work with the Apache TomEE PMC, who bundle our project and thereby provide a clear barometer for ease of integration. I note the question on the agenda of whether we have enough committers to make releases... I assume this refers to BVal, though it could have referred to Commons as we did spend an unfortunate amount of time blocked there. While the developer energy of most of the PMC is being expended elsewhere, I believe we have strong enough representation amongst the wider "ApachEE" (i.e. JEE at Apache) community to be handily able to garner the votes for a release once we are satisfied with the state of the codebase. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
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. ### Releases ### No new releases. ### Activity ### Low, but clearly discernible, JIRA/commit activity this quarter. Currently the project has but one active committer. A lack of volunteer availability/energy has left the Commons Weaver dependency situation yet unresolved, but all things in time. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
@Chris: does the project have enough committers to make releases?
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. ### Releases ### No new releases. ### Activity ### BVal saw an increase in traffic to its dev@ and user@ mailing lists this quarter. Several of these threads culminated in contributions of code and documentation, some of which have already been adopted. The board may recall the ongoing saga of releasing the Commons Weaver component for use by BVal; we encountered a small setback after Commons Weaver's 1.0 release upon discovering a blocking bug in one of *its* dependencies (exposed by the BVal trunk code). We thus engaged the third Apache community in the chain (Geronimo) with the result that Weaver 1.1 is currently undergoing a release vote. A la Bullwinkle, "This time for sure!" but we expect to have cleared the path to finish BVal 1.0 and 1.1 once this is complete. ### Community ### No changes in community. Last PMC member added Q4 2013 Last committer added Q3 2013 ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
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. ### Releases ### No new releases. ### Activity ### Development has proceeded at what can charitably be termed a crawl for the past year while BVal's team have been expending their volunteer energies elsewhere. A large obstacle has just been removed, however, in the form of the Apache Commons Weaver component, which has just seen its 1.0 release. This project had been one of the aforementioned time/energy sinks and was developed for the express purpose of solving one of BVal's long-standing design problems; speaking on behalf of the PMC I am hopeful that we can now resume a respectable development velocity and finally make our 1.0 and 1.1 (implementing, respectively, the same versions of the Java Bean Validation specification) releases in the near future. ### Community ### No changes in community. Romain Manni-Bucau was added to the PMC during the previous quarter after having been elected a committer the quarter before that. ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
## Apache BVal Report December 2013 ## 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. ### Releases ### No new releases. ### Activity ### Releasing our 1.0 and 1.1 versions, to coincide with Java Bean Validation 1.0 and 1.1 respectively, has been discussed and a basic approach seems to have been agreed upon. BVal's developers are busy all over the place (in many cases with other Apache projects) with a general shortage of "round tuits", but we remain optimistic that the releases will be made. Mailing list traffic picked up a bit this quarter. ### Community ### Romain Manni-Bucau has been added to the PMC. ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
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. ### Releases ### No new releases. ### Activity ### Java Bean Validation v1.1 has been implemented in a branch that successfully passes the TCK. Previous reports have mentioned that BVal awaited the availability of the new Commons [weaver] component, which is mostly baked and should have been released by the time that PMC reports again in December. The PMC must next determine a strategy to finalize its 1.0 API and merge this work with that having been done on the 1.1 branch to release both codebases. Mailing list traffic continues to be minimal. ### Community ### A new committer, Romain Manni-Bucau, has been welcomed to the BVal roster. Romain is the driving force behind the implementation of spec v1.1. ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
The Apache BVal project implements the Java EE Bean Validation 1.0 (JSR-303) specification and related extensions, and became a top-level project of the foundation on February 15, 2012. ### Releases ### No new releases. ### Activity ### BVal has experienced very little activity as of late. As time permits we have one team member working in the Commons community on a component that will help simplify BVal's code and, manpower being what it is, other BVal development has stalled awaiting the availability of this component (Commons [weaver], which will allow BVal to streamline/simplify the code it uses to operate in secured Java runtime environments). Mailing list traffic continues to be minimal. The Java Bean Validation specification v1.1 has been released last month; when BVal development resumes in earnest implementing this version of the specification is a top priority. ### Community ### No changes. ### Branding ### Nothing to report. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
The Apache BVal project implements the Java EE Bean Validation 1.0 (JSR-303) specification and related extensions, and became a top-level project of the foundation on February 15, 2012. ### Releases ### No new releases. ### Activity ### Part of the BVal community is engaged at Apache Commons, working on the [weaver] component (subject of my Fast Feather talk at ApacheCon NA 2013) which, when completed, is planned to be used in BVal's code. Mailing list traffic continues to be minimal. We continue to follow the progress of the Bean Validation specification; its 1.1.0 version is being developed under Red Hat's (open) leadership as JSR-349. Apache BVal will implement Bean Validation v1.1.0 as soon as is practical. ### Community ### Mohammad Nour El-Din has resigned from the PMC. ### Branding ### The BVal site has been restyled using a Twitter bootstrap foundation, and incorporating the new logo. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
The Apache BVal project implements the Java EE Bean Validation 1.0 (JSR-303) specification and related extensions, and became a top-level project of the foundation on February 15, 2012. ### Releases ### Apache BVal version 0.5 was released on September 21--just after our last report to the board! This was a quick turnaround release, addressing a fairly serious regression (hence the last report's complete omission of any mention of an impending release). ### Activity ### Development has begun to pick back up with some feints at solving one of our outstanding design issues; this has led to some interesting inter-project discussion, and looks poised to result in the creation of a new utility among the libraries provided by Apache Commons. Mailing list traffic continues to be minimal. We continue to follow the progress of the Bean Validation specification; its 1.1.0 version is being developed under Red Hat's (open) leadership as JSR-349. Apache BVal will implement Bean Validation v1.1.0 as soon as is practical. ### Community ### No changes in community. ### Branding ### Re-styling the website to incorporate our new logo remains an open task. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
The Apache BVal project implements the Java EE Bean Validation 1.0 (JSR-303) specification and related extensions, and became a top-level project of the foundation on February 15, 2012. ### Releases ### No releases since the last report. ### Activity ### Little development activity of late; most of the BVal team are spread across various ASF projects, so we've not yet been able to make good on our intentions to continue improving the codebase towards a 1.0 release. Traffic on the user mailing list remains low/nonexistent. We continue to follow the progress of the Bean Validation specification; its 1.1.0 version is being developed under Red Hat's (open) leadership as JSR-349. Apache BVal will implement Bean Validation v1.1.0 as soon as is practical. ### Community ### No changes in community. ### Branding ### The project has adopted (though not yet re-branded with) a new logo contributed by Adonis Raduca. The PMC thanks him for his contribution, as well as his employer, IRIAN Solutions, for his time. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
The Apache BVal project implements the Java EE Bean Validation 1.0 (JSR-303) specification and related extensions, and became a top-level project of the foundation on February 15, 2012. ### Releases ### No releases since the last report. ### Activity ### We've seen just a bit of externally-initiated activity in JIRA this month, a welcome contribution ensuring our codebase is compatible with some minor compiler changes in Java 7. Most of the BVal team are spread across various ASF projects, so we've not yet been able to make good on our intentions to continue improving the codebase towards a 1.0 release. Traffic on the user mailing list remains low/nonexistent. We continue to follow the progress of the Bean Validation specification; its 1.1.0 version is being developed under Red Hat's (open) leadership as JSR-349. Apache BVal will implement Bean Validation v1.1.0 as soon as is practical. ### Community ### Some interest indicated by an ASF member who had not previously contributed to BVal. ### Branding ### IRIAN donated some graphic design resource time to BVal and has given us a starting point for a new logo. We have yet to finalize the community's preferences for how, if at all, it should be changed before adoption, but IRIAN's efforts are greatly appreciated! ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
The Apache BVal project implements the Java EE Bean Validation 1.0 (JSR-303) specification and related extensions, and became a top-level project of the foundation on February 15, 2012. ### Releases ### BVal proudly made its first non-incubating release, version 0.4, on April 14, 2012. Ours was incorporated into the better-publicized Apache TomEE 1.0 release. ### Activity ### Since the release of BVal 0.4, there has been no activity to speak of. Our next goals are to continue improving the codebase for BVal 1.0. Traffic on the user mailing list remains low/nonexistent. We continue to follow the progress of the Bean Validation specification; its 1.1.0 version is being developed under Red Hat's (open) leadership as JSR-349. Apache BVal will implement Bean Validation v1.1.0 as soon as is practical. ### Community ### No new faces in the community. ### Branding ### The task of creating a new project logo remains open. ### Legal ### No concerns at present. ### Infrastructure ### Nothing needed at the moment.
The Apache BVal project implements the Java EE Bean Validation 1.0 (JSR-303) specification and related extensions, and became a top-level project of the foundation on February 15, 2012. ### Releases ### BVal version 0.3-incubating was released April 28, 2011. The PMC is currently voting to release BVal 0.4 RC1, which will be integrated into OpenEJB's imminent TomEE release. ### Activity ### Recent activity has focused on the 0.4 release, with an eye to the project's long-term goals (e.g. minimizing dependencies). Our next goals are to continue improving the codebase so that we can make, as soon as possible, a 1.0 release with the best possible interface with which to provide reliability to our user base. Discussions in this regard have already begun. Traffic on the user mailing list remains low/nonexistent. As always, we consider that to be merely in the nature of providing an implementation of a wider-known specification: the reference implementation gets the user traffic. We continue to follow the progress of the Bean Validation specification; its 1.1.0 version is being developed under Red Hat's (open) leadership as JSR-349. Certain of the features of specification version 1.1.0 duplicate custom functionality already implemented in BVal; these must of course be merged. Apache BVal will implement Bean Validation v1.1.0 as soon as is practical. ### Community ### The composition of the team has not changed since graduation, at which time all committers became members of the inaugural PMC. The PMC is quite diverse and we are satisfied that no entity has undue influence in our decision-making process. ### Branding ### The task of creating a new project logo remains open, though some positive discussion has taken place and seems to be heading in the direction of satisfying interested parties. ### Legal ### No concerns at present. ### Infrastructure ### We have some outstanding features we'd like to implement on our project website (specifically a news or blog feed), and may seek advice and/or support from infrastructure to accomplish this.
The Apache BVal project implements the Java EE Bean Validation 1.0 (JSR-303) specification and related extensions, and became a top-level project of the foundation on February 15, 2012. ### Releases ### BVal version 0.3-incubating was released April 28, 2011. The PMC is actively discussing making its first non-incubating release in the *immediate* future. We are highly motivated because as members of the Java EE ecosystem @ Apache we like to cooperate and coordinate with the release schedules of related projects (e.g. OpenJPA, Geronimo) whenever possible. ### Activity ### Since graduating to TLP status, activity has focused on post-graduation tasks, primarily the migration of the BVal website from Confluence to the Apache CMS. We continue to follow the progress of the Bean Validation specification; its 1.1.0 version is being developed under Red Hat's (open) leadership as JSR-349. Apache BVal will implement Bean Validation v1.1.0 as soon as is practical. Finally, we have established a #bval channel on Freenode IRC. We continue to make decisions on-list, but we hope that our availability on IRC will help build a sense of team camaraderie, and allow us to resolve simple questions in a more synchronous manner. ### Community ### The composition of the team has not changed since graduation, at which time all committers became members of the inaugural PMC. The PMC is quite diverse and we are satisfied that no entity has undue influence in our decision-making process. ### Branding ### Most of the team (and everyone else who has been asked) harbor some level of dislike for BVal's existing logo, the "check mark made of coffee beans." One of our ongoing tasks is the direction/selection/creation of a new project logo. ### Legal ### No concerns at present. ### Infrastructure ### We have some outstanding features we'd like to implement on our project website (specifically a news or blog feed), and may seek advice and/or support from infrastructure to accomplish this.
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software related to the Bean Validation
Specification and its implementation as Apache BVal
for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache BVal Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache BVal Project be and hereby is
responsible for the creation and maintenance of software
related to creating an implementation compliant with the
Bean Validation Specification and a library of pre-developed
validators and extensions; and be it further
RESOLVED, that the office of "Vice President, Apache BVal" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache BVal Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache BVal Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache BVal Project:
- Albert Lee <allee8285@apache.org>
- Carlos Vara Callau <carlosvara@apache.org>
- David Jencks <djencks@apache.org>
- Donald Woods <dwoods@apache.org>
- Gerhard Petracek <gpetracek@apache.org>
- Jeremy Bauer <jrbauer@apache.org>
- Kevan Lee Miller <kevan@apache.org>
- Luciano Resende <lresende@apache.org>
- Matthias Wessendorf <matzew@apache.org>
- Matthew Jason Benson <mbenson@apache.org>
- Mohammad Nour El-Din <mnour@apache.org>
- Roman Stumm <romanstumm@apache.org>
- Simone Tripodi <simonetripodi@apache.org>
- Mark Struberg <struberg@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matthew Jason Benson
be appointed to the office of Vice President, Apache BVal, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache BVal PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache BVal Project; and be it further
RESOLVED, that the Apache BVal Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Bean Validation podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Bean Validation podling encumbered upon the Apache
Incubator Project are hereafter discharged.
Special Order 7F, Establish the Apache BVal Project, was
approved by Unanimous Vote of the directors present.
Bean Validation was accepted into Incubator on 1 March 2010. The Bean Validation project is an implementation of the Java EE Bean Validation JSR303 specification. There are no other important issues open before a possible graduation. The project has agreed to seek status as a TLP, and has agreed by an internal vote on its readiness to graduate [1]. The primary task outstanding is the completion of a charter. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * none How has the community developed since the last report * Mailing list and JIRA activity are extremely quiet. We attribute this to the nature of the podling, being but an implementation of a specification, and the level of achievement of conformity to that specification. How has the project developed since the last report * we have upgraded to and continue to pass the latest available version of the JSR303 TCK. * we continue to track the progress of the JSR303 spec for the future. [1] http://markmail.org/thread/5wrg6zgj7s66dnwg
Bean Validation was accepted into Incubator on 1 March 2010. The Bean Validation project is an implementation of the Java EE Bean Validation JSR303 specification. There are no other important issues open before a possible graduation. Actually the project is discussing its graduation as TLP or into Apache Commons, as natural successor of Commons Validator. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * none How has the community developed since the last report * Users community activity is stable, users slightly decreased the activity of filling issues on JIRA and asking questions, we suppose codebase/provided documentation start being mature enough to satisfy users needs. How has the project developed since the last report. * Started a 'extras' module development where putting validators not included in the JSR303 spec. * planning the development for implementing next JSR330 spec version.
Bean Validation was accepted into Incubator on 1 March 2010. The Bean Validation project is an implementation of the Java EE Bean Validation JSR303 specification. There are no other important issues open before a possible graduation. Actually the project is discussing its graduation as TLP or into Apache Commons, as natural successor of Commons Validator. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * none How has the community developed since the last report * Users community activity is stable, users slightly decreased the activity of filling issues on JIRA and asking questions, we suppose codebase/provided documentation start being mature enough to satisfy users needs. How has the project developed since the last report. * Started a 'extras' module development where putting validators not included in the JSR303 spec. * planning the development for implementing next JSR330 spec version.
Apache Bean Validation will deliver an implementation of the JSR303 Bean Validation 1.0 specification. BVAL entered incubation on March 1, 2010. A list of the three most important issues to address in the move towards graduation. * Perform successful Releases - Done * Grow the community and committer base - stale at a medium level * Decide on graduation target of TLP or subproject - TBD The BVAL community is still discussing about the 3 possible graduation scenarios: * Graduate as TLP * Graduate as part of Apache Commons * Graduate under the Geronimo TLP The codebase is mature and stable, thus there is not much development effort going on atm. Otoh this means that there are not many developers working actively on BVAL. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of? . None at this time. How has the community developed since the last report? . No new committers. How has the project developed since the last report? . 0.3-incubating was released on 2011-02-04.
Failed to report. There is some degree of activity on its mailing lists, and addition of new Committers.
The community missed their December quarterly report. So, are submitting this report in January. Summary The community has been active with discussions on the dev list and code updates. A new 0.3 release has been discussed, but is not yet underway. Community * No new committers... * No new PMC members... Development * No new releases, but a 0.3 release has been discussed. * Work on annotations for commons-lang 3 * Many bug fixes Project Branding * Not started yet.
Did not report.
Apache Bean Validation will deliver an implementation of the JSR303 Bean Validation 1.0 specification. BVAL entered incubation on March 1, 2010. A list of the three most important issues to address in the move towards graduation. * First release of artifacts - Done * Grow the community and committer base - ongoing * Decide on graduation target of TLP or subproject - TBD Any issues that the Incubator PMC or ASF Board might wish/need to be aware of? * None at this time. How has the community developed since the last report? * New committer Matt Benson has started working on a branch to upgrade to commons-lang v3. How has the project developed since the last report? * 0.2-incubating was released on August 20th.
Apache Bean Validation will deliver an implementation of the JSR303 Bean Validation 1.0 specification. BVAL entered incubation on March 1, 2010. A list of the three most important issues to address in the move towards graduation. * First release of artifacts - Done * Grow the community and committer base - ongoing * Decide on graduation target of TLP or subproject - TBD Any issues that the Incubator PMC or ASF Board might wish/need to be aware of? * None at this time. How has the community developed since the last report? * Committer offer was extended and accepted by Matt Benson. * A couple of new users on the dev list. How has the project developed since the last report? * Currently a 0.2-incubating RC2 release vote is underway.
Apache Bean Validation will deliver an implementation of the JSR303 Bean Validation 1.0 specification. BVAL entered incubation on March 1, 2010. A list of the three most important issues to address in the move towards graduation. * First release of artifacts - Done * Grow the community and committer base - ongoing * Decide on graduation target of TLP or subproject - TBD Any issues that the Incubator PMC or ASF Board might wish/need to be aware of? * None at this time. How has the community developed since the last report? * PPMC membership was extended and accepted by Carlos Vara. * Committer offer was extended and accepted by David Jencks. * Growing activity on the dev list for two potential committers. How has the project developed since the last report? * Started discussions about potential content for a 0.2-incubating release. * Bean Validation benchmark app contributed by Carlos Vara to help with performance testing against the Hibernate RI.
Apache Bean Validation will deliver an implementation of the JSR303 Bean Validation 1.0 specification. BVAL entered incubation on March 1, 2010. A list of the most important issues to address in the move towards graduation * First release of artifacts. * Grow the community and committer base. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * None at this time. How has the community developed since the last report * Committer offer was extended and accepted by Carlos Vara. * Apache Geronimo has started using our artifacts in their 3.0 builds for Java EE 6. * Apache OpenJPA has started creating a image-gallery sample that shows how JPA2 and our Bean Validation implementation can be used together. How has the project developed since the last report * Rsync of Confluence content to our website is now setup. * Code has been passing the Bean Validation TCK since May 21. * We completed our first release on June 11, 2010, which was released as 0.1-incubating.
Apache Bean Validation will deliver an implementation of the JSR303 Bean Validation 1.0 specification. BVAL entered incubation on March 1, 2010. A list of the three most important issues to address in the move towards graduation: First release of artifacts. Grow the community and committer base. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of: None at this time. How has the community developed since the last report: The community has been focused on resolving TCK failures, with lots of help coming from contributor Carlos Vara. Apache OpenJPA trunk is now using our artifacts as their default provider for Bean Validation testing. Two other projects (one at the ASF) have mentioned they are using our artifacts instead of Hibernate. How has the project developed since the last report: Confluence is setup as our website and has been fully populated. SNAPSHOT artifacts are being published to repository.apache.org. TCK testing is being run by 3 or 4 committers and contributors.
Bean Validation will deliver an implementation of the JSR303 Bean Validation 1.0 specification. There are currently no issues requiring IPMC or Board attention. Since Bean Validation entered incubation on March 1, 2010, we have accomplished the following: 1. Initial project resources and accounts created 2. Initial code contribution under SGA from Agimatec GmbH imported into svn 3. Source code package names updated from com.agimatec to org.apache.bval 4. Agimatec copyright moved to NOTICE files and removed from source 5. Three committers are already active making code updates 6. Started setup of our Confluence space as our main website 7. Already have one non-committer using the code and submitting patches Upcoming major goals: 1. Finish setup of website 2. Setup and usage of Nexus 3. First release of artifacts 4. Start TCK testing Top 2 or 3 things to resolve before graduation: 1. Build community 2. Create at least one release