+1
Thanks!

    On Friday, 1 October 2021, 10:34:51 am NZDT, Andy Seaborne 
<a...@apache.org> wrote:  
 
 ## Description:
The mission of Jena is the creation and maintenance of software related 
to Java framework for building Semantic Web applications

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Jena was founded 2012-04-18 (9 years ago).
There are currently 18 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 9:7.

Community changes, past quarter:
- No new PMC members. Last addition was Aaron Coburn on 2019-01-22.
- No new committers. Last addition was Greg Albiston on 2019-07-08.

## Project Activity:
Jena version 4.2.0 was released 2021-09-12. It fixed CVE-2021-39239, 
which was discovered by the team, and affects all version 4.1.0 and earlier.

The release was not just about a CVE fix. The release included a new
component, a data validation engine for the ShEx language to go 
alongside the SHACL engine; and also support for reading JSON-LD 1.1 
using an external 3rd party library. JSON-LD 1.1 is used by some IOT 
device and service descriptions.

During the release checking, a problem was discovered in the OSGi bundle
related to the new dependencies for JSON-LD 1.1 handling. The project 
dropped the OSGi convenience binaries, and a discussion has started 
about retiring them. The development community no longer has the skills, 
nor interest, necessary to maintain their production. Contact with known 
downstream open source projects, and a message to users@ has not 
produced any concern.

Jena has a process for retiring modules - delete in git, record the last 
git commit with the code in case some interest emerges and will maintain 
the module.

## Community Health:
Activity seems normal. Some of the figures are slightly skewed because 
one PR had 48 commits which is unusual for Jena.

The dev@ list is also the destination of JIRA email and is otherwise 
quite quiet. The speed of evolution of the project is down to developer 
time.

The users@ is active and the main support channel.
  

Reply via email to