Hello all,

I prepare the draft for Decmeber 2023, I'm planning to submit this
afternoon. Feedback is welcome.

The automatic reminder about preparing the report didn't get out this
month, so I had to write the report faster than usual.

## 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 91 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.
- Aurélien Pupier was added as committer on 2023-11-13
- Jono Morris was added as committer on 2023-11-04
- Vignesh Nayak Manel was added as committer on 2023-09-12

## Project Activity:

Apache Camel:
- We released Camel 3.14.10
- We released Camel 3.20.7
- We released Camel 3.20.8
- We are about to release 3.20.9 at the time of writing (on vote)
- We released Camel 3.21.1
- We released Camel 3.21.2
- We are about to release 3.21.3 at the time of writing (on vote)
- We released Camel 4.0.1
- We released Camel 4.0.2
- We released Camel 4.0.3
- We released Camel 4.1.0
- We released Camel 4.2.0
- We are about to release 4.3.0 at the time of writing (on vote)
- 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 next Camel 4.x LTS release will be 4.4.0 and we're working on that.
- We continued the release train for 3.20.x LTS, and we are about to release
  the last 3.20.x release before the EOL.
- We are still supporting Camel 3.14.x, an LTS train. The release 3.14.10
will
  be the last one before EOL.
- We continued the release train for 3.21.x LTS
- We are working on having also a 3.22.x LTS release in the near future
- The situation is really healthy and the community is super. We are doing a
  lot of improvements and we are introducing new features.

Apache Camel K:
- For Camel K we released a really important 2.1.0 and a 2.0.1 release with
a
  lot of good work from community. It has no coupled dependency from the
  runtime and its release cycle will be decoupled from the core/runtime
  release cycle.
- Camel K Runtime dependency is now matching the release cycle with Camel
  Quarkus.
- For Camel-K-runtime we released 3.2.0
- At the time of writing two releases are on vote too 3.2.3 and 3.6.0
- Camel K is in good shape and we are doing the best we can to improve the
  developer experience.

Apache Camel Kamelets:
- We released Camel Kamelets 4.0.0
- We released Camel Kamelets 4.0.1
- We released Camel Kamelets 4.1.0
- We released Camel Kamelets 4.2.0
- We are working on releasing 4.3.0
- Camel-Kamelets is not only related to camel k anymore so it could be used
  with all the Camel's flavours
- We are improving the overall experience and cleaning up the codebase to
make
  Kamelets runtime agnostic

Apache Camel Quarkus:
- The Camel-Quarkus work is going ahead following the main camel releases
with
  multiple releases
- We released Camel-quarkus 2.16.0
- We released Camel-quarkus 3.2.1
- We released Camel-quarkus 3.2.2
- We released Camel-quarkus 3.2.3
- We released Camel-quarkus 3.4.0
- We released Camel-quarkus 3.5.0
- We released Camel-quarkus 3.6.0
- The health of the project is really good and we are receiving a lot of
  positive feedback and contribution

Camel-Karavan:
- Camel-Karavan is improving and more and more contributors are continuing
to
  help.
- We released the 4.0.0 version matching the LTS release
- We released also the 4.1.0 version
- The work is going really well and the community is starting to give
  feedback.

Camel-Kafka-Connector:
- Camel Kafka Connector release based on Camel 4.0.0 has been released.
- We have a lot of feedback and issues opened and we are working on the
  backlog
- We plan to release a new 4.3.0 release or at most we'll align to the 4.4.0

Overall:
- The Camel project and all the subprojects are in good shape and all of
them
  are growing in terms of community involvement.

## Community Health:
- 313 issues opened on GitHub, past quarter (3% decrease) and 307 issues
  closed on GitHub, past quarter (8% 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.
- 4598 commits in the past quarter (15% decrease) and 119 code contributors
in
  the past quarter (9% decrease):The camel core team is focusing on Camel
  4.4.x. We saw a good number of contributions from new contributors in
  subprojects and main Camel. The number of commits is related also to the
  fact we are starting to use the squash and merge approach instead of the
  rebase and merge.
- 1719 PRs opened on GitHub, past quarter (1% decrease) and 1723 PRs closed
on
  GitHub, past quarter (no change): The number are in line with what we are
  doing right now, we expect an increase of PRs in the next quarter for two
  reasons: we introduce dependabot on core Camel and we are going to release
  multiple LTS releases, so we expect bug fixing and new PRs.
- dev@camel.apache.org had a 3% increase in traffic in the past quarter (427
  emails compared to 411): There was a spike in the dev ML because of
  questions and discussions around the development and final decision for
  Camel 4.4.0, releases schedule, Spring Boot upgrade to 3.2.0 etc.
- 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 7% increase in traffic in the past quarter
  (228 emails compared to 244): Users are starting to move and ask questions
   on Zulip
- Jira Activity: The number doesn't seem to be accurate in the statistics
  page. We saw an increase in terms of opened issues. The stats are the
  following from the reporter: 324 issues opened in JIRA, past quarter (-22%
  change) 343 issues closed in JIRA, past quarter (-16% change)

Reply via email to