Nice work Andrea, thanks!

On Mon, Jun 6, 2022 at 10:49 AM Andrea Cosentino <[email protected]> wrote:

> Hello all,
>
> I prepared the draft, I'm planning to submit it this afternoon. Feedback
> welcome.
>
> ## 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:
> - No new PMC members. Last addition was Antonin Stefanutti on 2022-01-28.
> - No new committers. Last addition was Nicolas Filotto on 2022-03-01.
>
> ## Project Activity:
> - We released Camel 3.11.6
> - We released Camel 3.11.7
> - We released Camel 3.14.2
> - We released Camel 3.14.3
> - We released Camel 3.16.0
> - We released Camel 3.17.0
> - Note: Camel releases have synchronized releases of Camel-Karaf and
>   Camel-Spring-Boot too
> - We released 3.14.2 and 3.14.3: This is an LTS release train. We are going
> to
>   continue releasing 3.14.x, while we are preparing to the next LTS
>   3.18.0. We are working hard on 3.18.0 release, with a lot of new
> features.
> - We released Camel K 1.9.0
> - We released Camel K 1.9.1
> - We released Camel K 1.9.2
> - Related to Camel K we have also Camel K Runtime releases
> - We released Camel K Runtime 1.13.0
> - We are improving the Camel-K experience and we are increasing the
> Kamelets
>   number.
> - The Camel-Quarkus work is going ahead following the main camel releases
> with
>   multiple releases
> - We released Camel-quarkus 2.7.1
> - We released Camel-quarkus 2.8.0
> - We released Camel-quarkus 2.9.0
> - Camel-Kameleon and Camel-Karavan are creating a lot of interest in the
>   community and we are seeing a lot of interactions. We are improving the
>   projects by supporting new features and aligning with LTS releases.
>
> ## Community Health:
> - [email protected] 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
> - [email protected] 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 torwards 3.18.0 LTS.
> - [email protected] 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 and
> less
>   feedback.
> - 379 issues opened in JIRA, past quarter (21% decrease) and 325 issues
> closed
>   in JIRA, past quarter (27% decrease): We are in a stabilization phase for
>   Camel 3.18.0 and the LTS are more or less stable, so there is less
> activity
>   on JIRA. Note: Jira issues are related to Camel/Camel-Karaf and
>   Camel-Spring-Boot projects
> - 201 issues opened on GitHub, past quarter (-13% change) and 190 issues
>   closed on GitHub, past quarter (-19% change): We are slowing down on
> issue
>   opened on camel-kamelets for example and we are looking at backlog. Note:
>   Github issues are related to all the subprojects different from
>   Camel/Camel-Karaf/Camel-Spring-Boot
> - 3282 commits in the past quarter (29% decrease) and 121 code contributors
> in
>   the past quarter (5% increase): As said above the camel codebase is
>   stabilizing around the next LTS 3.18.0, so there are probably less
> commits.
> - 1054 PRs opened on GitHub, past quarter (18% decrease) and 1042 PRs
> closed
>   on GitHub, past quarter (19% decrease): on some of the subprojects the
>   activity is slowing down for stabilization reasons, so there are less
> PRs.
>

Reply via email to