Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

## Project Activity:
Releases:
 - no recent releases, 2.15.0 (latest stable) was released on 2023-05-02.
Events:
 - Ignite Summit 2023 was held on June 6, virtual event with more than 500
   registrations.

## Community Health:
- There are several open discussions about new committers and a couple of
  votes are open.
- There is a sligth decrease in the dev list, PR, and JIRA activity.
- The number of commits, GitHub opened and closed issues increased
  compared to the previous quarter.
- PMC discussed subscription of contibutor without commit bit to the security
  list (jury.gerzhedowich@gmail.com) and we agree to keep that subscription.
  Yury helped with security issues in SQL engine in the past and currently he is
  a candidate to committership. Also he would like to volunteer by monitoring
  security list security list.

Nov 2023

## Description:
The mission of Ignite project is the creation and maintenance of software
related to high-performance distributed database engine providing in-memory
and persistent data caching, partitioning, processing, and
querying components.

## Project Status:
Current project status: Ongoing
Issues for the board: none

## Membership Data:
Apache Ignite was founded 2015-08-19 (8 years ago)
There are currently 75 committers and 39 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- No new PMC members. Last addition was Ivan Daschinsky on 2022-09-15.
- Aleksandr Polovtsev was added as committer on 2023-08-17
- Stephen Darlington was added as committer on 2023-08-24

## Project Activity:
Releases:
 - no recent releases, 2.15.0 (latest stable) was released on 2023-05-02.
 - next release 2.16.0 was proposed by Nikita Amelchev to be finalized at the
   end of November. This release will improve Apache Calcite engine support,
   cluster management API, and add support of JDK 14-21.

## Project Activity:
Releases:
 - no recent releases, 2.15.0 (latest stable) was released on 2023-05-02.
 - next release 2.16.0 was proposed by Nikita Amelchev to be finalized at the
   end of November. This release will improve Apache Calcite engine support,
   cluster management API, and add support of JDK 14-21.

Other activity:
 - Machine Learning (ML) module was moved to ignite-extensions.
 - Transactions engine code cleanup is in progress (MVCC removal).
 - Community discusses discontinuing JDK 8 support.
 - Performance improvement proposed for peristence engine and storing
   checkpoint recovery data.

## Community Health:
 - There is notable traffic decrease in userlist (96 emails compared to 200 in
   the past quarter). This might be caused by opening Github issues for users.
 - There is decrease in commits, JIRA and Github issues opened (-20-30%).
 - Count of issues closed increased both in JIRA and GitHub (+20-50%).
 - Community attracts new contributors, JIRA accounts are requested. Number of
   code contributors has been increased (+23%).
 - security@ list subscription of non-PMC member was cancelled
   (jury.gerzhedowich@gmail.com). 

Feb 2024


## Description:
The mission of Ignite project is the creation and maintenance of software
related to high-performance distributed database engine providing in-memory
and persistent data caching, partitioning, processing, and
querying components.


## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache Ignite was founded 2015-08-19 (8 years ago)
There are currently 76 committers and 40 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.

Community changes, past quarter:
- Nikita Amelchev was added to the PMC on 2023-11-20
- Iurii Gerzhedovich was added as committer on 2024-02-09
## Project Activity:  
 - 2.16.0 (latest stable) was released on 2022-11-17.
 - ML has been moved to the separate extenstion.
 - This extracted ML Extension 1.0 was released on 2022-11-17.
 - Maintainers are fixing a number of Apache Calcite integration issues, this
   will allow us to discontinue H2 and overcome H2-related security concerns.

## Community Health: 
- Community started to discuss end of JDK 8 support
- There is decrease in the dev list activity (-30%) and in the number of
  open/closed issues(-70%), but other activity metrics are almost the same.
- Project attracts new contributors.