This was extracted (@ 2017-09-21 15:10) from a list of minutes
which have been approved by the Board. Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.

Status report for the Apache Camel project - August 2017
## Description:
- Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- The spam mails we are receiving on Nabble and also on the moderate mail
accounts are painful.
- The Camel team created a Gitter chat at
https://gitter.im/apache/apache-camel to provide more possibilities to our our
community to get in touch with us. https://s.apache.org/9kwJ
- We are receiving many contributions from our contributors (via GitHub pull
requests). We have more than 1500 closed pull requests where 98% is from
community contributors.
- We are focusing the development of the next minor release Apache Camel
2.20.0 expected to be released in Q4 2017.
- Some people started to work on some bigger changes for the next major
release Apache Camel 3.0.0.
- We have started to deprecate APIs and components that will be dropped for
Camel 3.0
- We run a new logo proposal and our community has vote:
https://s.apache.org/qWPW
Now, the PMC decides how to carry on with the logo change.
## Health report:
- The project is super healthy, active and stays at a high level
- At ApacheCon Europe 2016, we had 5 presentations about Apache Camel from
PMC's, committers and contributers/users.
## PMC changes:
- Currently 30 PMC members.
- Zoran Regvart was added to the PMC on Sun Jul 02 2017
## Committer base changes:
- Currently 58 committers.
- Tomohisa Igarashi was added as a committer on Wed Jun 07 2017
- Onder Sezgin was added as a committer on Thu Jun 08 2017
- Quinn Stevenson was added as a committer on Wed Jun 07 2017
## Releases:
- 2.17.5 was released on Jan 22 2017
- 2.17.6 was released on March 8 2017
- 2.17.7 was released on May 18 2017
- 2.18.2 was released on Jan 30 2017
- 2.18.3 was released on Mar 12 2017
- 2.18.4 was released on May 25 2017
- 2.19.1 was released on Jun 15 2017
- 2.19.2 was released on Aug 1 2017
## Mailing list activity:
- Mailing list activity stays at a high level.

## Description:
- Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- We are receiving many contributions from our contributors (via GitHub pull
requests). We have more than 1500 closed pull requests where 98% is from
community contributors.
- A new releases is coming out soon: Camel 2.18.3
- We are focusing the development of the next minor release Apache Camel
2.19.0 expected to be released in April.
- Some people started to work on some bigger changes for the next major
release Apache Camel 3.0.0.
- We have started to deprecate APIs and components that will be dropped for
Camel 3.0
- We are running a new logo proposal that has a deadline at the end of March.
We have receive about 6 different logo proposals. After the deadline we will
have a vote about the logo which the PMC then ultimate decides whether to carry
on with the logo change
## Health report:
- The project is super healthy, active and stays at a high level
- At ApacheCon Europe 2016, we had 5 presentations about Apache Camel from
PMC's, committers and contributers/users.
## PMC changes:
- Currently 30 PMC members.
- Zoran Regvart was added to the PMC on Sun Jul 02 2017
## Committer base changes:
- Currently 58 committers.
- Tomohisa Igarashi was added as a committer on Wed Jun 07 2017
- Onder Sezgin was added as a committer on Thu Jun 08 2017
- Quinn Stevenson was added as a committer on Wed Jun 07 2017
## Releases:
- 2.17.5 was released on Jan 22 2017
- 2.17.6 was released on March 8 2017
- 2.18.2 was released on Jan 30 2017
- 2.19.1 was released on Jun 15 2017
## Mailing list activity:
- Mailing list activity stays at a high level.

## Description:
- Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- We are receiving many contributions from our contributors (via GitHub pull
requests). We have more than 1500 closed pull requests where 98% is from
community contributors.
- A new releases is coming out soon: Camel 2.18.3
- We are focusing the development of the next minor release Apache Camel
2.19.0 expected to be released in April.
- Some people started to work on some bigger changes for the next major
release Apache Camel 3.0.0.
- We have started to deprecate APIs and components that will be dropped for
Camel 3.0
- We are running a new logo proposal that has a deadline at the end of March.
We have receive about 6 different logo proposals. After the deadline we will
have a vote about the logo which the PMC then ultimate decides whether to
carry on with the logo change
## Health report:
- The project is super healthy, active and stays at a high level
- At ApacheCon Europe 2016, we had 5 presentations about Apache Camel from
PMC's, committers and contributers/users.
## PMC changes:
- Currently 29 PMC members.
- Luca Burgazzoli was added to the PMC on Thu Oct 06 2016
## Committer base changes:
- Currently 54 committers.
- Last committer addition was Zoran Regvart at Feb 18 2017
## Releases:
- 2.17.5 was released on Jan 22 2017
- 2.17.6 was released on March 8 2017
- 2.18.2 was released on Jan 30 2017
## Mailing list activity:
- Mailing list activity stays at a high level.

