Good point about ApacheCon. It makes sense to add this section. Regards JB
> Le 3 juin 2021 à 21:55, Zoran Regvart <zo...@regvart.com> a écrit : > > Hi Andrea, > thanks for compiling this, I think we could add a note about the two > Apache events where we'll have Camel presence, something along the > lines: > > - We'll be featured on the Integration track at ApacheCon @Home 2021 > and ApacheCon Asia 2021. We received 22 submissions and selected 14 > for a two day presence at ApacheCon @Home 2021, first day focusing on > Camel, second day focusing on other ASF projects in the software > integration ecosystem. For ApacheCon Asia 2021 we selected all 8 > submissions, also for two days on the Integration track, 6 out of 8 > featuring Camel. Schedule for ApacheCon Asia 2021 has been > published[1], the schedule for ApacheCon @Home 2021 has been submitted > and will be published soon. > > [1] https://apachecon.com/acasia2021/tracks/integration.html > > zoran > > > On Thu, Jun 3, 2021 at 7:23 AM Andrea Cosentino <anco...@gmail.com> wrote: >> >> Hello, >> >> I created a draft for next Board Report for June 2021. Feedback are >> welcome. I'm planning to send this tomorrow. >> >> ## 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 (12 years ago) >> There are currently 76 committers and 38 PMC members in this project. >> The Committer-to-PMC ratio is 2:1. >> >> Community changes, past quarter: >> - James Netherton was added to the PMC on 2021-04-12 >> - Zineb Bendhiba was added as committer on 2021-03-11 >> >> ## Project Activity: >> - We released Camel 3.7.3 on 2021-03-10. >> - We released Camel 3.9.0 on 2021-03-28. >> - We released Camel 2.25.4 on 2021-05-28. >> - We released Camel 3.7.4 on 2021-05-03. >> - We released Camel 3.10.0 on 2021-05-20. >> - The Camel 3.7.x releases are part of the second LTS for Camel 3. We are >> planning to support 3.7.x for one year. We are releasing these LTS with >> bug >> fixes >> - We are already working on 3.11.0 release: this release will be the prelude >> of the first LTS release of 2021. Originally we would like to have 3.10.0 >> as >> LTS, but it turns out more work would be needed, so we decide to go with >> 3.10.0 as development release and 3.11.0 as LTS immediately after. We're >> almost ready to release. >> - We released Camel-K 1.4.0 on 2021-04-17 >> - We are improving the Camel-K experience and we are expanding and improving >> the Kamelet concept, by introducing the camel-kamelets repository >> dedicated >> to this particular Camel aspect. >> - The Camel-Quarkus work is going ahead following the main camel releases >> with >> 2 versions this quarter >> - We released Camel-quarkus-1.8.0 on 2021-03-29. >> - We released Camel-quarkus 1.8.1 on 2021-04-06. >> - We are continuing working on the Camel-kafka-connector project and we >> released three versions of it >> - 0.7.3 on 13 Mar 2021 >> - 0.9.0 on 31 Mar 2021 >> - 0.10.0 on 23 May 2021 >> - The 0.7.x releases are based on the second LTS of main Camel, 3.7.x >> - We are working for supporting the next Camel LTS with >> camel-kafka-connector >> too >> >> ## Community Health: >> - dev@camel.apache.org had a 19% decrease in traffic in the past quarter >> (375 >> emails compared to 459): This decrease is related to the stabilization of >> the code base preparing for the next LTS 3.11.0. >> - iss...@camel.apache.org had a 22% increase in traffic in the past quarter >> (2521 emails compared to 2052): This increase is related to the fact we >> are >> getting more feedback on the development releases torward the next LTS >> release. We are creating new issues for the third LTS release, but we are >> also starting to see issues for 3.7.x. >> - us...@camel.apache.org had a 13% increase in traffic in the past quarter >> (356 emails compared to 315): the increase is related to people switching >> from Camel 2 to Camel 3, since we are already at the second LTS, so we >> are >> looking at discussions about this and also issues with Camel 3. This is >> also related to people moving from second LTS to a development release >> for >> the next LTS. >> - 369 issues opened in JIRA, past quarter (-4% decrease) and 356 issues >> closed >> in JIRA, past quarter (-1% decrease): as reported above, the situation is >> stable. We are facing issues and improvements for 3.11 and old development >> releases for the next LTS, but also starting to see new issues for Camel 3 >> and the 3.7.x LTS releases. The activity related to Camel 2 is near to >> zero, >> even though we are still see people asking for issues and how to migrate. >> - 4774 commits in the past quarter (4% decrease) and 120 code contributors >> in >> the past quarter (1% increase): the core Camel team is stabilizing the >> codebase so there is a little decrease in number of commits, contributions >> related to documentation and website is increasing. In this quarter we >> were >> much more stable in this area. >> - 979 PRs opened on GitHub, past quarter (-24% decrease) and 972 PRs closed >> on >> GitHub, past quarter (-24% decrease): the code stabilization and also a >> little less work on the camel kafka connector side explain the decrease in >> number of PRs open and closed. We expect this stat to increase again once >> we >> release the next LTS. >> - 365 issues opened on GitHub, past quarter (9% increase) and 286 issues >> closed on GitHub, past quarter (5% increase): There is a new addition in >> terms of repositories which is the camel-kamelets repository, where we >> opened and closed a lot of new GH issues > > > > -- > Zoran Regvart
