Hello River folk,

Please review or make any suggestions you'd like to communicate to the board.

Regards,

Peter.

As per the boards request we discussed the Attic and there was strong support for continuing the River project, despite activity being relatively quiet, it does appear that the board was not aware of our commit history due to the project's use of svn and a stable trunk branch.  Development is currently performed in the modules branch, which doesn't appear on github or show up in commit statistics.

Since the boards request to consider the attic, the project team has voted to change from svn to git, however due to the number of branches and separate components, we are still trying to figure out how to execute the change.   Additionally the project has also voted to change the modular build from Maven to Gradle.

The River project typically operates in maintenance mode, however there is an ongoing long term undertaking to make River's monolithic codebase modular.

The modules branch will become the stable trunk branch after the next release, this modular build has been a significant undertaking, hence the long time since the project's last release.

##Commit statistics (from comm...@river.apache.org):

July 2020    64 commits

May 2020    12 commits

Sept 2019    1 commit

Aug 2019    32 commits

June 2019    8 commits

May 2019    71 commits

Dec 2018    3 commits

Nov 2018    2 commits

May 2018    3 commits

Apr 2018    2 commits

Mar 2018    8 commits

Feb 2018    48 commits


## 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 1516% increase in traffic in the past quarter (97 emails compared to 6):

2 issues opened in JIRA, past quarter (200% increase)

## Busiest email threads:

 * dev@river.apache.org/Board feedback - Request discuss attic for
   River/(17 emails)
 * dev@river.apache.org/Maven build/(14 emails)
 * dev@river.apache.org/Example Gradle Buuild/(11 emails)
 * dev@river.apache.org/Vote: Change from subversion to git/(7 emails)
 * dev@river.apache.org/Workaround for JDK 14.0.1 and TLS:
   -Djdk.tls.server.enableSessionTicketExtension=false/(6 emails)
 * dev@river.apache.org/Gradle Build [PREVIOUSLY] Re: Board feedback -
   Request discuss attic for River/(5 emails)
 * dev@river.apache.org/Further update regarding firewall and NAT
   issues in River/(4 emails)
 * dev@river.apache.org/svn commit: r1879695 - in
   /river/jtsk/modules/modularize/apache-river: ./ browser/ dist/
   extra/ phoenix-activation/phoenix-common/
   phoenix-activation/phoenix-dl/ phoenix-activation/phoenix-group/
   phoenix-activation/phoenix/ phoenix-activation/phoenix/s.../(4 emails)
 * dev@river.apache.org/Proxy identity behaves unexpectedly for secure
   services./(3 emails)
 * dev@river.apache.org/Draft Report River - May 2020/(3 emails)

## Busiest JIRA tickets:

 * RIVER-471 <https://issues.apache.org/jira/browse/RIVER-471>/Untangle
   circular links between modules/(0 comments)
 * RIVER-472 <https://issues.apache.org/jira/browse/RIVER-472>/Gradle
   build/(0 comments)

Reply via email to