## Description:
- Apache Camel is a powerful open source integration framework based on
known Enterprise Integration Patterns.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- We are receiving many contributions from our contributors (via GitHub pull
requests).
- We are focusing the development of the next minor release Apache Camel
2.19.0.
- Some people started to work on some bigger changes for the next major
release Apache Camel 3.0.0.
- With the community, we are looking for a new logo for our project.
## Health report:
- The project is super healthy, active and stays at a high level
- At ApacheCon Europe 2016, we had 5 presentations about Apache Camel from
PMC's, committers and contributers/users.
## PMC changes:
- Currently 29 PMC members.
- Luca Burgazzoli was added to the PMC on Thu Oct 06 2016
## Committer base changes:
- Currently 54 committers.
- No new committers added in the last 3 months
- Last committer addition was Nicola Ferraro at Mon Aug 22 2016
## Releases:
- 2.16.4 was released on Sun Sep 25 2016
- 2.17.4 was released on Wed Nov 30 2016
- 2.18.0 was released on Sun Oct 09 2016
- 2.18.1 was released on Fri Dec 02 2016
## Mailing list activity:
- Mailing list activity stays at a high level.

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
There are no issues requiring board attention at this time.
Community
---------
The project is healthy, active and stays at a high level. We got 3 new
contributors who signed the ICLA in this reporting periode.
Currently 28 PMC members. Last PMC addition:
Gregor Zurowski was added as a PMC on Fri Dec 04 2015
Currently 54 committers. Last committer addition:
Arno Noordover was added as a committer on Thu Jun 16 2016
Nicola Ferraro was added as a committer on Mon Aug 22 2016
Nicola Ferraro was added as a committer on Mon Aug 22 2016
Mailing list activity stays on a high level:
users@camel.apache.org:
913 subscribers (up 13 in the last 3 months)
1168 emails sent to list (1626 in previous quarter)
dev@camel.apache.org:
349 subscribers (up 4 in the last 3 months)
678 emails sent to list (798 in previous quarter)
issues@camel.apache.org:
83 subscribers (up 1 in the last 3 months)
2012 emails sent to list (2413 in previous quarter)
256 JIRA tickets created and 237 JIRA tickets closed/resolved in the last 3
months
Community Objectives
--------------------
We are receiving many contributions from our contributors (via GitHub pull
requests).
We are focusing the development of the next minor release Apache Camel
2.18.0.
Some people started to work on some bigger changes for the next major release
Apache Camel 3.0.0.
Releases
--------
2.17.2 was released on Fri Jul 01 2016

