Hello all, I prepare the draft for March 2024, I'm planning to submit this afternoon to avoid any delay. Feedback is welcome.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Project Status: Current project status: Ongoing with high activity Issues for the board: [There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (15 years ago) There are currently 92 committers and 45 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Andrea Tarocchi on 2023-09-11. - Gaelle Fournier was added as committer on 2024-03-06 ## Project Activity: Apache Camel: - We released Camel 3.21.4 - We released Camel 3.22.0 - We released Camel 3.22.1 - We released Camel 4.0.4 - We released Camel 4.3.0 - We released Camel 4.4.0 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is synchronized. - The 4.4.x release is our LTS release train and we are already working on 4.4.1 and next development release 4.5.0 - We continued the release train for 3.21.x LTS - The 3.22.x release train is another LTS we are supporting - The situation is really healthy and the community is super. We are introducing many new features and working on engaging the community more. Apache Camel K: - For Camel K we released a 2.2.0 version with a lot of good stuff. - For Camel-K-runtime we released 3.2.3 and 3.6.0, both the releases were on vote at the time of writing of the last report. - Camel K is in good shape and the community is expading with new contributors and many new good idea. Apache Camel Kamelets: - We released Camel Kamelets 4.0.3 - We released Camel Kamelets 4.4.0 - The 4.4.0 release is matching the LTS release from Camel core and it's an important building block for starting with routes - We introduced a lot of new Kamelets and we are improving the documentation Apache Camel Quarkus: - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 3.7.0 - We released Camel-quarkus 3.8.0 - The 3.8.0 release is matching the 4.4.0 release from Camel core and it will be an LTS - A lot of work has been done on testing side and we are working on supporting more extensions Apache Camel-Karavan: - Camel-Karavan is improving and the community around the project is increasing in number of features and new issues reporting - We released the 4.3.0 - We released the 4.3.1 - We released also the 4.4.0 version matching the LTS version from Camel core Camel-Kafka-Connector: - Camel Kafka Connector release based on Camel 4.0.3 has been released. - We plan to release a 4.4.0 to match the LTS release from camel core - The community is active and we receive a lot of feedback and requests Overall: - The Camel project and all the subprojects are in a really good shape and all of them are growing in terms of community involvement. ## Community Health: - 303 issues opened on GitHub, past quarter (8% decrease) and 277 issues closed on GitHub, past quarter (18% decrease): Some of the subproject are using github issues, but Camel core is still on JIRA. We focused mostly on the LTS 4.4.x and some of the Github Issues based projects were focused on backlog activities and alignments, like for example Camel K. - 4835 commits in the past quarter (2% decrease) and 103 code contributors in the past quarter (13% decrease): We are more or less in line with the last quarter, we were a lot focused on more features for 4.4.x and the number of code contributors is justified by the fact we were stabilizing the codebase. - 1714 PRs opened on GitHub, past quarter (6% decrease) and 1726 PRs closed on GitHub, past quarter (5% decrease): Here we are more or less in line with the last quarter. The situation is really good and we are observing more engagement in open PRs. - dev@camel.apache.org had a 21% decrease in traffic in the past quarter (330 emails compared to 416): There was a spike in December and now we are back at usual level. We are discussing some release scheduling in dev ML and we noticed many developers prefer to discuss directly in Zulip. - iss...@camel.apache.org had a 18% decrease in traffic in the past quarter (2423 emails compared to 2935): We were focusing on backlog and the clean up done in the last quarter justify the decrease. - us...@camel.apache.org had a 18% decrease in traffic in the past quarter (202 emails compared to 245): Users are starting to move and ask questions on Zulip, like the discussion for development. - Jira Activity: The number doesn't seem to be accurate in the statistics page. It reports 0 issues opened and 0 closed. Closing the subscriptions to Apache JIRA contributed to the decrease of numbers. I'll try to gather more stats in the next report.
