Hello all,

I prepared the draft for March Board Report. I would like to submit on
Monday. 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 (16 years ago)
There are currently 94 committers and 47 PMC members in this project.
The Committer-to-PMC ratio is 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Colm O hEigeartaigh on 2024-03-11.
- No new committers. Last addition was Thomas Diesler on 2024-11-22.

## Project Activity:
Apache Camel:
- We released Camel 3.22.4
- We released Camel 4.8.3
- We released Camel 4.8.4
- We released Camel 4.10.0
- We released Camel 4.10.1
- We are in the process of releasing 4.8.5 for the 4.8.x LTS line
- We are in the process of releasing 4.10.2 for the 4.10.x LTS line
- 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.
- 4.8.x is our last LTS release train. We released the main version 4.8.0
with
  two others patch releases 4.8.3 and 4.8.4
- The situation is really healthy and the community is super. We are
  introducing many new features and working on engaging the community more.
  Camel is growing even in terms of interest

Apache Camel K:
- We released the 2.5.1 version
- We released the 2.6.0 version
- For Camel-K-runtime we released 3.15.2, for 2.5.x work.
- Camel K is in good shape and the community is expading with new
contributors
  and many new good idea and many good interactions. The situation is
healthy.

Apache Camel Kamelets:
- We released Camel Kamelets 4.8.3
- We released Camel Kamelets 4.8.4
- We released Camel Kamelets 4.10.0
- We released Camel Kamelets 4.10.1
- The 4.8.x release train 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
  by focusing on much more examples. Also we improved the Kamelets
  description.

Apache Camel Quarkus:
- The Camel-Quarkus work is going ahead following the main camel releases
with
  multiple releases
- We released Camel-quarkus 3.15.2
- We released Camel-quarkus 3.17.0
- We released Camel-quarkus 3.18.0
- We released Camel-quarkus 3.19.0
- The 3.15.x is matching the 4.8.x release train from the main project
- A lot of work has been done on testing side more new features and
extensions
  have been developed and improved.

Apache Camel-Karavan:
- Camel-Karavan is improving and the community around the project is
  increasing in number of features and new issues reporting. It's growing.
- We released the 4.10.0
- We released the 4.8.1
- The 4.10.x is aligned to Camel 4.10.x LTS

Camel-Kafka-Connector:
- 4.8.3 has been released and based on the last LTS release train 4.8.0
- The community is active and we receive a lot of feedback and requests. We
  are improving the documentation.

Apache Camel-Karaf:
- Camel-karaf main branch has been updated and now works with Camel 4.9.0
and
  Karaf 4.4.7+. Many new contributors are helping on this.
- We released also 3.22.4 for this project.

## Community Health:
- dev@camel.apache.org had a 9% increase in traffic in the past quarter (361
  emails compared to 330): Related to release planning and more heads up
- iss...@camel.apache.org had a 4% decrease in traffic in the past quarter
  (2138 emails compared to 2221): Most of the projects are now using Github
as
   first way of opening issues, so the decrease is somewhat expected.
- us...@camel.apache.org had a 31% increase in traffic in the past quarter
  (182 emails compared to 138): Users are starting to move and ask questions
   on Zulip, but we had many discussion around releasing and questions from
   users
- PRs opened: 1450, 18% decrease. This is because we slowed down on some
  subprojects.
- PRs closed: 1460, 17% decrease. Same reason.
- Issues opened 169, 34% decrease. The reason is related to the slowing down
  on some subprojects.
- Issues closed 190, 25 decrease. Same reason.

Reply via email to