## Description:
- Apache Camel is a powerful open source integration framework based on
known Enterprise Integration Patterns.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- We resolved a trademark issue on GitHub with a project called Camel.Net.
- We are focusing the development of the next minor release Apache Camel
2.18.0.
## Health report:
- The project is healthy, active and stays at a high level.
- We got 10 new contributors who signed the ICLA in this reporting periode.
## PMC changes:
- Currently 28 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Gregor Zurowski on Fri Dec 04 2015
## Committer base changes:
- Currently 52 committers.
- New commmitters:
- Luca Burgazzoli was added as a committer on Thu Apr 07 2016
- Stephan Siano was added as a committer on Tue Apr 26 2016
## Releases:
- 2.15.6 was released on Thu Mar 31 2016
- 2.16.3 was released on Sat Apr 09 2016
- 2.17.0 was released on Sat Mar 26 2016
- 2.17.1 was released on Sun May 08 2016
## Mailing list activity:
- users@camel.apache.org:
- 903 subscribers (up 14 in the last 3 months):
- 1704 emails sent in the past 3 months (1349 in the previous cycle)
- dev@camel.apache.org:
- 346 subscribers (up 9 in the last 3 months):
- 842 emails sent in the past 3 months (634 in the previous cycle)
- commits@camel.apache.org:
- Currently: 63 subscribers (up 4 in the last 3 months):
- 2574 emails sent in the past 3 months (1938 in the previous cycle)
- issues@camel.apache.org:
- 82 subscribers (up 7 in the last 3 months):
- 2526 emails sent in the past 3 months (2088 in the previous cycle)
- notifications@camel.apache.org:
- 8 subscribers (up 1 in the last 3 months)
## JIRA activity:
- 346 JIRA tickets created in the last 3 months
- 411 JIRA tickets closed/resolved in the last 3 months

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* Some of the current PMC expressed their wish to keep up with the current
chair. Because there was no further discussion started who could be a good
successor for the current chair, the current chair agreed to continue in
his role.
* We discovered a trademark issue, a GitHub project called camel.js
(https://github.com/matthewcodes/camel.js). The project is now renamed to
oneHumpOrTwo.js (https://github.com/matthewcodes/oneHumpOrTwo.js).
Some of the content still needs to be updated.
* We didn't got a new contributor who signed the ICLA in this reporting
periode.
* The community stays at a high level (328 subscribers at dev@; 883
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 440 mails per month on the users mailing list in September 2015 -
November 2015
* Avg. 199 mails per month on the dev mailing list in September 2015 -
November 2015
* Avg. 298 committs per month in September 2015 - November 2015
Community Objectives
--------------------
* The camel-extra project moved to GitHub [1].
* We are focusing the development of the next minor release Apache Camel
2.17.0.
* The Camel PMC voted to allow Camel committers to update the Camel
dist/release SVN repo which is necessary to publish a new release.
Project Composition
-------------------
* Sergey Beryozkin was added as new committer in this reporting period
* Aki Yoshida, Andrea Cosentino, Jean-Baptiste Onofré and Gregor Zurowski
were added as new PMC member in this reporting period
Releases
--------
* 2.15.5 (Nov 30 2015)
* 2.16.1 (Nov 22 2015)
* 2.14.4 (Nov 11 2015)
* 2.15.4 (Oct 28 2015)
* 2.16.0 (Oct 08 2015)
[1] https://github.com/camel-extra/camel-extra

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* The current PMC chair would like to resign and we are discussing who could
take over this role.
* On 15th July one of our PMC discovered a trademark issue, a GitHub project
called camel-labs. Unfortunately, some of the Camel PMC's was involved in this
project. On 31nd July the project was renamed and the issues was solved.
* We got 1 new contributors who signed the ICLA.
* The community stays at a high level (328 subscribers at dev@; 873
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 355 mails per month on the users mailing list in June 2015 -
August 2015
* Avg. 116 mails per month on the dev mailing list in June 2015 -
August 2015
* Avg. 282 commits per month in June 2015 - August 2015
Community Objectives
--------------------
* The camel-extra project [1] is now read-only. The people didn't received any
information how to proceed to move to SF. This wasn't a good experience, also
because all of the camel-extra committers want to move to GitHub.
* We are focusing the development of the next minor release Apache Camel
2.16.0.
Project Composition
-------------------
* no new committer was added in this reporting period
* the last committer was added at 19/05/2015
* no new PMC member was added in this reporting period
* the last PMC member was added at 04/24/2014
Releases
--------
* 2.15.3 (20/08/2015)
[1] https://code.google.com/a/apache-extras.org/p/camel-extra/

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* We got 7 new contributors who signed the ICLA.
* The community stays at a high level (323 subscribers at dev@; 857
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 578 mails per month on the users mailing list in March 2015 -
May 2015
* Avg. 238 mails per month on the dev mailing list in March 2015 -
May 2015
* Avg. 534 committs per month in March 2015 - May 2015
Community Objectives
--------------------
* We are discussing the camel-extra move to GitHub, as Google-Code will shut
down the service is a few month. We are missing the recommendation from
com-dev where the apache-extra projects should move to [1]. Without a
recommendation, we will move the camel-extra project to GitHub, because
it's the preferred place for these committers.
* We are focusing the development of the next minor release Apache Camel
2.16.0.
* We handled the security issues CVE-2015-0263 and CVE-2015-0264. Thanks to
Stephan Siano for reporting it to us.
Project Composition
-------------------
* Andrea Cosentino (22/04/2015) and Franz Forsthofer (19/05/2015) were added
* the last committer was added at 11/06/2014
* no new PMC member was added in this reporting period
* the last PMC member was added at 04/24/2014
Releases
--------
* 2.14.3 (01/06/2015)
* 2.15.2 (04/05/2015)
* 2.15.1 (01/04/2015)
[1] http://s.apache.org/Cej

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* We got 4 new contributors who signed the ICLA.
* The community stays at a high level (323 subscribers at dev@; 825
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 432 mails per month on the users mailing list in December 2014 -
February 2015
* Avg. 145 mails per month on the dev mailing list in December 2014 -
February 2015
* Avg. 426 committs per month in December 2014 - February 2015
Community Objectives
--------------------
* We finalized the Apache Camel 2.15.0 release
* We are started the development of the next minor release Apache Camel 2.16.0.
Project Composition
-------------------
* no new committer was added in this reporting period
* the last committer was added at 11/06/2014
* no new PMC member was added in this reporting period
* the last PMC member was added at 04/24/2014
Releases
--------
* 2.13.4 (03/10/2015)
* 2.14.1 (12/16/2014)
* 2.14.2 (03/10/2015)
* 2.15.0 (03/10/2015)

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* We got 5 new contributors who signed the ICLA.
* The community stays at a high level (321 subscribers at dev@; 800
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 552 mails per month on the users mailing list in September 2014 -
November 2014
* Avg. 183 mails per month on the dev mailing list in September 2014 -
November 2014
* Avg. 647 commits per month in September 2014 - November 2014
Community Objectives
--------------------
* We are planning to release Apache Camel 2.14.1 in the next weeks.
* Adding new features and improvements to Apache Camel in version 2.15.0.
Project Composition
-------------------
* One new committer was added in this reporting period
* Colm O hEigeartaigh 11/06/2014
* no new PMC member was added in this reporting period
* the last PMC member was added at 04/24/2014
Releases
--------
* 2.12.5 (10/27/2014)
* 2.13.3 (10/31/2014)

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* We got 3 new contributors who signed the ICLA.
* We have two talks scheduled at the next ApacheCon EU:
* Using Websocket With CXF And Camel - Akitoshi Yoshida
* Apache Camel In The Belly Of The Docker Whale - Henryk Konsek
* The community stays at a high level (307 subscribers at dev@; 772
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 618 mails per month on the users mailing list in June 2014 -
August 2014
* Avg. 182 mails per month on the dev mailing list in June 2014 -
August 2014
* Avg. 347 committs per month in June 2014 - August 2014
Community Objectives
--------------------
* We finalized the Spring 4 and Java 8 support.
* We are planning to release Apache Camel 2.14.0 next week.
* Adding new features and improvements to Apache Camel in version 2.15.0.
Project Composition
-------------------
* no new committer was added in this reporting period
* the last committer was added at 06/11/2014
* no new PMC member was added in this reporting period
* the last PMC member was added at 04/24/2014
Releases
--------
* 2.12.4 (07/06/2014)
* 2.13.2 (07/06/2014)

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* We got 5 new contributors who signed the ICLA.
* The community stays at a high level (297 subscribers at dev@; 760
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 607 mails per month on the users mailing list in March 2014 -
May 2014
* Avg. 123 mails per month on the dev mailing list in March 2014 -
May 2014
* Avg. 290 committs per month in March 2014 - May 2014
Community Objectives
--------------------
* We are finalizing Apache Camel 2.14.0 to get it out of the door during the
next reporting period.
Project Composition
-------------------
* Dhiraj Bokde was added as committer (04/23/2014)
* Bilgin Ibryam was added as new PMC member (04/24/2014)
* Grzegorz Grzybek was added as committer (06/11/2014)
* Gregor Zurowski was added as committer (06/11/2014)
Releases
--------
* 2.13.0 (03/18/2014)
* 2.13.1 (05/13/2014)

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* Packtpub published one new book about Apache Camel:
http://www.packtpub.com/apache-camel-developers-cookbook/book
* The previous CamelOne conference is now part of RedHat's DevNation
conference which is planned for 04/13/2014 - 04/17/2014
(http://www.devnation.org/#agenda)
* We will have two talks at ApacheCon 2014 in Denver:
* http://s.apache.org/8un
* http://s.apache.org/TPG
* We got 3 new contributors who signed the ICLA.
* The community stays at a high level (289 subscribers at dev@; 732
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 692 mails per month on the users mailing list in December 2013 -
February 2014
* Avg. 142 mails per month on the dev mailing list in December 2013 -
February 2014
* Avg. 275 commits per month in December 2013 - February 2014
Community Objectives
--------------------
* We handled the security issues CVE-2014-0002 and CVE-2014-0003. Thanks to
David Jorm for reporting it to us.
* We are finalizing Apache Camel 2.13.0 to get it out of the door soon.
* We are discussing new features for the next minor release Apache Camel
2.14.0.
Project Composition
-------------------
* No new committer in this reporting period (last one joined 10/16/2013)
* No new PMC member in this reporting period (last one joined 10/05/2013)
Releases
--------
* 2.12.3 (02/21/14)
* 2.11.4 (02/16/14)
* 2.11.3 (01/13/14)

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* The project is active and stays at a high level.
* There was a bit of community contention this period when a committer added
a target to Camel's maven plugins to run a third party (but open source)
console with all branding, marketing links, etc... intact and not allowing
the Camel community any control over the display of the Camel portion. The
PMC (in particular 4 PMC members had to issue specific vetos) did decide to
revert this change, but discussion did degrade into various personal attacks,
attacks against employers, etc... This seems to happen very often when there
is a disagreement in Camel and has caused many people to not feel they can
speak up and disagree or state their opinions.
Community
---------
* Packtpub published two new book about Apache Camel, one was written by one
of our committers:
http://www.packtpub.com/apache-camel-message-routing/book
http://www.packtpub.com/apache-camel-messaging-system/book
* JAX-Magazine published two article about Apache Camel which was written by
one of our PMC member:
http://jaxenter.com/jax-magazine/JAX-Magazine-2013-05
http://jaxenter.com/tutorial-integrating-with-apache-camel-48211.html
* The community stays at a high level (276 subscribers at dev@; 711
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 948 mails per month on the users mailing list in September 2013 -
November 2013
* Avg. 177 mails per month on the dev mailing list in September 2013 -
November 2013
* Avg. 453 committs per month in September 2013 - November 2013
Community Objectives
--------------------
* We handled the security issue CVE-2013-4330. Thanks to security@ for their
support.
* Working on the Camel 2.13.0 release.
Project Composition
-------------------
* Christian Posta was added as committer (10/16/2013)
* James Carman was added as committer (10/05/2013)
* James Carman was added as new PMC member (10/05/2013)
Releases
--------
* 2.12.2 (11/27/2013)
* 2.12.1 (09/22/2013)
* 2.11.2 (09/24/2013)
* 2.10.7 (09/19/2013)
* 2.9.8 (09/20/2013)

There is a similar issue with ActiveMQ where a console was
introduced with branding intact that made it appear that the
console vendor "owned" the project. Shane notes that in
general, pmcs must clearly separate apache project from
downstream commercial products. It's fine if people add
plugins when they use our stuff, or even if they re-ship their
own product based on our stuff. But when the average user gets
an Apache product, it should look like an Apache product, and
not a third party. AI: Chris: will join discussion on
camel-dev list

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* We delivered our first releases coming from our new GIT repository.
* Red Hat was organizing the CamelOne 2013 conference. The slides are
available at
http://camelone.com/apache-camel-conference-2013/camelone_agenda_2013/.
* The community stays at a high level (183 subscribers at dev@; 503
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 811 mails per month on the users mailing list in June 2013 - August
2013
* Avg. 154 mails per month on the dev mailing list in June 2013 - August
2013
* Avg. 339 commits per month in June 2013 - August 2013
Community Objectives
--------------------
* Starting to work on Camel 2.13.0
* The interest on the new major version Camel 3.0.0 has decreased
Project Composition
-------------------
* Aki Yoshida was added as a new committer (07/08/2013)
* Rich Newcomb was added as committer (07/08/2013)
* Raul Kripalani was added as new PMC member (07/07/2013)
Releases
--------
* 2.12.0 (09/09/2013)
* 2.11.1 (07/14/2013)
* 2.9.7 (07/03/2013)
* 2.9.6 (06/23/2013)

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* We switched from SVN to GIT which was a bit bumpy because of the
missing announcement from INFRA when the SVN repo was going read-only.
But we are fine now and preparing our first release which comes from
our new GIT repo. Thank's INFRA!
* Red Hat is organizing the CamelOne 2013 conference in Boston on June 10th
- 11th (http://camelone.com/). ConCom and the Camel PMC's were involved in
the planning of this event.
* The community stays at a high level (183 subscribers at dev@; 503
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 958 mails per month on the users mailing list in March 2013 - May
2013
* Avg. 205 mails per month on the dev mailing list in March 2013 - May 2013
* Avg. 348 committs per month in March 2013 - May 2013
* No new committers in this reporting period (last one joined in Dec 2012)
* No new PMC members in this reporting period (last one joined in Dec 2012)
Community Objectives
--------------------
* Working on Camel 2.12.0 which is our last planned 2.x release
* Finalizing our "pre" Camel 3.0 work
* Discussing and finalizing the Camel 3.0.0 road map
Releases
--------
* 2.11.0 (04/17/2013)
* 2.9.7 (04/24/2013)

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* At ApacheCon NA 2013 we had 4 talks about Apache Camel.
* Red Hat planned (and will announce in short time) the CamelOne 2013
conference in Boston on June 10th - 11th (http://camelone.com/).
Rob Davies (Camel PMC member and Red Hat employee), ConCom and the
Apache Camel PMC are working together to ensure that this event
will meet the ASF trademark and ConCom guidelines.
Please find the relevant mail thread at http://s.apache.org/Hq1
* The community stays at a high level (183 subscribers at dev@; 503
subscribers at users@)
* The community is active and questions being answered in short term.
* Avg. 805 mails per month on the users mailing list in Dec 2012 - Feb 2013
* Avg. 244 mails per month on the dev mailing list in Dec 2012 - Feb 2013
* Avg. 299 committs per month in Dec 2012 - Feb 2013
* No new committers in this reporting period (last one joined in Dec 2012)
* No new PMC members in this reporting period (last one joined in Dec 2012)
Community Objectives
--------------------
* Finalizing our working on Camel 2.11.0
* Discussing Camel 3.0.0
Releases
--------
* 2.10.4 (02/22/2013)
* 2.9.6 (03/07/2013)

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* "Java aktuell - Das Magazin" and "Java Spektrum" published articles about
Apache Camel.
* At ApacheCon EU 2012 we had 4 talks about Apache Camel.
* The community stays at a high level (183 subscribers at dev@; 503 subscribers
at users@)
* The community is active and questions being answered in short term.
* Avg. 795 mails per month on the users mailing list in Sep 2011 - Nov 2012
* Avg. 247 mails per month on the dev mailing list in Sep 2011 - Nov 2012
* Avg. 402 commits per month in Sep 2011 - Nov 2012
* We welcome Henryk Konsek, Raul Kripalani and Scott England-Sullivan as new
committer.
* We welcome Babak Vahdat and Charles Moulliard in our PMC.
* After acquiring FuseSource by RedHat and inviting two committers, our PMC of
21 is affiliated with 7 different unique organizations (13 of them are
affiliated with a single company).
* Our additional 17 committers belongs to 14 different unique organizations
(4 of them are affiliated with the same single company mentioned above).
Community Objectives
--------------------
* Finalizing our working on Camel 2.11.0
* Plan the work for Camel 3.0.0
Releases
--------
* 2.9.4
* 2.9.5
* 2.10.2
* 2.10.3

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* Apache Camel in the news:
* "Java aktuell - Das Magazin", "Java Magazin", "Heise Developer" and
"h-online" published articles about Apache Camel
* We celebrated our fifth birthday: http://s.apache.org/PZ7
* We will have 4 talks at ApacheCon EU 2012 and also a talk at JavaOne 2012
* The community stays at a high level
* The community is active and questions being answered in short term.
* Avg. 781 mails per month on the users mailing list in Jun 2011 - Aug 2012
* Avg. 239 mails per month on the dev mailing list in Jun 2011 - Aug 2012
* Avg. 275 commits per month in Jun 2011 - Aug 2012
* No new committer in this reporting period (last one joined in March 2012)
* We are watching a few good candidates which we probably add in the next
reporting period
* No new PMC members in this reporting period (last one joined in November
2011)
Community Objectives
--------------------
* Working on Camel 2.11.0
* Concrete the Camel 3.0.0 road map
Releases
--------
* 2.10.1
* 2.10.0
* 2.9.3
* 2.8.6

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy, active and stays at a high level.
Community
---------
* CamelOne 2012 was held from 5/15/2012 - 5/16/2012 in Boston, MA
(http://CamelOne.com)
* It was a great success and a really cool and fun conference.
* The attendance was a lot higher this year (~ +60%) which shows the
popularity of the Camel project.
* Apache Camel in the news:
* http://www.javacodegeeks.com/2012/03/integration-framework-comparison-spring.html?m=1
* The community stays at a high level:
* 503 subscribers to the users mailing list (+0 %)
* 183 subscribers to the dev mailing list (+0 %)
* The community is active
* Avg. 863 mails per month on the users mailing list in
Mar 2011 - Mai 2012 (+25 %)
* Avg. 167 mails per month on the dev mailing list in
Mar 2011 - Mai 2012 (-15 %)
* Avg. 308 commits per month in Mar 2011 - Mai 2012 (-17 %)
* No new committer in this reporting period (last one joined in March 2012)
* No new PMC members in this reporting period (last one joined in November
2011)
Community Objectives
--------------------
* Closing down the Camel 2.10.0 release which will resolve more than 400
issues
* 15 new components, support for Java 7, support for Spring 3.1, ...
* Start working on Camel 2.11.0
* Concrete the Camel 3.0.0 road map
Releases
--------
* 2.8.5
* 2.9.2

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy and continues to grow.
* Progress has been made toward using the CXF developed export utility to
migrate the website from rsync to svnpubsub as per guidelines from the
Infrastructure team.
Community
---------
* The community grows:
* 503 subscribers to the users mailing list (+3 %)
* 183 subscribers to the dev mailing list (+2 %)
* The community is active
* Avg. 688 mails per month on the users mailing list in Dec 2011 - Feb 2012
* Avg. 196 mails per month on the dev mailing list in Dec 2011 - Feb 2012
* Avg. 507 commits per month in Dec 2011 - Feb 2012
* Babak Vahdat (bvahdat) joined the community as a new committer.
* Bilgin Ibryam (bibryam) joined the community as a new committer.
* No new PMC members since the last board report (December 2011)
* We are on track to increasing diversity.
* Our PMC of 19 is affiliated with 6 different unique organizations (11 of
them are affiliated with a single company).
* Our additional 16 committers belongs to 14 different unique organizations
(3 of them are affiliated with the same single company mentioned above).
* Fusesource planned and announced a CamelOne conference at May 15th - 16th
(http://fusesource.com/apache-camel-conference-2012/). ConCom approved to use
the name CamelOne for this event. The Camel PMC, especially Jeff Genender,
Rob Davies, Claus Ibsen and myself will make sure this event will meet the
ASF trademark and ConCom guidelines.
Community Objectives
--------------------
* Our first objective is to continue with the development for Camel 2.10.0.
* Beside this, we continues development with new features and fixes for the
camel-2.8.x and 2.9.x maintenance branches.
* In the next weeks we have to concrete our schedule for Camel 3.0.0 which
will be a bigger release.
Branding Status
---------------
* Project Naming And Descriptions : Compliant
* Website Navigation Links : Compliant
* Trademark Attributions : Compliant
* Logos and Graphics : Compliant
* Project Metadata : Compliant
Releases
--------
* 2.7.5 (the 2.7.x series continues to be maintained under a "security and
important fixes only" profile)
* 2.8.4
* 2.9.0
* 2.9.1

Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* The project is healthy and continues to grow.
* There are no issues that require the board attention.
* We are still working on increasing diversity.
Community
---------
* The community grows:
* 489 subscribers to the users mailing list
* 179 subscribers to the dev mailing list
* The community is active (909 mails on the users mailing list in
November 2011 - 577 in the last board report for October 2011)
* Apache Camel has been presented at ApacheCon in Vancouver by Hadrian
Zbarcea and Daniel Kulp.
* Set up back port guidelines for our maintenance branches.
* We added a new mailing list issues@ to which all our JIRA notifications
are forwarded to have less noise on dev@.
* No new committers since the last board report (November 2011)
* No new PMC members since the last board report (November 2011)
Community Objectives
--------------------
* Our current objective is to release Camel 2.9.0 soon. We did a few
preparations for bigger refactorings which we plan for Camel 3.0.0, added
new components, fixed issues and added new features and improvements.
* Our second objective is to start with the development for Camel 2.10.0 in
the next days.
* Besides all this we continues development with new features and fixes for
the camel-2.7.x and 2.8.x maintenance branches.
Branding Status
---------------
* Project Naming And Descriptions : Compliant
* Website Navigation Links : Compliant
* Trademark Attributions : Compliant
* Logos and Graphics : Compliant
* Project Metadata : Compliant
Releases
--------
* 2.8.3

Change the Apache Camel Project Chair

WHEREAS, the Board of Directors heretofore appointed Hadrian
Zbarcea to the office of Vice President, Apache Camel, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Hadrian Zbarcea from the office of Vice President, Apache
Camel, and
WHEREAS, the Project Management Committee of the Apache Camel
project has chosen by vote to recommend Christian Mueller as
the Successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Hadrian Zbarcea is
relieved and discharged from the duties and responsibilities of
the office of Vice President, Apache Camel, and
BE IT FURTHER RESOLVED, that Christian Mueller be and hereby
is appointed to the office of Vice President, Apache Camel, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification, or
until a successor is appointed.
Special Order 7A, Resolution to Change the Apache Camel
Project Chair, was approved by Unanimous Vote of the directors
present.

Apache Camel is a powerful open source integration framework
based on known Enterprise Integration Patterns.
Community:
* There are a few issues that require the board attention
and the PMC will continue to work to fix them.
* The project is healthy and continues to grow
* One committer added to the project: Ioannis Canellos (iocanel)
* One member added to the PMC: Dan Kulp (dkulp)
* A resolution to change the PMC Chair was submitted for
the board consideration this month.
Development:
* Development continues with new features and fixes on trunk
and the camel-2.7.x and 2.8.x maintenance branches
* The number of issues fixed on trunk is rather large and we
decided to issue a RC to allow for better testing in the
community before the final 2.9.0
Releases:
* 2.9.0-RC1

Jim reports that discussions have settled down and he is
comfortable with how things are going. Shane plans to follow
up. Dan reports that additional ASF members have been added to
the PMC. With the change of chair, we will continue with (at
least) one more month of monthly reporting.

Apache Camel is a powerful open source integration framework
based on known Enterprise Integration Patterns.
Community:
* There are a few issues that require the board intervention
* The project is healthy and continues to grow
* Three more PMC members moved to emeritus status: nsandhu,
ammulder and jlaskowski
* One member added to the PMC: jgenender
Development:
* Development continues with new features and fixes on trunk
and the camel-2.7.x and 2.8.x maintenance branches
Releases:
* 2.7.4
* 2.8.2

This report is approved, and the board would like a report from
the new chair in November.

Apache Camel is a powerful open source integration framework
based on known Enterprise Integration Patterns.
Community:
* There are a few issues that require the board intervention.
* The project is healthy and continues to grow
* Three PMC members moved to emeritus status: djencks,
bsnyder and romkal
Development:
* Development continues with new features and fixes on trunk
and the camel-2.7.x and 2.8.x maintenance branches
* Brian Fox reported LGPL dependencies shipped with exactly
2 camel components (camel-web and camel-web-standalone)
in version 2.4.0 released more than a year ago on
06/12/2010. I can confirm his findings, not sure what the
right solution is though, will discuss this in the PMC.
Releases:
* 2.8.1

The Camel PMC might need help resolving their trademark issue.
AI Jim: help PMC with the trademark issue.
AI Hadrian: report again next month.

Apache Camel is a powerful open source integration framework
based on known Enterprise Integration Patterns.
Community:
* There are a few issues that require the board intervention.
* The project grows at the same intense pace.
* Freeman Fang (fang) joined the community as a new committer.
* We added an "Estimated Complexity" custom field to jira
to encourage the community contributions.
Development:
* Development continues with new features and fixes on trunk
and the camel-2.7.x and 2.8.x maintenance branches
Releases:
* None

Since the issues were not resolved during the slow vacation season,
a report will be requested for next month.

Apache Camel is a powerful open source integration framework
based on known Enterprise Integration Patterns.
Community:
* There are a few issues that require the board intervention.
* The community continues to grow
* Mailing lists continue to be very active.
* diversity in the project is increasing
* 3 new committers joined the project: dkulp, jbonofre, dvaleri
Development:
* Development continues with new features and fixes on trunk
and the camel-2.7.x maintenance branch
* We intend to continue the practice of issuing patch releases
more frequently
Releases:
* Camel 2.7.3 (under vote)
* Camel 2.8.0 (under vote)
Issues:
* The community needs more diversity.

Camel to produce an additional report next month.

AI: Jim to describe our expectations of a chair, and how to balance
with commercial interests, and the need to avoid personal attacks on
mailing lists.

Guillaume noted that the Branding policy "requests" rather than
"requires" attribution. If necessary, Guillaume and Shane to follow up
on trademark mailing list.

Apache Camel is a powerful open source integration framework
based on known Enterprise Integration Patterns.
Community:
* No issues that require the board attention.
* The community continues to grow at the fast paced rhythm
we're used too
* We increased the frequency of releases and issue more
patch releases
* We had a security vulnerability (XSS) reported against Camel
which we resolved.
* Mailing lists continue to be very active.
* Fusesource hosted a CamelOne conference in May
* diversity in the project is increasing
* 2 more companies announced support offerings around Camel.
* 1 new committer joined the project: boday
* 1 committer joined the PMC: joed
* The PMC is in the process of assessing the trademarks
compliance and we'll have detailed answers in the next
report.
Development:
* Development continues with new features and fixes on trunk
* A Camel 2.8.0 release is planned for this month.
Releases:
* Camel 2.7.0
* Camel 2.7.1
* Camel 2.7.2

Apache Camel is a powerful open source integration framework
based on known Enterprise Integration Patterns.
Community:
* No issues that require the board attention.
* The community continues to grow and submit contributions.
* Mailing lists continue to be very active.
* 2 new committers joined the project: rickette, tjsnell
* Fusesource planned and announced a CamelOne conference in May
The Camel PMC contacted Fusesource and Rob Davies, Camel PMC
member and Fusesource manager, ensured us that the CamelOne
event sponsored by FuseSource will meet the ASF trademark
guidelines as defined by the current draft posted online.
Development:
* Development continues with new features and fixes on trunk
* A Camel 2.7.0 release is planned for this month.
Releases:
* Camel 2.6.0 released.

Apache Camel is a powerful open source integration framework
based on known Enterprise Integration Patterns.
Community:
* No issues that require the board attention.
* The project community is growing and becoming more diverse.
* Community contributions increasing at a steady pace.
* Mailing lists continue to be very active.
* 5 committers joined the PMC: krasserm, slewis, akarpe, cschneider, cmueller
* 1 new committer joined the project: joed
Development:
* Development continues with new features and fixes on trunk
* Planning started for a new Camel 3.0
* The PMC ran a survey during the month of Oct on how camel is used
* The last maintenance release of camel 1.x under voting,
there will be no new development for camel 1.x
* A Camel 2.6.0 release is planned for this month as well.
Releases:
* Camel 2.5.0 released.
* Camel 1.6.4 is being released (under vote)

Community:
* No issues that require the board attention.
* The project community continue to grow at the same fast pace.
* No new committers or changes in the PMC
Development:
* Development continues with new features and fixes on trunk
* The community started a discussion about moving to a new major release Camel 3.0
* On the 1.x branch we discussed and agree to have one final release in Q4
and then discontinue development of that branch.
* We corrected the few issues we had with xml files missing the AL2 license.
There are only a few text test files that miss the license now, which I am
working on fixing.
* We are planning a new camel 2.5.0 release this week.
Releases:
* Camel 2.4.0 released.

Community:
* No issues that require the board attention.
* The community continues to grow and be very active.
* We welcome Christian Schneider as a new committer (already a cxf committer)
* We welcome Christian Mueller as a new committer (waiting for an account)
* Other contributors submitted iclas and volunteer to help out with the wiki doc
Development:
* Development continues at an intense pace on trunk
* Development on the 1.x release branch slowed down. Although still in use,
most other projects we know of that use Camel migrated to 2.x. We are
currently discussing when would be the right time to discontinue development
for the 1.x version.
* We are looking at the quality of our releases and found it in extremely
good shape. The rat plugin revealed a few xml test data files that are
missing the apache header and we are correcting that (camel has over 4700
unit tests).
Releases:
* Camel 2.3.0 released.
* Camel 1.6.3. maintenance released.

Community:
* No issues that require the board attention.
* The community continues to be very active.
* Two new committers added: Ashwin Karpe and Stanley Lewis
* There are a few other very active contributors on our radar
Development:
* Development continues at the same intense pace on both trunk
and maintenance 1.x
* No plans to discontinue support for camel 1.x yet, but we
may need to discuss that soon.
* Most of the other projects using camel (we know of) already
upgraded to camel 2.x
Releases:
* Camel 2.2.0 released.

Community:
* No issues that require the board attention.
* Another busy quarter with increased contributions from the community.
* Mailing lists continue to be very active.
* Martin Krasser accepted as new committer.
* We are keeping an eye on a few other active contributors to become
committers.
Development:
* Development continues on both 1.x maintenance branch and trunk.
* Another maintenance release of the 1.x branch planned for next quarter.
* Camel 2.2.0 planned for next quarter.
Releases:
* Camel 1.6.2 (maintenance) released.
* Camel 2.1.0 released.

Community:
* We saw the usual level of intense activity this quarter.
* The community continues to grow.
* Charles Moulliard is a new committer.
Development:
* Development continues on both 1.x maintenance branch and trunk.
* Camel continues to gain ground as an integration framework.
* Final release of Camel 2.0 expected in a month or so.
Releases:
* Camel 1.6.1 maintenance release.
* Camel 2.0-M2 just released.

Community:
* The Camel community continues to be very active.
* Camel is participating in the Google SOC with 2 projects.
* No new committers.
Development:
* Lots of contributions from committers and community on trunk.
* New components proposed by the community are under evaluation.
* Final release of Camel 2.0 and 1.x maintenance release planned for
this quarter.
Releases:
* None this month.

Apache Camel PMC Board Report, March 2009
Community:
* The Camel community continues to be very active and growing.
* Increased traffic on the development and user lists indicate wider
adoption of Camel.
* No new committers.
Development:
* Lots of contributions from committers and community on trunk.
* We just issued the first milestone release of Camel 2.0.
* Final release of Camel 2.0 planned for next quarter.
* Development on the camel 1.x is slowing down while the focus shifted to 2.0.
* Camel 1.x will be still maintained for the foreseeable future.
Releases:
* Camel 2.0-M1 released.

Community:
* TLP infrastructure transition is complete (INFRA-1830).
* Community is very active on both camel-1.x branch and the trunk.
* The development and user lists continue to be very active.
* No new committers.
Development:
* Lots of contributions from committers and community on both
camel-1.x branch and trunk.
Releases:
* Camel 1.6.0 released.

Community:
* The Camel community is very excited about becoming a TLP.
* We started the process of moving the infrastructure (INFRA-1830).
* Community is vibrant and contributing new features, components and
tutorials to Camel.
* The development and user lists continue to be very active.
* No new committers.
* A privacy policy has been added to the website and wiki.
Development:
* Lots of development effort continues.
Releases:
* No new releases in the past month.
* We plan a new Camel 1.6 release once we migrate the infrastructure.

Establish the Apache Camel Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of an
open-source integration framework based on known Enterprise
Integration Patterns for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Camel PMC",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Camel Project be and hereby is
responsible for the creation and maintenance of an open-source
integration framework based on known Enterprise Integration
Patterns; and be it further
RESOLVED, that the office of "Vice President, Apache Camel" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Camel Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Camel Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Camel Project:
* Jonathan Anstey <janstey@apache.org>
* Hiram Chirino <chirino@apache.org>
* Rob Davies <rdavies@apache.org>
* Claus Ibsen <davsclaus@apache.org>
* David Jencks <djencks@apache.org>
* Willem Jiang <ningjiang@apache.org>
* Roman Kalukiewicz <romkal@apache.org>
* Jacek Laskowski <jlaskowski@apache.org>
* Aaron Mulder <ammulder@apache.org>
* Guillaume Nodet <gnodet@apache.org>
* Nicky Sandhu <nsandhu@apache.org>
* Bruce Snyder <bsnyder@apache.org>
* James Strachan <jstrachan@apache.org>
* William Tam <wtam@apache.org>
* Gary Tully <gtully@apache.org>
* Gert Vanthienen <gertv@apache.org>
* Hadrian Zbarcea <hadrian@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hadrian Zbarcea
be appointed to the office of Vice President, Apache Camel,
to serve in accordance with and subject to the direction
of the Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache Camel PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Camel Project; and be it further
RESOLVED, that the Apache ActiveMQ Project be and hereby
is tasked with the migration and rationalization of the Apache
ActiveMQ CAMEL sub-project; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
ActiveMQ Camel sub-project encumbered upon the
Apache ActiveMQ Project are hereafter discharged.
Special Order 7B, Establish the Apache Camel Project, was
approved by Unanimous Vote of the directors present.