Hello River folk,
Please review or make any suggestions you'd like to communicate to the
board.
Regards,
Peter.
The River project typically operates in maintenance mode, however there
is an ongoing long term undertaking to make River's monolithic codebase
modular.
The project has voted to move from SVN to Git.
The modules branch will become the trunk branch after the next release,
this modular build has been a significant undertaking, hence the long
time since the project's last release.
## Description:
The mission of River is the creation and maintenance of software related to
Jini service oriented architecture
## Issues:
No issues warranting attention at this time.
## Membership Data:
Apache River was founded 2011-01-19 (10 years ago)
There are currently 16 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Dan Rollo on 2017-12-01.
- No new committers. Last addition was Dan Rollo on 2017-11-02.
- Recently we have received new contributions and we are likely to see
new additions in the near future.
## Project Activity:
River-3.0.0 was released on 2016-10-06.
river-jtsk-2.2.3 was released on 2016-02-21.
river-examples-1.0 was released on 2015-08-10.
## Community Health:
dev@river.apache.org had a 75% decrease in traffic in the past quarter
(24 emails compared to 96)
## Busiest email threads:
* dev@river.apache.org/[VOTE]: make trunk an unstable development
branch./(8 emails)
* dev@river.apache.org/Example Gradle Buuild/(4 emails)
* dev@river.apache.org/August Board Report [DRAFT]/(3 emails)
* dev@river.apache.org/Your project website/(2 emails)
* dev@river.apache.org/Why jtreg/(2 emails)
* dev@river.apache.org/Git repository/(2 emails)
* dev@river.apache.org/Serialization and serial form/(1 emails)
* dev@river.apache.org/Java Deserialization CVE's/(1 emails)
* dev@river.apache.org/Problems starting Infra services with new
build/(1 emails)
