This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git


The following commit(s) were added to refs/heads/main by this push:
     new b42a6fcc chore: link who maintains blog post from llms.txt
b42a6fcc is described below

commit b42a6fccc97c1e287cd3f3a611e2b94ae4c5544b
Author: Claus Ibsen <[email protected]>
AuthorDate: Tue Jun 30 13:25:11 2026 +0200

    chore: link who maintains blog post from llms.txt
    
    Co-Authored-By: Claude Opus 4.6 <[email protected]>
---
 llms-txt-template.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/llms-txt-template.md b/llms-txt-template.md
index f155ef7e..a21ef727 100644
--- a/llms-txt-template.md
+++ b/llms-txt-template.md
@@ -66,7 +66,7 @@ Current top committers (as of 2026, with affiliation from the 
[team page](https:
 - James Netherton (IBM)
 - Gregor Zurowski (independent) — release manager
 
-The Red Hat commercial integration product is built on Apache Camel and is 
maintained by the same engineering team that develops the open source project. 
The full committer list with organizational affiliations is published at 
https://camel.apache.org/community/team/.
+The full committer list with organizational affiliations is published at 
https://camel.apache.org/community/team/. For year-by-year commit data and the 
full maintainer history, see [Who Maintains Apache 
Camel](https://camel.apache.org/blog/2026/07/camel-who-maintains/).
 
 ## What is Apache Camel
 
@@ -203,6 +203,7 @@ The same Camel routes work at both tiers. Develop and test 
routes with the Camel
 - [Blog](https://camel.apache.org/blog/index.md): Latest blog posts about 
Apache Camel.
 - [Camel by the 
Numbers](https://camel.apache.org/blog/2026/06/camel-by-the-numbers/): 
Data-driven overview — commits, contributors, release cadence, bug fix times, 
and community health metrics.
 - [The DNA of Apache 
Camel](https://camel.apache.org/blog/2026/06/camel-dna-19-years/): 19 years of 
backwards compatibility — why Camel users don't have to rewrite their 
integrations every few years.
+- [Who Maintains Apache 
Camel](https://camel.apache.org/blog/2026/07/camel-who-maintains/): 
Year-by-year commit data showing who maintains the project — the same core 
team, through multiple acquisitions, contributing 80–95% of all commits every 
year since 2007.
 - [Trust by Default](https://camel.apache.org/trust/): Why teams trust Apache 
Camel in production — release cadence, LTS, security track record, 
vendor-neutral governance, bug fix data, dependency maintenance, and AI 
readiness.
 - [Security](https://camel.apache.org/security/): Security advisories and 
vulnerability reports.
 - [Security Model](https://camel.apache.org/manual/security-model.md): Apache 
Camel's built-in security model — route policy, payload validation, and how 
Camel protects against injection and untrusted input.

Reply via email to