This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/comdev-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 13f8e60a Updated asf-site from main at
81dae681a5b53024f8992047559d2dfeac25a99d
13f8e60a is described below
commit 13f8e60a8a7eaef3fafe8903bb2fd46d5f549338
Author: jenkins <[email protected]>
AuthorDate: Wed Jun 10 13:13:08 2026 +0000
Updated asf-site from main at 81dae681a5b53024f8992047559d2dfeac25a99d
Built from
https://ci-builds.apache.org/job/Community%20Development/job/site/job/main/237/
---
content/_pagefind/fragment/en_1463190.pf_fragment | Bin 0 -> 2558 bytes
content/_pagefind/fragment/en_1771276.pf_fragment | Bin 4636 -> 0 bytes
content/_pagefind/fragment/en_24e2a33.pf_fragment | Bin 0 -> 2314 bytes
content/_pagefind/fragment/en_4b95f9a.pf_fragment | Bin 1412 -> 0 bytes
content/_pagefind/fragment/en_9e4a51d.pf_fragment | Bin 2122 -> 0 bytes
content/_pagefind/fragment/en_b4aa81e.pf_fragment | Bin 0 -> 3526 bytes
content/_pagefind/fragment/en_d554d64.pf_fragment | Bin 1822 -> 0 bytes
content/_pagefind/fragment/en_ff37a58.pf_fragment | Bin 0 -> 4369 bytes
content/_pagefind/index/en_1c8ff95.pf_index | Bin 0 -> 32170 bytes
content/_pagefind/index/en_21147aa.pf_index | Bin 29082 -> 0 bytes
content/_pagefind/index/en_2256f60.pf_index | Bin 0 -> 32982 bytes
content/_pagefind/index/en_2fb1b5c.pf_index | Bin 0 -> 29583 bytes
content/_pagefind/index/en_365ea14.pf_index | Bin 0 -> 30172 bytes
content/_pagefind/index/en_3d8ff15.pf_index | Bin 32778 -> 0 bytes
content/_pagefind/index/en_40eec56.pf_index | Bin 30851 -> 0 bytes
content/_pagefind/index/en_53f16c3.pf_index | Bin 31030 -> 0 bytes
content/_pagefind/index/en_a1e9d1c.pf_index | Bin 0 -> 35141 bytes
content/_pagefind/index/en_a2cd527.pf_index | Bin 0 -> 31079 bytes
content/_pagefind/index/en_a48909f.pf_index | Bin 30795 -> 0 bytes
content/_pagefind/index/en_ad43d3d.pf_index | Bin 29629 -> 0 bytes
content/_pagefind/index/en_bc237c7.pf_index | Bin 0 -> 6580 bytes
content/_pagefind/index/en_bf2b258.pf_index | Bin 32263 -> 0 bytes
content/_pagefind/index/en_c69c57f.pf_index | Bin 0 -> 30647 bytes
content/_pagefind/index/en_cbe23ad.pf_index | Bin 6521 -> 0 bytes
content/_pagefind/index/en_cf6d643.pf_index | Bin 0 -> 29218 bytes
content/_pagefind/index/en_d84d214.pf_index | Bin 34021 -> 0 bytes
content/_pagefind/index/en_d951591.pf_index | Bin 29361 -> 0 bytes
content/_pagefind/index/en_de1f7c9.pf_index | Bin 0 -> 29129 bytes
content/_pagefind/index/en_eb5a441.pf_index | Bin 0 -> 31107 bytes
content/_pagefind/index/en_fef29cf.pf_index | Bin 29149 -> 0 bytes
content/_pagefind/pagefind-entry.json | 2 +-
content/_pagefind/pagefind.en_771373e0be.pf_meta | Bin 0 -> 1600 bytes
content/_pagefind/pagefind.en_e1aa53fb94.pf_meta | Bin 1596 -> 0 bytes
content/companies/advocacy.html | 60 ++++-
content/companies/benefits.html | 122 +++++++---
content/companies/employ.html | 267 +++++++++++++---------
content/companies/index.xml | 8 +-
content/companies/sponsor.html | 104 +++++++--
content/index.xml | 8 +-
content/sitemap.xml | 24 +-
40 files changed, 406 insertions(+), 189 deletions(-)
diff --git a/content/_pagefind/fragment/en_1463190.pf_fragment
b/content/_pagefind/fragment/en_1463190.pf_fragment
new file mode 100644
index 00000000..cc6ca003
Binary files /dev/null and b/content/_pagefind/fragment/en_1463190.pf_fragment
differ
diff --git a/content/_pagefind/fragment/en_1771276.pf_fragment
b/content/_pagefind/fragment/en_1771276.pf_fragment
deleted file mode 100644
index 14e117e4..00000000
Binary files a/content/_pagefind/fragment/en_1771276.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/fragment/en_24e2a33.pf_fragment
b/content/_pagefind/fragment/en_24e2a33.pf_fragment
new file mode 100644
index 00000000..6eb51ce9
Binary files /dev/null and b/content/_pagefind/fragment/en_24e2a33.pf_fragment
differ
diff --git a/content/_pagefind/fragment/en_4b95f9a.pf_fragment
b/content/_pagefind/fragment/en_4b95f9a.pf_fragment
deleted file mode 100644
index 2ab6ba74..00000000
Binary files a/content/_pagefind/fragment/en_4b95f9a.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/fragment/en_9e4a51d.pf_fragment
b/content/_pagefind/fragment/en_9e4a51d.pf_fragment
deleted file mode 100644
index 4a8f717d..00000000
Binary files a/content/_pagefind/fragment/en_9e4a51d.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/fragment/en_b4aa81e.pf_fragment
b/content/_pagefind/fragment/en_b4aa81e.pf_fragment
new file mode 100644
index 00000000..61c7b96e
Binary files /dev/null and b/content/_pagefind/fragment/en_b4aa81e.pf_fragment
differ
diff --git a/content/_pagefind/fragment/en_d554d64.pf_fragment
b/content/_pagefind/fragment/en_d554d64.pf_fragment
deleted file mode 100644
index 6844de75..00000000
Binary files a/content/_pagefind/fragment/en_d554d64.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/fragment/en_ff37a58.pf_fragment
b/content/_pagefind/fragment/en_ff37a58.pf_fragment
new file mode 100644
index 00000000..f7f5be20
Binary files /dev/null and b/content/_pagefind/fragment/en_ff37a58.pf_fragment
differ
diff --git a/content/_pagefind/index/en_1c8ff95.pf_index
b/content/_pagefind/index/en_1c8ff95.pf_index
new file mode 100644
index 00000000..a4724cc5
Binary files /dev/null and b/content/_pagefind/index/en_1c8ff95.pf_index differ
diff --git a/content/_pagefind/index/en_21147aa.pf_index
b/content/_pagefind/index/en_21147aa.pf_index
deleted file mode 100644
index 270dcf72..00000000
Binary files a/content/_pagefind/index/en_21147aa.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_2256f60.pf_index
b/content/_pagefind/index/en_2256f60.pf_index
new file mode 100644
index 00000000..3862f4f7
Binary files /dev/null and b/content/_pagefind/index/en_2256f60.pf_index differ
diff --git a/content/_pagefind/index/en_2fb1b5c.pf_index
b/content/_pagefind/index/en_2fb1b5c.pf_index
new file mode 100644
index 00000000..19958993
Binary files /dev/null and b/content/_pagefind/index/en_2fb1b5c.pf_index differ
diff --git a/content/_pagefind/index/en_365ea14.pf_index
b/content/_pagefind/index/en_365ea14.pf_index
new file mode 100644
index 00000000..3eb55b9e
Binary files /dev/null and b/content/_pagefind/index/en_365ea14.pf_index differ
diff --git a/content/_pagefind/index/en_3d8ff15.pf_index
b/content/_pagefind/index/en_3d8ff15.pf_index
deleted file mode 100644
index c5b85d88..00000000
Binary files a/content/_pagefind/index/en_3d8ff15.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_40eec56.pf_index
b/content/_pagefind/index/en_40eec56.pf_index
deleted file mode 100644
index cb78f0f7..00000000
Binary files a/content/_pagefind/index/en_40eec56.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_53f16c3.pf_index
b/content/_pagefind/index/en_53f16c3.pf_index
deleted file mode 100644
index 3c079095..00000000
Binary files a/content/_pagefind/index/en_53f16c3.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_a1e9d1c.pf_index
b/content/_pagefind/index/en_a1e9d1c.pf_index
new file mode 100644
index 00000000..d05d1bd8
Binary files /dev/null and b/content/_pagefind/index/en_a1e9d1c.pf_index differ
diff --git a/content/_pagefind/index/en_a2cd527.pf_index
b/content/_pagefind/index/en_a2cd527.pf_index
new file mode 100644
index 00000000..d9ba88ec
Binary files /dev/null and b/content/_pagefind/index/en_a2cd527.pf_index differ
diff --git a/content/_pagefind/index/en_a48909f.pf_index
b/content/_pagefind/index/en_a48909f.pf_index
deleted file mode 100644
index 70f94972..00000000
Binary files a/content/_pagefind/index/en_a48909f.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_ad43d3d.pf_index
b/content/_pagefind/index/en_ad43d3d.pf_index
deleted file mode 100644
index 0bc34148..00000000
Binary files a/content/_pagefind/index/en_ad43d3d.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_bc237c7.pf_index
b/content/_pagefind/index/en_bc237c7.pf_index
new file mode 100644
index 00000000..5a5efb7a
Binary files /dev/null and b/content/_pagefind/index/en_bc237c7.pf_index differ
diff --git a/content/_pagefind/index/en_bf2b258.pf_index
b/content/_pagefind/index/en_bf2b258.pf_index
deleted file mode 100644
index 59352778..00000000
Binary files a/content/_pagefind/index/en_bf2b258.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_c69c57f.pf_index
b/content/_pagefind/index/en_c69c57f.pf_index
new file mode 100644
index 00000000..732b2a37
Binary files /dev/null and b/content/_pagefind/index/en_c69c57f.pf_index differ
diff --git a/content/_pagefind/index/en_cbe23ad.pf_index
b/content/_pagefind/index/en_cbe23ad.pf_index
deleted file mode 100644
index 23c648cc..00000000
Binary files a/content/_pagefind/index/en_cbe23ad.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_cf6d643.pf_index
b/content/_pagefind/index/en_cf6d643.pf_index
new file mode 100644
index 00000000..11705744
Binary files /dev/null and b/content/_pagefind/index/en_cf6d643.pf_index differ
diff --git a/content/_pagefind/index/en_d84d214.pf_index
b/content/_pagefind/index/en_d84d214.pf_index
deleted file mode 100644
index 73fc9066..00000000
Binary files a/content/_pagefind/index/en_d84d214.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_d951591.pf_index
b/content/_pagefind/index/en_d951591.pf_index
deleted file mode 100644
index bc5df6f5..00000000
Binary files a/content/_pagefind/index/en_d951591.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_de1f7c9.pf_index
b/content/_pagefind/index/en_de1f7c9.pf_index
new file mode 100644
index 00000000..5ca1864b
Binary files /dev/null and b/content/_pagefind/index/en_de1f7c9.pf_index differ
diff --git a/content/_pagefind/index/en_eb5a441.pf_index
b/content/_pagefind/index/en_eb5a441.pf_index
new file mode 100644
index 00000000..69d8c9b0
Binary files /dev/null and b/content/_pagefind/index/en_eb5a441.pf_index differ
diff --git a/content/_pagefind/index/en_fef29cf.pf_index
b/content/_pagefind/index/en_fef29cf.pf_index
deleted file mode 100644
index 1c34d384..00000000
Binary files a/content/_pagefind/index/en_fef29cf.pf_index and /dev/null differ
diff --git a/content/_pagefind/pagefind-entry.json
b/content/_pagefind/pagefind-entry.json
index 6056e242..41c62425 100644
--- a/content/_pagefind/pagefind-entry.json
+++ b/content/_pagefind/pagefind-entry.json
@@ -1 +1 @@
-{"version":"1.0.3","languages":{"en":{"hash":"en_e1aa53fb94","wasm":"en","page_count":182}}}
\ No newline at end of file
+{"version":"1.0.3","languages":{"en":{"hash":"en_771373e0be","wasm":"en","page_count":182}}}
\ No newline at end of file
diff --git a/content/_pagefind/pagefind.en_771373e0be.pf_meta
b/content/_pagefind/pagefind.en_771373e0be.pf_meta
new file mode 100644
index 00000000..b79a8729
Binary files /dev/null and b/content/_pagefind/pagefind.en_771373e0be.pf_meta
differ
diff --git a/content/_pagefind/pagefind.en_e1aa53fb94.pf_meta
b/content/_pagefind/pagefind.en_e1aa53fb94.pf_meta
deleted file mode 100644
index 8c6cc7b6..00000000
Binary files a/content/_pagefind/pagefind.en_e1aa53fb94.pf_meta and /dev/null
differ
diff --git a/content/companies/advocacy.html b/content/companies/advocacy.html
index 181abb0a..b2667c6a 100644
--- a/content/companies/advocacy.html
+++ b/content/companies/advocacy.html
@@ -9,12 +9,12 @@
<meta property="og:url"
content="https://community.apache.org/companies/advocacy.html";>
<meta property="og:site_name" content="ASF Community Development">
<meta property="og:title" content="Open Source Advocacy">
- <meta property="og:description" content="Open Source Advocacy ¶ Since the
earliest days of the Apache Software Foundation, companies have built their
business and reputation around ASF projects, and we have always encouraged
that. We, in turn, depends on the good will of companies. How companies speak
about ASF projects is a critical part of our public image.
-Respect Our Brands ¶ Like any organization, the ASF has Trademark Policy which
describes appropriate and inappropriate ways to use the brand of the ASF, and
of ASF projects. We expect companies to familiarize themselves with these
policies, just as they would when working with another company or partner.">
+ <meta property="og:description" content="Open Source Advocacy ¶ How your
company talks about ASF projects directly affects how willing those communities
are to work with you. Companies that speak respectfully about open source
projects — giving credit to the community, and respecting project brands —
build the reputation and trust that opens doors to deeper collaboration.
+Since the earliest days of the Apache Software Foundation, companies have
built their business and reputation around ASF projects, and we have always
encouraged that. We, in turn, depend on the goodwill of companies. How
companies speak about ASF projects is a critical part of our public image — and
of yours.">
<meta property="og:locale" content="en">
<meta property="og:type" content="article">
<meta property="article:section" content="companies">
- <meta property="article:modified_time" content="2026-01-16T11:04:33-05:00">
+ <meta property="article:modified_time" content="2026-06-09T14:13:03-04:00">
<meta property="article:tag" content="Companies">
<meta property="article:tag" content="Advocacy">
<meta property="article:tag" content="Branding">
@@ -202,18 +202,39 @@ Respect Our Brands ¶ Like any organization, the ASF has
Trademark Policy which
<br><br>
<h1 id="open-source-advocacy">Open Source Advocacy <a
class="headerlink" title="Permalink"
href="#open-source-advocacy">¶</a></h1>
+<p>How your company talks about ASF projects directly affects how willing
+those communities are to work with you. Companies that speak
+respectfully about open source projects — giving credit to the
+community, and respecting project brands — <a
href="/companies/benefits.html#reputation-and-trust">build the reputation and
+trust</a> that opens doors
+to deeper collaboration.</p>
<p>Since the earliest days of the Apache Software Foundation, companies
have built their business and reputation around ASF projects, and we
-have always encouraged that. We, in turn, depends on the good will of
+have always encouraged that. We, in turn, depend on the goodwill of
companies. How companies speak about ASF projects is a critical part of
-our public image.</p>
+our public image — and of yours.</p>
+<nav id="TableOfContents">
+ <ul>
+ <li><a href="#respect-our-brands">Respect Our Brands</a></li>
+ <li><a href="#be-proactive-about-education">Be Proactive About
Education</a></li>
+ <li><a href="#community-first">Community First</a></li>
+ <li><a href="#see-also">See Also</a></li>
+ </ul>
+</nav>
<h2 id="respect-our-brands">Respect Our Brands <a class="headerlink"
title="Permalink" href="#respect-our-brands">¶</a></h2>
-<p>Like any organization, the ASF has <a
href="https://www.apache.org/foundation/marks/";>Trademark
-Policy</a> which describes
-appropriate and inappropriate ways to use the brand of the ASF, and of
+<p>Like any organization, the ASF has a <a
href="https://www.apache.org/foundation/marks/";>Trademark
+Policy</a> that describes
+appropriate and inappropriate ways to use the brand of the ASF and of
ASF projects. We expect companies to familiarize themselves with these
policies, just as they would when working with another company or
partner.</p>
+<p>Respecting project brands isn’t just a legal obligation — it signals
+that your company understands how open source governance works, which
+builds <a href="/companies/benefits.html#reputation-and-trust">credibility
with the project
+community</a> and
+strengthens your <a
href="/companies/benefits.html#business-and-strategic-advantages">strategic
+partnerships</a>
+with other participants.</p>
<h2 id="be-proactive-about-education">Be Proactive About Education <a
class="headerlink" title="Permalink"
href="#be-proactive-about-education">¶</a></h2>
<p>Be sure that anyone speaking on behalf of your company understands
and respects the <a href="https://www.apache.org/foundation/marks/";>ASF
Trademark
@@ -228,15 +249,30 @@ about how best to represent your work in and around these
communities.</p>
<h2 id="community-first">Community First <a class="headerlink"
title="Permalink" href="#community-first">¶</a></h2>
<p>When you mention ASF projects, we ask that you put the community first.
It’s great to celebrate what your company and employees are doing in and
-around ASF projects - we welcome and encourage that! - but be sure to
+around ASF projects — we welcome and encourage that! — but be sure to
give credit where it’s due. The community as a whole makes our projects
work, and contributes to your success.</p>
<p>Some companies make claims about their involvement in ASF projects that
-imply that they own the project, or are primarily responsible for it.
+imply they own the project, or are primarily responsible for it.
Phrases like “creators of …” or “primary contributors
to …” devalue
the work that the rest of the community does, and unfairly take credit
-for the work that others have done to contribute to your success. We ask
-that you not do that.</p>
+for the work that others have contributed.</p>
+<p>Getting this wrong has practical consequences: projects that feel their
+work has been appropriated are less likely to prioritize your feature
+requests, less willing to coordinate releases with your schedule, and
+more skeptical of your contributors’ motives. Getting it right — giving
+genuine credit — earns goodwill that <a
href="/companies/benefits.html#influence-the-roadmap">accelerates everything
+else</a> you’re trying to
+achieve in the project.</p>
+<h2 id="see-also">See Also <a class="headerlink" title="Permalink"
href="#see-also">¶</a></h2>
+<ul>
+<li><a href="/companies/benefits.html">Benefits of open source
participation</a> —
+why your company’s reputation in project communities matters</li>
+<li><a href="/companies/employ.html">Employing contributors</a> — practical
ways to
+participate</li>
+<li><a href="/projectIndependence.html">Project Independence</a> — why the ASF
+values vendor-neutral governance</li>
+</ul>
</div>
diff --git a/content/companies/benefits.html b/content/companies/benefits.html
index 629bc612..a623a750 100644
--- a/content/companies/benefits.html
+++ b/content/companies/benefits.html
@@ -9,12 +9,13 @@
<meta property="og:url"
content="https://community.apache.org/companies/benefits.html";>
<meta property="og:site_name" content="ASF Community Development">
<meta property="og:title" content="Benefits of Open Source Participation">
- <meta property="og:description" content="Benefits of ASF Participation ¶
Companies that actively participate in ASF projects realize significant
strategic and operational advantages that extend far beyond cost savings. It’s
important to think strategically about how, where, and why you will participate
and measure impact.
-Influence the Roadmap ¶ While it can sometimes take months, or years, to gain
expertise and trust in an established community, showing up to do the daily
project maintenance – issue and PR triage; reviewing PRs; planning and
executing community events; answering user questions – you’ll quickly begin to
establish that you can be trusted, which will make it easier for you to
influence the direction of the project.">
+ <meta property="og:description" content="Contributing upstream is not
charity. It’s a strategic investment in influence, talent, velocity, and
business continuity — for the software you already depend on.
+Benefits of ASF Participation ¶ Companies that actively participate in ASF
projects realize significant strategic and operational advantages that extend
far beyond cost savings. It’s important to think strategically about how,
where, and why you will participate and measure impact.
+Influence the Roadmap Recruiting and Talent Development Faster Problem
Resolution Reduced Integration Cost Ecosystem Health as Business Continuity
Reputation and Trust Business and Strategic Advantages Influence the Roadmap ¶
While it can sometimes take months, or years, to gain expertise and trust in an
established community, showing up to do the daily project maintenance — issue
and PR triage, reviewing PRs, planning and executing community events,
answering user questions — you’ll beg [...]
<meta property="og:locale" content="en">
<meta property="og:type" content="article">
<meta property="article:section" content="companies">
- <meta property="article:modified_time" content="2026-01-16T11:04:33-05:00">
+ <meta property="article:modified_time" content="2026-06-09T14:13:03-04:00">
<meta property="article:tag" content="Companies">
<meta property="article:tag" content="Benefits">
<meta property="article:tag" content="Business Value">
@@ -201,52 +202,113 @@ Influence the Roadmap ¶ While it can sometimes take
months, or years, to gain e
<br><br>
- <h1 id="benefits-of-asf-participation">Benefits of ASF Participation <a
class="headerlink" title="Permalink"
href="#benefits-of-asf-participation">¶</a></h1>
+ <blockquote>
+<p>Contributing upstream is not charity. It’s a strategic investment in
+influence, talent, velocity, and business continuity — for the
+software you already depend on.</p>
+</blockquote>
+<h1 id="benefits-of-asf-participation">Benefits of ASF Participation <a
class="headerlink" title="Permalink"
href="#benefits-of-asf-participation">¶</a></h1>
<p>Companies that actively participate in ASF projects realize significant
strategic and operational advantages that extend far beyond cost savings.
It’s important to think strategically about how, where, and why you will
participate and measure impact.</p>
+<nav id="TableOfContents">
+ <ul>
+ <li><a href="#influence-the-roadmap">Influence the Roadmap</a></li>
+ <li><a href="#recruiting-and-talent-development">Recruiting and Talent
Development</a></li>
+ <li><a href="#faster-problem-resolution">Faster Problem Resolution</a></li>
+ <li><a href="#reduced-integration-cost">Reduced Integration Cost</a></li>
+ <li><a href="#ecosystem-health-as-business-continuity">Ecosystem Health as
Business Continuity</a></li>
+ <li><a href="#reputation-and-trust">Reputation and Trust</a></li>
+ <li><a href="#business-and-strategic-advantages">Business and Strategic
Advantages</a></li>
+ </ul>
+</nav>
<h2 id="influence-the-roadmap">Influence the Roadmap <a class="headerlink"
title="Permalink" href="#influence-the-roadmap">¶</a></h2>
<p>While it can sometimes take months, or years, to gain expertise and
trust in an established community, showing up to do the daily
-project maintenance – issue and PR triage; reviewing PRs; planning and
-executing community events; answering user questions – you’ll
quickly
-begin to establish that you can be trusted, which will make it easier
-for you to influence the direction of the project.</p>
+project maintenance — issue and PR triage, reviewing PRs, planning and
+executing community events, answering user questions — you’ll begin to
+establish credibility, which makes it easier to influence the direction
+of the project.</p>
<p>Decisions about the direction of Apache projects are made by the people
who show up to participate in the conversation. If you don’t join the
conversation, then your competitors will decide how tomorrow’s
technology will shape up.</p>
-<p>Make sure someone on your team is reading the project <a
href="https://www.apache.org/foundation/mailinglists.html";>mailing
+<p>Make sure someone on your team is reading the project <a
href="https://lists.apache.org/";>mailing
lists</a> every day,
-and advocating for your priorities. That’s what community means –
-showing up to own the future of the project.</p>
-<p>While trust does not necessarily transfer to other employees, over time,
-as project participants see your company actively contributing to the
-project, and demonstrating ownership, they’ll be more willing to work
-with you.</p>
-<h2 id="recruiting">Recruiting <a class="headerlink" title="Permalink"
href="#recruiting">¶</a></h2>
+and advocating for your priorities. That’s what community means —
+showing up and having a say in where the project goes.</p>
+<p>When you have engineers who regularly participate in a project, you’re
+more likely to earn a seat at the table where roadmap decisions happen —
+deprecations, API changes, release timelines. You learn about breaking
+changes months before they ship, not after. You can advocate for
+features your teams need rather than working around their absence.</p>
+<p>This isn’t about control. It’s about having a voice
proportional to your
+stake. To understand the path from contributor to trusted community
+member, see the <a href="/contributor-ladder.html">contributor ladder</a>.</p>
+<h2 id="recruiting-and-talent-development">Recruiting and Talent Development
<a class="headerlink" title="Permalink"
href="#recruiting-and-talent-development">¶</a></h2>
<p>By working upstream on projects, you directly showcase to potential
employees what they might be working on. This helps attract the right
kind of talent to work on your priorities, and they’ll begin to see your
company as a partner in the project, and an attractive place to work.</p>
-<p>Being involved in the day-to-day life of the project
-gives you direct access to the most qualified people in the world to
-work on your team. And you know they’ll be arriving with the skills you
-need.</p>
+<p>Being involved in the day-to-day life of the project gives you direct
+access to the most qualified people in the world to work on your team.
+And you know they’ll be arriving with the skills you need.</p>
+<p>Engineers who contribute upstream also develop skills that are difficult
+to acquire any other way: navigating large unfamiliar codebases,
+collaborating asynchronously across organizations, writing code that
+meets a high external bar for quality and documentation. These are
+exactly the skills that make senior engineers effective internally, and
+they’re developed through practice, not training courses. And the skills
+aren’t purely technical — upstream participation also builds the ability
+to clearly present and defend ideas, build consensus, and advocate for a
+technical direction in a community of peers.</p>
+<p>Companies known for upstream contributions attract engineers who value
+that work — a self-reinforcing talent advantage.</p>
+<h2 id="faster-problem-resolution">Faster Problem Resolution <a
class="headerlink" title="Permalink"
href="#faster-problem-resolution">¶</a></h2>
+<p>When your engineers have existing relationships with maintainers, bug
+reports often get triaged faster. Design discussions are more likely to
+include your perspective. Security patches may be coordinated with you
+rather than being a surprise. In many projects, the difference between
+“anonymous issue reporter” and “known contributor” can
be the difference
+between weeks and days.</p>
+<h2 id="reduced-integration-cost">Reduced Integration Cost <a
class="headerlink" title="Permalink"
href="#reduced-integration-cost">¶</a></h2>
+<p>Contributing fixes upstream means they ship in the next release for
+everyone — including you. The alternative is carrying internal patches,
+rebasing them every release, and hoping they don’t conflict with
+upstream changes. Every patch you push upstream is maintenance you’re
+far less likely to carry yourself.</p>
+<h2 id="ecosystem-health-as-business-continuity">Ecosystem Health as Business
Continuity <a class="headerlink" title="Permalink"
href="#ecosystem-health-as-business-continuity">¶</a></h2>
+<p>The projects you depend on are maintained by a small number of people,
+often without dedicated funding. When those maintainers burn out or move
+on, the project stalls — and your dependency becomes a liability.
+Contributing engineering time is a direct investment in the continuity
+of software your business relies on. It’s cheaper than building an
+alternative. The ASF also accepts <a
href="https://www.apache.org/foundation/sponsorship.html";>financial
+sponsorship</a>, which
+supports the infrastructure that all projects share.</p>
+<h2 id="reputation-and-trust">Reputation and Trust <a class="headerlink"
title="Permalink" href="#reputation-and-trust">¶</a></h2>
+<p>In the open source ecosystem, reputation is currency. Companies known
+for contributing — not just consuming — can earn trust from foundations,
+maintainers, and the broader developer community. That trust opens
+doors: partnership opportunities, early access to emerging projects, and
+goodwill that’s impossible to buy with sponsorship dollars alone.</p>
+<p>In Apache projects, trust is earned by individuals — this is a core
+principle of <a href="https://www.apache.org/theapacheway/";>The Apache Way</a>.
+Don’t assume that one person’s reputation will necessarily rub off
on
+other members from the same team or organization. Over time, your
+company may gain a reputation for participation and trustworthiness, but
+that’s always built on the track record of individual contributors.</p>
<h2 id="business-and-strategic-advantages">Business and Strategic Advantages
<a class="headerlink" title="Permalink"
href="#business-and-strategic-advantages">¶</a></h2>
<p>For more than 25 years, the ASF has been a place where industry
-standards have been set and implemented. Collaborating in those
-projects is the most effective way to shape industry standards and best
-practices. You’ll be building trust with current and potential
-customers, and building strategic partnerships with other companies
-working in the same space.</p>
+standards have been set and implemented. Collaborating in
+<a href="https://projects.apache.org/";>those projects</a> is one of the most
+effective ways to shape industry standards and best practices. You’ll be
+building credibility with current and potential customers, and building
+strategic partnerships with other companies working in the same space.</p>
<p>And by collaborating with your peers on the common tasks, you’ll be
able
-to better focus on your unique business differentiators.
-Collaborate on what all share; Compete where you excel.</p>
-<p><em>The benefits of open source participation compound over time, creating
-sustainable competitive advantages and fostering innovation that drives
-long-term business success.</em></p>
+to better focus on your unique business differentiators. Collaborate on
+what you have in common; compete where you’re distinctive.</p>
</div>
diff --git a/content/companies/employ.html b/content/companies/employ.html
index 3b93977f..702ba1be 100644
--- a/content/companies/employ.html
+++ b/content/companies/employ.html
@@ -9,13 +9,13 @@
<meta property="og:url"
content="https://community.apache.org/companies/employ.html";>
<meta property="og:site_name" content="ASF Community Development">
<meta property="og:title" content="Employing Open Source Contributors">
- <meta property="og:description" content="Employing or Contracting with Open
Source Contributors ¶ If your business relies on an open source project,
employing, contracting with or otherwise financially supporting, contributors
to the project is the most effective way to ensure that your priorities are
reflected in project decisions. (See also Recruiting and Employee Satisfaction)
+ <meta property="og:description" content="Employing or Contracting with Open
Source Contributors ¶ If your business relies on an open source project,
employing, contracting with, or otherwise financially supporting contributors
to the project is the most effective way to influence project decisions and
ensure your priorities are reflected in the roadmap. (See also Recruiting and
Talent Development)
This goes far beyond code contributions, although that is the most obvious and
visible way that you can participate.
Think of staffing an open source project exactly the same way you would think
about staffing an internal software development project or working with
external contractors. What positions would you staff if you weren’t sharing the
load with the community? Are those positions being adequately covered?">
<meta property="og:locale" content="en">
<meta property="og:type" content="article">
<meta property="article:section" content="companies">
- <meta property="article:modified_time" content="2026-01-16T13:32:27-05:00">
+ <meta property="article:modified_time" content="2026-06-09T14:13:03-04:00">
<meta property="article:tag" content="Companies">
<meta property="article:tag" content="Employment">
<meta property="article:tag" content="Contributors">
@@ -203,12 +203,13 @@ Think of staffing an open source project exactly the same
way you would think ab
<br><br>
<h1
id="employing-or-contracting-with-open-source-contributors">Employing or
Contracting with Open Source Contributors <a class="headerlink"
title="Permalink"
href="#employing-or-contracting-with-open-source-contributors">¶</a></h1>
-<p>If your business relies on an open source project, employing, contracting
with or
-otherwise financially supporting,
-contributors to the project is the most effective way to ensure that
-your priorities are reflected in project decisions.
-(See also <a
href="/companies/benefits.html#recruiting-and-employee-satisfaction">Recruiting
and Employee
-Satisfaction</a>)</p>
+<p>If your business relies on an open source project, employing, contracting
with, or
+otherwise financially supporting
+contributors to the project is the most effective way to <a
href="/companies/benefits.html#influence-the-roadmap">influence
+project decisions</a> and
+ensure your priorities are reflected in the roadmap.
+(See also <a
href="/companies/benefits.html#recruiting-and-talent-development">Recruiting
and Talent
+Development</a>)</p>
<p>This goes <a href="/contributors/non-code.html">far beyond code
contributions</a>,
although that is the most obvious and visible way that you can participate.</p>
<p>Think of staffing an open source project exactly the same way you would
@@ -217,145 +218,185 @@ positions would you staff if you weren’t sharing
the load with the
community? Are those positions being adequately covered?</p>
<p>Dedicating employee or contractors’ time to positions like marketing,
events, and
end-user support, as well as software development, significantly
-increases your influence and trust in the project community.</p>
+increases your <a
href="/companies/benefits.html#reputation-and-trust">influence and
+trust</a> in the project
+community.</p>
+<nav id="TableOfContents">
+ <ul>
+ <li><a href="#effective-ways-to-contribute">Effective Ways to
Contribute</a>
+ <ul>
+ <li><a href="#allocate-dedicated-time">Allocate Dedicated Time</a></li>
+ <li><a href="#recognize-contributions">Recognize Contributions</a></li>
+ <li><a href="#support-conference-and-meetup-participation">Support
Conference and Meetup Participation</a></li>
+ </ul>
+ </li>
+ <li><a href="#chop-wood-carry-water-routine-maintenance">Chop Wood, Carry
Water (Routine Maintenance)</a>
+ <ul>
+ <li><a href="#triage">Triage</a></li>
+ <li><a href="#infrastructure">Infrastructure</a></li>
+ <li><a href="#user-support">User Support</a></li>
+ </ul>
+ </li>
+ <li><a href="#transparency">Transparency</a></li>
+ <li><a href="#respect-project-independence">Respect Project
Independence</a></li>
+ <li><a href="#support-individual-contributors">Support Individual
Contributors</a>
+ <ul>
+ <li><a href="#internship-and-fellowship-programs">Internship and
Fellowship Programs</a></li>
+ </ul>
+ </li>
+ <li><a href="#getting-started">Getting Started</a></li>
+ </ul>
+</nav>
<h2 id="effective-ways-to-contribute">Effective Ways to Contribute <a
class="headerlink" title="Permalink"
href="#effective-ways-to-contribute">¶</a></h2>
<p>While many companies contribute here and there to open source projects,
having a carefully considered strategy for doing so will lead to more
-consistent, measurable results, and greater influence in the project’s
-decisions and roadmap.</p>
+consistent, measurable results, and greater <a
href="/companies/benefits.html#influence-the-roadmap">influence in the
project’s
+decisions and roadmap</a>.</p>
<h3 id="allocate-dedicated-time">Allocate Dedicated Time <a class="headerlink"
title="Permalink" href="#allocate-dedicated-time">¶</a></h3>
-<p>Earning trust in open source projects takes consistent engagement, and
-visibility to the community. Thus, having guaranteed dedicated time to
-focus on upstream work will result in better long-term results.</p>
-<p>Giving employees a specific time allocation - 10-20% of their schedule
-is typical - will ensure that they remain visible to the community, and
+<p><a href="/companies/benefits.html#reputation-and-trust">Earning trust</a>
in open
+source projects takes consistent engagement and visibility to the
+community. Having guaranteed dedicated time to focus on upstream work
+will produce better long-term results.</p>
+<p>Giving employees a specific time allocation — 10-20% of their schedule
+is typical — will ensure that they remain visible to the community, and
are able to have focused time to build their skills.</p>
-<p>Trust earned by one contributor does not necessarily rub off on your
-other employees. So don’t assume that you can just swap out one employee
+<p>Trust earned by one contributor does not necessarily transfer to your
+other employees. Don’t assume that you can just swap out one employee
for another.</p>
<h3 id="recognize-contributions">Recognize Contributions <a class="headerlink"
title="Permalink" href="#recognize-contributions">¶</a></h3>
<p>Include open source contributions in performance reviews and career
-advancement considerations. Define specific metrics, such as PRs
+advancement considerations. Define specific metrics — PRs
accepted, reviews, public speaking engagements, or promotion to
-committer or PMC member, which are tied to promotion opportunities. This
-will help employees feel appreciated, and communicate that engagement in
-open source projects is not considered charity or altruism, but is a key
-part of company goals.</p>
+committer or PMC member — and tie them to promotion opportunities. This
+communicates that engagement in open source projects is a key
+part of company goals, not charity or altruism.</p>
+<p>When employees see that upstream work is valued internally, they invest
+more deeply in it — and that deeper investment is what produces the
+<a href="/companies/benefits.html#recruiting-and-talent-development">talent
development</a>
+and <a href="/companies/benefits.html#influence-the-roadmap">roadmap
influence</a>
+your company is looking for.</p>
<h3 id="support-conference-and-meetup-participation">Support Conference and
Meetup Participation <a class="headerlink" title="Permalink"
href="#support-conference-and-meetup-participation">¶</a></h3>
<p>Fund employee attendance at relevant conferences and encourage speaking
-opportunities. Understand that attending conferences is primarily about
-creating opportunities to collaborate with peers, and this, in turn,
-will accelerate your business priorities.</p>
-<h2 id="support-individual-contributors">Support Individual Contributors <a
class="headerlink" title="Permalink"
href="#support-individual-contributors">¶</a></h2>
-<p>Supporting individual contributors financially (via B2B contracts,
-individual sponsorships, fellowships, and third party sponsor programs)
-can be a very effective way to contribute to a project if you don’t have
-full-time positions available on your payroll.</p>
-<h3 id="bug-bounties">Bug Bounties <a class="headerlink" title="Permalink"
href="#bug-bounties">¶</a></h3>
-<p>While the ASF does not ever directly pay for contributions to ASF
-projects, as a matter of principle, there are many third-party “bug
-bounty” sites that allow you to support individual contributors in their
-work on projects that you care about.</p>
-<p>The project
-<a
href="https://github.com/disclose/bug-bounty-platforms";>bug-bounty-platforms</a>
-maintains a list of such sites, along with contact information. The ASF
-does not endorse any of these sites, but developers are welcome to work
-with them as they contribute to ASF projects.</p>
-<h3 id="sponsor-and-internship-programs">Sponsor and Internship Programs <a
class="headerlink" title="Permalink"
href="#sponsor-and-internship-programs">¶</a></h3>
-<p>There are many third-party programs through which you can support
-contributors to open source projects, with <a
href="https://github.com/open-source/sponsors";>GitHub
-Sponsors</a> being one of the
-best-known.</p>
-<p>Internship programs such as <a
href="https://www.outreachy.org/";>Outreachy</a>
-provide opportunties for individuals to work a paid internship for an
-open source project. Companies can support these organizations, and thus
-indirectly fund work on projects that they care about.</p>
-<h2 id="project-independence">Project Independence <a class="headerlink"
title="Permalink" href="#project-independence">¶</a></h2>
-<p>Project independence is a central tenet of the ASF, and one of the most
-common places that companies misstep in their interactions with ASF
-projects.</p>
-<p>Take time to understand ASF ethos, the <a
href="https://www.apache.org/foundation/marks/";>ASF Trademark
-Policy</a>, and the reasons why
-we value project independence. Trust takes a long time to earn, but can
-be burned very quickly by misusing a project’s brand.</p>
-<p>There are several very practical ways that you can contribute to overall
-project health, while earning trust for your contributors.</p>
-<h3 id="broad-project-ownership">Broad Project Ownership <a class="headerlink"
title="Permalink" href="#broad-project-ownership">¶</a></h3>
-<p>Ensure contributions align with long-term project goals rather than
-solely short-term company priorities. That ensures that the project as a
-whole remains healthy.</p>
-<p>Companies that focus only on contributions that support their own
-specific business model quickly identify themselves as not valuing the
-overall health of the project. It also makes it very difficult to
-attract broader community interest in your proposed changes, since they
-are seen as self-serving.</p>
-<h3 id="chop-wood-carry-water-routine-maintenance">Chop Wood, Carry Water
(Routine Maintenance) <a class="headerlink" title="Permalink"
href="#chop-wood-carry-water-routine-maintenance">¶</a></h3>
+opportunities. Attending conferences is primarily about
+creating opportunities to collaborate with peers, which in turn
+accelerates your <a
href="/companies/benefits.html#influence-the-roadmap">roadmap
+influence</a> and <a
href="/companies/benefits.html#recruiting-and-talent-development">talent
+pipeline</a>.</p>
+<p>See also <a
href="/companies/sponsor.html#event-and-meetup-sponsorship">Event and Meetup
Sponsorship</a>
+for ways to increase your visibility at these events.</p>
+<h2 id="chop-wood-carry-water-routine-maintenance">Chop Wood, Carry Water
(Routine Maintenance) <a class="headerlink" title="Permalink"
href="#chop-wood-carry-water-routine-maintenance">¶</a></h2>
<p>Open source communities sometimes use the phrase “chop wood, carry
-water” to talk about doing the mundane maintenance tasks that are
-required to keep a project going.</p>
-<p>Many companies focus only on the flashy new features, and ignore the
-fact that a software project needs daily care to keep going.</p>
-<h4 id="triage">Triage <a class="headerlink" title="Permalink"
href="#triage">¶</a></h4>
-<p>Participating in the weekly triage of new issue reports and pull
+water” to describe the mundane maintenance tasks required to keep a
+project going.</p>
+<p>Many companies focus only on flashy new features and ignore the
+fact that a software project needs daily care. But routine maintenance
+is where <a href="/companies/benefits.html#reputation-and-trust">trust is
built</a>
+and <a href="/companies/benefits.html#faster-problem-resolution">problem
resolution
+accelerates</a>.</p>
+<h3 id="triage">Triage <a class="headerlink" title="Permalink"
href="#triage">¶</a></h3>
+<p>Participating in weekly triage of new issue reports and pull
requests keeps a project healthy. It ensures that the project does not
-appear abandoned. And it exposes your team to parts of the project on
-which they would not otherwise gain expertise.</p>
-<p>It also identifies your contributors as people who care about the
-overall health of the project, which, in turn, earns trust and increases
-the community’s willingness to work with you.</p>
+appear abandoned. It exposes your team to parts of the project on
+which they would not otherwise gain expertise. And it identifies your
+contributors as people who care about overall project health.</p>
<p>Be sure to explicitly give your employees time to do these tasks.</p>
-<h4 id="infrastructure">Infrastructure <a class="headerlink" title="Permalink"
href="#infrastructure">¶</a></h4>
+<h3 id="infrastructure">Infrastructure <a class="headerlink" title="Permalink"
href="#infrastructure">¶</a></h3>
<p>While the physical infrastructure behind ASF projects is maintained by a
<a href="https://infra.apache.org/";>team of paid professionals</a>,
there’s more to
project infrastructure than that. Keeping the CI system running
effectively, understanding what supplementary infrastructure the project
-depends, on, and generally being useful are key ways to ensure the
-sustainability of the project.</p>
-<p>For projects that provide infrastructure, or other cloud services,
+depends on, and generally being useful are key ways to ensure
+<a
href="/companies/benefits.html#ecosystem-health-as-business-continuity">sustainability
of the project</a>.</p>
+<p>For projects that provide infrastructure or other cloud services,
donating these to the project (talk to infra about how!) is critical to
the health of ASF projects.</p>
-<h4 id="user-support">User Support <a class="headerlink" title="Permalink"
href="#user-support">¶</a></h4>
-<p>Answering user questions is the very best way to understand the pain
+<h3 id="user-support">User Support <a class="headerlink" title="Permalink"
href="#user-support">¶</a></h3>
+<p>Answering user questions is the best way to understand the pain
that your own customers are experiencing with the project. It will make
you more responsive to them, and build your own expertise, in a way that
-no other activity will do.</p>
-<h3 id="transparency">Transparency <a class="headerlink" title="Permalink"
href="#transparency">¶</a></h3>
-<p>Many companies value secrecy in their roadmap, as they believe that it
+no other activity can — which is why it directly contributes to <a
href="/companies/benefits.html#faster-problem-resolution">faster
+problem
+resolution</a> for your
+own teams.</p>
+<h2 id="transparency">Transparency <a class="headerlink" title="Permalink"
href="#transparency">¶</a></h2>
+<p>Many companies value secrecy in their roadmap, believing that it
gives them a competitive advantage in the market.</p>
<p>This is in tension with the open source focus on transparency and
collaboration. Finding an appropriate balance is key to your successful
-participation in ASF projects.</p>
-<p>Being transparent about your company priorities has several positive
-outcomes.</p>
-<h4 id="avoid-conflicts">Avoid Conflicts <a class="headerlink"
title="Permalink" href="#avoid-conflicts">¶</a></h4>
-<p>Telling the project what you will be working on can avoid conflicting
-with other work that is going in a different direction. The project can
-discuss your plans, and compromise on a mutually agreed direction,
-saving you time going down a path which will ultimately get rejected.</p>
-<h4 id="attract-collaborators">Attract Collaborators <a class="headerlink"
title="Permalink" href="#attract-collaborators">¶</a></h4>
-<p>It can be a way to identify people from outside your organization who
-share the same priority, who may work with you to achieve your goals,
-and, in the process, provide ideas and innovation that you may have
-missed had you done the work yourself behind your company walls.</p>
-<h4 id="earn-trust">Earn Trust <a class="headerlink" title="Permalink"
href="#earn-trust">¶</a></h4>
-<p>It always comes back to earning trust. Being transparent about your
-priorities shows the project what you care about. It doesn’t leave them
-guessing about your ulterior motives. The more you do this, and the more
-you live up to what you say you’re going to do, the more the project
-will be willing to work with you.</p>
+participation in ASF projects. Being transparent about your company
+priorities has several practical payoffs:</p>
+<ul>
+<li>
+<p><strong>Avoid conflicts</strong> — Telling the project what you will be
working on
+can avoid conflicting with other work that is going in a different
+direction. The project can discuss your plans and compromise on a
+mutually agreed direction, saving you time going down a path which
+will ultimately get rejected. (This is a direct example of <a
href="/companies/benefits.html#reduced-integration-cost">reduced
+integration
+cost</a>.)</p>
+</li>
+<li>
+<p><strong>Attract collaborators</strong> — You may identify people from
outside your
+organization who share the same priority, who may work with you to
+achieve your goals, providing ideas and innovation you would have
+missed behind your company walls. (See <a
href="/companies/benefits.html#business-and-strategic-advantages">Business and
Strategic
+Advantages</a>.)</p>
+</li>
+<li>
+<p><strong>Earn trust</strong> — Being transparent about your priorities shows
the
+project what you care about, rather than leaving them guessing. The
+more you live up to what you say you’re going to do, the more the
+project will be willing to work with you. (See <a
href="/companies/benefits.html#reputation-and-trust">Reputation and
+Trust</a>.)</p>
+</li>
+</ul>
+<h2 id="respect-project-independence">Respect Project Independence <a
class="headerlink" title="Permalink"
href="#respect-project-independence">¶</a></h2>
+<p>Project independence is a central tenet of the ASF, and one of the most
+common places that companies misstep. Understanding <a
href="/projectIndependence.html">why independence
+matters</a> will help you avoid burning the trust
+you’ve worked to build.</p>
+<p>A few practical guidelines:</p>
+<ul>
+<li>
+<p><strong>Broad project ownership</strong> — Ensure contributions align with
+long-term project goals rather than solely short-term company
+priorities. Companies that focus only on self-serving contributions
+quickly signal that they don’t value overall project health, making
+it harder to attract community interest in their proposed changes.</p>
+</li>
+<li>
+<p><strong>Respect the brand</strong> — Familiarize yourself and your
spokespeople
+with the <a href="https://www.apache.org/foundation/marks/";>ASF Trademark
+Policy</a>. See our <a href="/companies/advocacy.html">advocacy
+guide</a> for practical tips.</p>
+</li>
+</ul>
+<h2 id="support-individual-contributors">Support Individual Contributors <a
class="headerlink" title="Permalink"
href="#support-individual-contributors">¶</a></h2>
+<p>If you don’t have full-time positions available on your payroll,
+supporting individual contributors financially — via B2B contracts,
+individual sponsorships, fellowships, and third-party programs — is
+another effective way to invest in <a
href="/companies/benefits.html#ecosystem-health-as-business-continuity">ecosystem
health as business
+continuity</a>.</p>
+<h3 id="internship-and-fellowship-programs">Internship and Fellowship Programs
<a class="headerlink" title="Permalink"
href="#internship-and-fellowship-programs">¶</a></h3>
+<p>Programs such as <a href="https://www.outreachy.org/";>Outreachy</a> provide
+opportunities for individuals to work paid internships on open source
+projects. <a href="https://github.com/open-source/sponsors";>GitHub
Sponsors</a> is
+another well-known mechanism. Companies can support these organizations,
+and thus indirectly fund work on projects that they care about.</p>
+<p>See also <a href="/companies/sponsor.html">Financial Sponsorship</a> for
broader
+organizational funding options.</p>
<h2 id="getting-started">Getting Started <a class="headerlink"
title="Permalink" href="#getting-started">¶</a></h2>
<ol>
<li>Identify projects your company already uses or depends on</li>
<li>Connect with existing contributors in your organization</li>
<li>Start with small, manageable contributions</li>
<li>Consider sending a weekly/monthly update to the project dev list
-about what you’re focusing on. (Discuss this with the project first
-to be sure it’s welcome.)</li>
+about what you’re focusing on (discuss this with the project first
+to be sure it’s welcome)</li>
<li>Build relationships within project communities</li>
-<li>Gradually increase involvement and responsibility (See <a
href="/contributors/becomingacommitter.html">Becoming a
+<li>Gradually increase involvement and responsibility (see <a
href="/contributors/becomingacommitter.html">Becoming a
committer</a>)</li>
</ol>
-<p><em>Companies that invest in employing open source contributors create a
sustainable model that benefits the entire ecosystem while building internal
expertise and community relationships.</em></p>
</div>
diff --git a/content/companies/index.xml b/content/companies/index.xml
index 7f5151dd..82df9cc2 100644
--- a/content/companies/index.xml
+++ b/content/companies/index.xml
@@ -12,28 +12,28 @@
<link>https://community.apache.org/companies/benefits.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/companies/benefits.html</guid>
- <description><h1
id="benefits-of-asf-participation">Benefits of ASF Participation
<a class="headerlink" title="Permalink"
href="#benefits-of-asf-participation">&para;</a></h1>
<p>Companies
that actively participate in ASF projects realize significant
strategic
and operational advantages that extend far beyond cost
savings.
It&rsquo;s important to think strategically about how, where,
and why you will& [...]
+ <description><blockquote>
<p>Contributing upstream is
not charity. It&rsquo;s a strategic investment in
influence, talent,
velocity, and business continuity — for the
software you already depend
on.</p>
</blockquote>
<h1
id="benefits-of-asf-participation">Benefits of ASF Participation
<a class="headerlink" title="Permalink"
href="#benefits-of-asf-participation">&para;</a></h1>
[...]
</item>
<item>
<title>Employing Open Source Contributors</title>
<link>https://community.apache.org/companies/employ.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/companies/employ.html</guid>
- <description><h1
id="employing-or-contracting-with-open-source-contributors">Employing
or Contracting with Open Source Contributors <a class="headerlink"
title="Permalink"
href="#employing-or-contracting-with-open-source-contributors">&para;</a></h1>
<p>If
your business relies on an open source project, employing, contracting with
or
otherwise financially supporting,
contributors to the project is the
mos [...]
+ <description><h1
id="employing-or-contracting-with-open-source-contributors">Employing
or Contracting with Open Source Contributors <a class="headerlink"
title="Permalink"
href="#employing-or-contracting-with-open-source-contributors">&para;</a></h1>
<p>If
your business relies on an open source project, employing, contracting with,
or
otherwise financially supporting
contributors to the project is the
mos [...]
</item>
<item>
<title>Financial Sponsorship of Open Source</title>
<link>https://community.apache.org/companies/sponsor.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/companies/sponsor.html</guid>
- <description><h1 id="financial-sponsorship">Financial
Sponsorship <a class="headerlink" title="Permalink"
href="#financial-sponsorship">&para;</a></h1>
<p>The
sustainability of our projects relies on consistent funding
for
infrastructure, legal services, marketing, events, and many
other
expenses. Financial sponsorship is a direct way to participate
in
keeping the lights on.</p>
<h2 id=&# [...]
+ <description><h1 id="financial-sponsorship">Financial
Sponsorship <a class="headerlink" title="Permalink"
href="#financial-sponsorship">&para;</a></h1>
<p>Financial
sponsorship is a direct way to invest in the <a
href="https://community.apache.org/companies/benefits.html#ecosystem-health-as-business-continuity">business
continuity</a>
of
projects your company depends on, while gaining [...]
</item>
<item>
<title>Open Source Advocacy</title>
<link>https://community.apache.org/companies/advocacy.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/companies/advocacy.html</guid>
- <description><h1 id="open-source-advocacy">Open Source
Advocacy <a class="headerlink" title="Permalink"
href="#open-source-advocacy">&para;</a></h1>
<p>Since
the earliest days of the Apache Software Foundation, companies
have built
their business and reputation around ASF projects, and we
have always
encouraged that. We, in turn, depends on the good will of
companies. How
companies speak about ASF pro [...]
+ <description><h1 id="open-source-advocacy">Open Source
Advocacy <a class="headerlink" title="Permalink"
href="#open-source-advocacy">&para;</a></h1>
<p>How
your company talks about ASF projects directly affects how willing
those
communities are to work with you. Companies that speak
respectfully about
open source projects — giving credit to the
community, and respecting
project brands — <a href= [...]
</item>
</channel>
</rss>
diff --git a/content/companies/sponsor.html b/content/companies/sponsor.html
index cce03e99..41b8a7f1 100644
--- a/content/companies/sponsor.html
+++ b/content/companies/sponsor.html
@@ -9,13 +9,13 @@
<meta property="og:url"
content="https://community.apache.org/companies/sponsor.html";>
<meta property="og:site_name" content="ASF Community Development">
<meta property="og:title" content="Financial Sponsorship of Open Source">
- <meta property="og:description" content="Financial Sponsorship ¶ The
sustainability of our projects relies on consistent funding for infrastructure,
legal services, marketing, events, and many other expenses. Financial
sponsorship is a direct way to participate in keeping the lights on.
-ASF Sponsorship ¶ Companies can sponsor the ASF with an annual donation,
conferences sponsorship, targeted donations to a particular project, or in-kind
donations of products or services.
-Event and Meetup Sponsorship ¶ In addition to the main ASF conference, many
ASF projects have their own events. These are usually listed on
events.apache.org, and announced within the project community itself.">
+ <meta property="og:description" content="Financial Sponsorship ¶ Financial
sponsorship is a direct way to invest in the business continuity of projects
your company depends on, while gaining visibility and talent access in project
communities.
+The sustainability of ASF projects relies on consistent funding for
infrastructure, legal services, marketing, events, and many other expenses.
When you sponsor, you’re helping keep the lights on for software that’s already
in your supply chain.
+ASF Sponsorship Event and Meetup Sponsorship Supporting Individual
Contributors Bug Bounties and Contract Work Internship and Fellowship Programs
Choosing Between Sponsorship and Employment See Also ASF Sponsorship ¶
Companies can sponsor the ASF with an annual donation, conference sponsorship,
targeted donations to a particular project, or in-kind donations of products or
services.">
<meta property="og:locale" content="en">
<meta property="og:type" content="article">
<meta property="article:section" content="companies">
- <meta property="article:modified_time" content="2026-01-16T11:04:33-05:00">
+ <meta property="article:modified_time" content="2026-06-09T14:13:03-04:00">
<meta property="article:tag" content="Companies">
<meta property="article:tag" content="Sponsorship">
<meta property="article:tag" content="Funding">
@@ -203,31 +203,109 @@ Event and Meetup Sponsorship ¶ In addition to the main
ASF conference, many ASF
<br><br>
<h1 id="financial-sponsorship">Financial Sponsorship <a
class="headerlink" title="Permalink"
href="#financial-sponsorship">¶</a></h1>
-<p>The sustainability of our projects relies on consistent funding for
+<p>Financial sponsorship is a direct way to invest in the <a
href="/companies/benefits.html#ecosystem-health-as-business-continuity">business
+continuity</a>
+of projects your company depends on, while gaining visibility and
+<a href="/companies/benefits.html#recruiting-and-talent-development">talent
access</a>
+in project communities.</p>
+<p>The sustainability of ASF projects relies on consistent funding for
infrastructure, legal services, marketing, events, and many other
-expenses. Financial sponsorship is a direct way to participate in
-keeping the lights on.</p>
+expenses. When you sponsor, you’re helping keep the lights on for
+software that’s already in your supply chain.</p>
+<nav id="TableOfContents">
+ <ul>
+ <li><a href="#asf-sponsorship">ASF Sponsorship</a></li>
+ <li><a href="#event-and-meetup-sponsorship">Event and Meetup
Sponsorship</a></li>
+ <li><a href="#supporting-individual-contributors">Supporting Individual
Contributors</a>
+ <ul>
+ <li><a href="#bug-bounties-and-contract-work">Bug Bounties and
Contract Work</a></li>
+ <li><a href="#internship-and-fellowship-programs">Internship and
Fellowship Programs</a></li>
+ </ul>
+ </li>
+ <li><a href="#choosing-between-sponsorship-and-employment">Choosing
Between Sponsorship and Employment</a></li>
+ <li><a href="#see-also">See Also</a></li>
+ </ul>
+</nav>
<h2 id="asf-sponsorship">ASF Sponsorship <a class="headerlink"
title="Permalink" href="#asf-sponsorship">¶</a></h2>
<p>Companies can sponsor the ASF with an <a
href="https://apache.org/foundation/sponsorship.html";>annual
donation</a>,
-<a href="https://communityovercode.org";>conferences sponsorship</a>,
+<a href="https://communityovercode.org";>conference sponsorship</a>,
targeted donations to a particular project, or in-kind donations of
products or services.</p>
+<p>ASF sponsorship is acknowledged publicly on the Foundation website and
+at events — giving your company brand visibility across the entire
+Apache ecosystem.</p>
<h2 id="event-and-meetup-sponsorship">Event and Meetup Sponsorship <a
class="headerlink" title="Permalink"
href="#event-and-meetup-sponsorship">¶</a></h2>
<p>In addition to the <a href="https://communityovercode.org";>main ASF
conference</a>,
many ASF projects have their own events. These are usually listed on
<a href="https://events.apache.org";>events.apache.org</a>, and announced
within the
project community itself.</p>
-<p>Sponsoring, and speaking at, these events, is perhaps the fastest way to
-raise your profile in a project community, and for your employees to
-earn trust and visibility within the project.</p>
-<p>Supporting local gatherings of open source enthusiasts is a great way to
-foster community growth, and can help your company attract and retain
+<p>Sponsoring and speaking at these events is perhaps the fastest way to
+<a href="/companies/benefits.html#reputation-and-trust">raise your profile</a>
in a
+project community, and for your employees to earn trust and visibility.
+It’s also a direct path to <a
href="/companies/benefits.html#recruiting-and-talent-development">talent
+recruitment</a>
+— you’re meeting the most engaged contributors in person.</p>
+<p>Supporting local gatherings of open source enthusiasts fosters
+community growth and can help your company attract and retain
experts in your employ.</p>
<p>See also the <a
href="https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC";>Apache
Local
Communities</a>
for local and regional groups where you can engage with other ASF
enthusiasts.</p>
+<h2 id="supporting-individual-contributors">Supporting Individual Contributors
<a class="headerlink" title="Permalink"
href="#supporting-individual-contributors">¶</a></h2>
+<p>Not all financial support needs to go through the Foundation. Companies
+can also fund individual contributors directly — via contracts, bounty
+programs, fellowships, or sponsorship platforms — to accelerate work on
+projects they care about.</p>
+<p>This is particularly useful when you don’t have headcount to <a
href="/companies/employ.html">employ
+contributors directly</a>, but still want to
+invest in <a
href="/companies/benefits.html#ecosystem-health-as-business-continuity">ecosystem
+health</a>
+and <a href="/companies/benefits.html#faster-problem-resolution">faster problem
+resolution</a>.</p>
+<h3 id="bug-bounties-and-contract-work">Bug Bounties and Contract Work <a
class="headerlink" title="Permalink"
href="#bug-bounties-and-contract-work">¶</a></h3>
+<p>While the ASF does not directly pay for contributions to ASF
+projects as a matter of principle, there are many third-party “bug
+bounty” platforms that allow you to fund individual contributors for
+work on projects you depend on.</p>
+<p>The project
+<a
href="https://github.com/disclose/bug-bounty-platforms";>bug-bounty-platforms</a>
+maintains a list of such sites, along with contact information. The ASF
+does not endorse any of these sites, but developers are welcome to work
+with them as they contribute to ASF projects.</p>
+<p>Companies can also contract directly with individual contributors for
+specific work — fixing bugs, implementing features, or improving
+documentation — as long as the resulting contributions go through the
+normal project review and acceptance process.</p>
+<h3 id="internship-and-fellowship-programs">Internship and Fellowship Programs
<a class="headerlink" title="Permalink"
href="#internship-and-fellowship-programs">¶</a></h3>
+<p>Programs such as <a href="https://www.outreachy.org/";>Outreachy</a> provide
+opportunities for individuals to work paid internships on open source
+projects. <a href="https://github.com/open-source/sponsors";>GitHub
Sponsors</a> is
+another well-known mechanism. Companies can support these organizations,
+and thus indirectly fund work on projects that they care about.</p>
+<h2 id="choosing-between-sponsorship-and-employment">Choosing Between
Sponsorship and Employment <a class="headerlink" title="Permalink"
href="#choosing-between-sponsorship-and-employment">¶</a></h2>
+<p>Financial sponsorship and <a href="/companies/employ.html">employing
+contributors</a> are complementary strategies:</p>
+<ul>
+<li><strong>Sponsorship</strong> supports shared infrastructure and community
events
+that benefit all participants. It builds broad visibility and
+goodwill.</li>
+<li><strong>Employing contributors</strong> gives you direct <a
href="/companies/benefits.html#influence-the-roadmap">roadmap
+influence</a> and <a
href="/companies/benefits.html#faster-problem-resolution">faster
+problem resolution</a>
+on specific projects.</li>
+</ul>
+<p>Most companies that are serious about open source engagement do both.</p>
+<h2 id="see-also">See Also <a class="headerlink" title="Permalink"
href="#see-also">¶</a></h2>
+<ul>
+<li><a href="/companies/benefits.html">Benefits of open source
participation</a> —
+the strategic case for all forms of engagement</li>
+<li><a href="/companies/employ.html">Employing contributors</a> — staffing open
+source work directly</li>
+<li><a href="https://apache.org/foundation/sponsorship.html";>ASF Sponsorship
program</a> —
+official sponsorship tiers and details</li>
+</ul>
</div>
diff --git a/content/index.xml b/content/index.xml
index 48bb1a08..13a3f4ae 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -460,7 +460,7 @@
<link>https://community.apache.org/companies/benefits.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/companies/benefits.html</guid>
- <description><h1
id="benefits-of-asf-participation">Benefits of ASF Participation
<a class="headerlink" title="Permalink"
href="#benefits-of-asf-participation">&para;</a></h1>
<p>Companies
that actively participate in ASF projects realize significant
strategic
and operational advantages that extend far beyond cost
savings.
It&rsquo;s important to think strategically about how, where,
and why you will& [...]
+ <description><blockquote>
<p>Contributing upstream is
not charity. It&rsquo;s a strategic investment in
influence, talent,
velocity, and business continuity — for the
software you already depend
on.</p>
</blockquote>
<h1
id="benefits-of-asf-participation">Benefits of ASF Participation
<a class="headerlink" title="Permalink"
href="#benefits-of-asf-participation">&para;</a></h1>
[...]
</item>
<item>
<title>BoardReport</title>
@@ -523,14 +523,14 @@
<link>https://community.apache.org/companies/employ.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/companies/employ.html</guid>
- <description><h1
id="employing-or-contracting-with-open-source-contributors">Employing
or Contracting with Open Source Contributors <a class="headerlink"
title="Permalink"
href="#employing-or-contracting-with-open-source-contributors">&para;</a></h1>
<p>If
your business relies on an open source project, employing, contracting with
or
otherwise financially supporting,
contributors to the project is the
mos [...]
+ <description><h1
id="employing-or-contracting-with-open-source-contributors">Employing
or Contracting with Open Source Contributors <a class="headerlink"
title="Permalink"
href="#employing-or-contracting-with-open-source-contributors">&para;</a></h1>
<p>If
your business relies on an open source project, employing, contracting with,
or
otherwise financially supporting
contributors to the project is the
mos [...]
</item>
<item>
<title>Financial Sponsorship of Open Source</title>
<link>https://community.apache.org/companies/sponsor.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/companies/sponsor.html</guid>
- <description><h1 id="financial-sponsorship">Financial
Sponsorship <a class="headerlink" title="Permalink"
href="#financial-sponsorship">&para;</a></h1>
<p>The
sustainability of our projects relies on consistent funding
for
infrastructure, legal services, marketing, events, and many
other
expenses. Financial sponsorship is a direct way to participate
in
keeping the lights on.</p>
<h2 id=&# [...]
+ <description><h1 id="financial-sponsorship">Financial
Sponsorship <a class="headerlink" title="Permalink"
href="#financial-sponsorship">&para;</a></h1>
<p>Financial
sponsorship is a direct way to invest in the <a
href="https://community.apache.org/companies/benefits.html#ecosystem-health-as-business-continuity">business
continuity</a>
of
projects your company depends on, while gaining [...]
</item>
<item>
<title>Funding campaign disclaimer</title>
@@ -670,7 +670,7 @@
<link>https://community.apache.org/companies/advocacy.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/companies/advocacy.html</guid>
- <description><h1 id="open-source-advocacy">Open Source
Advocacy <a class="headerlink" title="Permalink"
href="#open-source-advocacy">&para;</a></h1>
<p>Since
the earliest days of the Apache Software Foundation, companies
have built
their business and reputation around ASF projects, and we
have always
encouraged that. We, in turn, depends on the good will of
companies. How
companies speak about ASF pro [...]
+ <description><h1 id="open-source-advocacy">Open Source
Advocacy <a class="headerlink" title="Permalink"
href="#open-source-advocacy">&para;</a></h1>
<p>How
your company talks about ASF projects directly affects how willing
those
communities are to work with you. Companies that speak
respectfully about
open source projects — giving credit to the
community, and respecting
project brands — <a href= [...]
</item>
<item>
<title>Pilot Mentoring Programme with India ICFOSS</title>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 8e5807f5..08221f9f 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -174,7 +174,7 @@
<lastmod>2025-12-02T15:09:51+00:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/advocacy.html</loc>
- <lastmod>2026-01-16T11:04:33-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/board/overview.html</loc>
<lastmod>2024-02-15T18:53:00-05:00</lastmod>
@@ -228,10 +228,10 @@
<lastmod>2026-06-09T11:35:42-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/benefits.html</loc>
- <lastmod>2026-01-16T11:04:33-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/companies/benefits.html</loc>
- <lastmod>2026-01-16T11:04:33-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/board.html</loc>
<lastmod>2026-06-09T11:35:42-04:00</lastmod>
@@ -243,13 +243,13 @@
<lastmod>2024-02-15T18:53:00-05:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/branding.html</loc>
- <lastmod>2026-01-16T11:04:33-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/business.html</loc>
<lastmod>2026-06-09T14:18:52-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/business-value.html</loc>
- <lastmod>2026-01-16T11:04:33-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/chair.html</loc>
<lastmod>2025-07-29T10:25:42-04:00</lastmod>
@@ -318,7 +318,7 @@
<lastmod>2026-06-09T11:35:42-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/contributors.html</loc>
- <lastmod>2026-01-16T13:32:27-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/crowdfunding.html</loc>
<lastmod>2023-06-22T10:30:52+02:00</lastmod>
@@ -333,10 +333,10 @@
<lastmod>2026-04-10T23:18:25+01:00</lastmod>
</url><url>
<loc>https://community.apache.org/companies/employ.html</loc>
- <lastmod>2026-01-16T13:32:27-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/employment.html</loc>
- <lastmod>2026-01-16T13:32:27-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/etiquette.html</loc>
<lastmod>2026-02-01T09:26:38+00:00</lastmod>
@@ -345,10 +345,10 @@
<lastmod>2026-06-09T14:18:52-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/companies/sponsor.html</loc>
- <lastmod>2026-01-16T11:04:33-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/funding.html</loc>
- <lastmod>2026-01-16T11:04:33-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/committers/funding-disclaimer.html</loc>
<lastmod>2023-06-22T10:30:52+02:00</lastmod>
@@ -468,7 +468,7 @@
<lastmod>2026-06-09T11:35:42-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/companies/advocacy.html</loc>
- <lastmod>2026-01-16T11:04:33-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/patch.html</loc>
<lastmod>2023-04-27T11:08:26+02:00</lastmod>
@@ -513,7 +513,7 @@
<lastmod>2026-06-09T14:18:52-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/tags/sponsorship.html</loc>
- <lastmod>2026-01-16T11:04:33-05:00</lastmod>
+ <lastmod>2026-06-09T14:13:03-04:00</lastmod>
</url><url>
<loc>https://community.apache.org/gsoc/use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html</loc>
<lastmod>2024-01-28T08:18:39+05:30</lastmod>
