Hello all, Here is the draft for March board report. I'm planning to submit it soon, so if you have feedback please let me know. Thanks.
## Description: The mission of Apache Camel is the creation and maintenance of an open-source integration framework based on known Enterprise Integration Patterns. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Camel was founded 2008-12-17 (13 years ago) There are currently 81 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Antonin Stefanutti was added to the PMC on 2022-01-28 - Otavio Rodolfo Piske was added to the PMC on 2022-01-21 - Zineb Bendhiba was added to the PMC on 2022-01-24 - Karen Lease was added as committer on 2022-01-24 - Nicolas Filotto was added as committer on 2022-03-01 ## Project Activity: - We released Camel 3.7.7 - We released Camel 3.11.5 - We released Camel 3.14.0 - We released Camel 3.14.1 - We released Camel 3.15.0 - Note: Camel releases have synchronized releases of Camel-Karaf and Camel-Spring-Boot too - We released 3.14.0 and 3.14.1: This is an LTS release train. We are going to continue releasing 3.14.x and 3.11.x, while we are preparing to the next LTS 3.17.x. We are working hard on 3.16.0 release, with a lot of new features. - We released Camel K 1.8.0 - We released Camel K 1.8.1 - We released Camel K 1.8.2 - Related to Camel K we have also Camel K Runtime releases - We released Camel K Runtime 1.11.0 - We released Camel K Runtime 1.12.0 - We are improving the Camel-K experience and we are expanding and improving the Kamelet concept, by introducing more Kameletes to the provided catalog. The amount of Kamelets is increasing in a really impressive way. We are also improving the CLI experience and we are working on involving more contributors by publishing a roadmap for 2022 - The Camel-Quarkus work is going ahead following the main camel releases with multiple releases - We released Camel-quarkus 2.2.1 - We released Camel-quarkus 2.5.0 - We released Camel-quarkus 2.6.0 - We released Camel-quarkus 2.7.0 - On the Camel-Kafka-Connector side we released - 1.0.0 release based on Kamelets - Camel-Kameleon and Camel-Karavan are creating a lot of interest in the community and we are seeing a lot of interactions. ## Community Health: - dev@camel.apache.org had a 4% increase in traffic in the past quarter (454 emails compared to 436): There is a little increase because we had some feedback from user migrating from old Camel 3.x to latest LTS 3.14.x and also because of some queries about Camel K - iss...@camel.apache.org had a 22% increase in traffic in the past quarter (2125 emails compared to 1734): This is related to some new features we are adding to the development release of Camel 3. - us...@camel.apache.org had a 5% decrease in traffic in the past quarter (315 emails compared to 330): The situation is more or less the same of last quarter, the 3.14.x LTS is solid so we have probably less traffic - 461 issues opened in JIRA, past quarter (32% increase) and 411 issues closed in JIRA, past quarter (30% increase): As reported we are working hard on development release and we are also looking at backlog. Note: Jira issues are related to Camel/Camel-Karaf and Camel-Spring-Boot projects - 224 issues opened on GitHub, past quarter (-5% change) and 219 issues closed on GitHub, past quarter (no change): More or less the situation is similar to the last quarter. We have a lot of issues on Github opened for camel-kamelets. Note: Github issues are related to all the subprojects different from Camel/Camel-Karaf/Camel-Spring-Boot - 4105 commits in the past quarter (21% increase) and 115 code contributors in the past quarter (-2% change): the core Camel team is working on new features on the codebase so there is an increase in number of commits, contributions related to documentation and website is increasing. - 1142 PRs opened on GitHub, past quarter (23% increase) and 1147 PRs closed on GitHub, past quarter (24% increase): We have a lot of work done on all the subprojects, so we see a lot of PRs coming from new contributors about documentation but also new features.
