Skip to content
Draft
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 61 additions & 0 deletions source/companies/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
---
title: Companies and Open Source
url: /companies/
tags: ["companies", "business", "navigation"]
---

# Companies and Open Source

All modern digital infrastructure is dependent on open source software.
Companies must think strategically about how they will engage with the
open source projects on which they rely in order to ensure
sustainability, and influence the direction of these projects for the
benefit of their customers.

## [Benefits to Companies](/companies/benefits.html)

Active participation in open source projects provides significant strategic and operational benefits to companies, from talent acquisition to technology innovation and market positioning.


## Ways to contribute

There are three primary ways that companies can engage with ASF
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
There are three primary ways that companies can engage with ASF
There are several primary ways that companies can engage with ASF

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fall victim of that far too often - specifying a number of things listed below is just very prone to get wrong when the list grows or shrinks.

projects. Each has costs and benefits that should be carefully
considered.

<div class="row">
<!-- Employ -->
<div class="col-md-4">

### [Employ Contributors](/companies/employ.html)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would love to see a different title used here as employing contributors directly has many issues.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps this is a "Sponsor Individuals" and the next one is "Sponsor Projects"

Copy link
Member

@potiuk potiuk Jan 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would love to see a different title used here as employing contributors directly has many issues.

I do think we should mention employment as one of the options (contracting and sponsoring individuals as well) - becaue it's the fact and even welcome that many contributors, committers, PMC members are employees. This is a good thing - for example one that allows Airflow to thrive (amongst other things). But I think we should just be explicit about boundaries of the influence - this is what I wanted to clarify how much influence companies might expect (see my "aligining incentives" proposal).


[![employ](/images/company-employ.jpg)](/companies/employ.html)

The most impactful way companies support open source is by employing developers and other professionals who contribute to projects. This includes not just code contributions, but documentation, community management, testing, design, and advocacy work.
</div><!-- End Employ -->


<div class="col-md-4">
<!-- Sponsor -->

### [Financial Sponsorship](/companies/sponsor.html)

[![sponsor](/images/company-sponsor.jpg)](/companies/sponsor.html)

Companies can provide crucial financial support through ASF sponsorship, in-kind donation of services, Community Over Code conference sponsorship, local meetup support, and direct contributor sponsorship programs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I know that "direct contributor sponsorship" is here, but I think it's a very different thing for both contributors and companies, and it deserves a separate entry, because it introduces "maintainership" concept. Companies do not understand that OSS project need "maintenance". They only think in terms of "bugs" and "features". But "maintainership" is so much more and different than that and we need to be very precise - I think - on educating companies that it exists - not as the last point in the "Sponsor" part - especially that "supporting maintainers" is very different from "sponsoring".


</div> <!-- End Sponsor -->

<!-- Advocacy-->
<div class="col-md-4">

### [Advocacy](/companies/advocacy.html)

[![advocacy](/images/company-advocacy.jpg)](/companies/advocacy.html)

Companies can advocate for open source adoption both publicly and with their customers, while appropriately using open source project brands and promoting the value of community-driven development.
</div> <!-- End Advocacy-->
</div> <!-- End Row -->
---

*The Apache Software Foundation welcomes corporate participation that aligns with our mission of providing software for the public good.*
20 changes: 20 additions & 0 deletions source/companies/advocacy.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
title: Open Source Advocacy
url: /companies/advocacy.html
tags: ["companies", "advocacy", "branding"]
---

# Open Source Advocacy

Advocating for ASF projects, while respecting the project's independence
and honoring the project's brands, can significantly drive adoption of
the project, which can advance your own company's business

While it's fine to associate your company's name and reputation with an
ASF project, you must do it in ways that don't confuse or mislead the
public about the project's independence.

Be sure your marketing department understands and respects the [ASF Trademark
Policy](https://www.apache.org/foundation/marks/).


111 changes: 111 additions & 0 deletions source/companies/benefits.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,111 @@
---
title: Benefits of Open Source Participation
url: /companies/benefits.html
tags: ["companies", "benefits", "business value"]
---

# 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. It can be challenging to justify these benefits to management, as many of them are long-term. And these benefits will vary greatly depending on the nature of your business.

Copy link
Member

@potiuk potiuk Dec 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a suggestion

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I moved the comments here. The first chapter is somewhat discouraging about the "short-term" gains, so I think it's worth to mention specific "short-term" gains the companies can have by establishing relationship with maintainers.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think some of those are listed below *establishing relationships" - but those are a bit "slogans" and if someone reads it, I think it should be clear what is the actual "gain" they have. I believe the first chapnter is the one that wil be read by somoene in the companies - to make quick decisions, the "details" below are nice but they do not show "what do I have" - for example "establishing relationship" does not ring "I save money" for corporate user. While "saving weeks of work" for your team "through establishing relationships" does.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What change are you suggesting here?

Copy link
Member

@potiuk potiuk Dec 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What change are you suggesting here?

I already did -> I moved all the changes above (from _index.md) to "benefits.md" Those are the suggestions I proposed - adding two more paragraphs under the original one which focused on the "long-term" benefits. The two paragraphs I proposed are focusing more on the short-term benefits and actual ways companies migh save money in shorter term (making their teams more productive)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the proposal:

Screenshot 2025-12-29 at 22 54 29

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, personal relationships are great, if you can find them/build them. But of far greater importance is establishing connections between the project and a corporate contributor (base). This feels like you are advocating some sort of intermediary to broker such connections with projects. I can see the benefits in the short term, but this set of documents is to help companies build their own relationships using open source and community best practices.

Copy link
Member

@potiuk potiuk Jan 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel that for us (ASF) far greater benefit is to establish relationships between people - (for example employees of a company and maintainers). I do not want to introduce any intermediary, but to explain that companies can benefit for making their employees having good relationships with maintainers - even if they are not maintainers themselves. This is how it works in Airflow for example. As maintainers - we have great personal relationships with Amazon employees who contribute to Airflow, also with their management who contributes to the Airflow Summit.

And we work closely with those Amazon employees mainly because we have great relationship with them - not because they are Amazon employees. Same with Astronomer and Google.

We (PMC) vaalue Amazon, Astronomer and Google as stakeholders and we are grateful for them spending their energy and effort on Airflow. but we are not even supposed (as a PMC) to have relation with Amazon, Google or Astronomer. The best those companies can do (in relation to PMC) is to align incentives of their employees who are contributors and PMC members.

I think saying that PMC can have any "project direction" relationship directly with the companies - would be IMHO quite contradicting a lot of the "Vendor independence" in ASF. In ASF such relation should only be done through individuals who might or might not be employees, or even contractors of those companies. And I think we should be very clear about it.

This feels like you are advocating some sort of intermediary to broker such connections with projects.

Not sure what kind of intermediary we are talking about. PMC <-> individual contributor relationship is clear. PMC <> company relationship is essentially "should not happen". So if we are talking about PMC <> individual contributor <> Company relationship - the individual is intermediary. I do not see any other intermediaries here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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. It can be challenging to justify these benefits to management, as many of them are long-term. And these benefits will vary greatly depending on the nature of your business.
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. It can be challenging to justify these benefits to management, as many of them are long-term. And these benefits will vary greatly depending on the nature of your business.
However, such cooperation works in both directions and some of them are short term - when maintainers see company that is actively participating in the project, they are eager to help and solve problems that individuals from the company are raising.
Personal relationships with maintainers also makes it possible to save even weeks of going in a wrong direction in your deployments, because maintainers will know your context and will be able to help to make better decisions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, ok, I see. I think that these sentiments are reflected in the #avoid-conflicts section, and in the #attract-collaborators sections. Let me know what you think.

## Business and Strategic Advantages

### Market Positioning
- Establish thought leadership in key technology areas
- Build brand recognition and trust within developer communities
- Demonstrate commitment to industry standards and collaboration
- Influence technology direction and ecosystem development

### Customer Relationships
- Provide transparent, auditable technology solutions
- Offer customers freedom from vendor lock-in
- Build trust through community-driven development
- Enable customer participation in product evolution

### Competitive Advantage
- Shape industry standards and best practices
- Access innovations before they become mainstream
- Build strategic partnerships through community collaboration
- Reduce competitive threats through ecosystem participation

## Talent and Human Resources

### Talent Acquisition
- Access to a global pool of skilled developers
- Attract candidates who value open source contribution
- Demonstrate company culture and technical values
- Build relationships with potential hires through community work

### Employee Development
- Enhance technical skills through diverse project exposure
- Develop leadership and collaboration abilities
- Build professional networks and industry recognition
- Increase job satisfaction and retention rates

### Knowledge Transfer
- Learn from industry experts and best practices
- Stay current with emerging technologies and trends
- Develop cross-functional expertise
- Build institutional knowledge and capabilities

## Technology and Innovation

### Technical Excellence
- Access to cutting-edge technologies and innovations
- Benefit from collective problem-solving and peer review
- Reduce development time through shared components
- Improve code quality through community standards

### Risk Mitigation
- Avoid vendor lock-in and proprietary dependencies
- Ensure long-term technology sustainability
- Benefit from community security reviews and updates
- Maintain control over critical technology components

### Faster Time to Market
- Leverage existing solutions rather than building from scratch
- Focus resources on core business differentiators
- Accelerate development through community contributions
- Reduce testing and validation overhead

## Operational Benefits

### Cost Efficiency
- Share development and maintenance expenses across community
- Minimize duplicate effort through collaboration

## Long-term Strategic Value

### Ecosystem Influence
- Participate in technology roadmap decisions
- Build strategic relationships with key industry players
- Influence standards and best practices development
- Create sustainable competitive advantages

### Innovation Pipeline
- Access emerging technologies and research
- Participate in next-generation technology development
- Build capabilities for future market opportunities
- Establish innovation partnerships and collaborations

### Organizational Learning
- Develop open collaboration and transparency practices
- Build cross-functional and cross-organizational capabilities
- Enhance organizational agility and adaptability
- Create culture of continuous learning and improvement

## Measuring Success

### Quantitative Metrics
- Developer productivity and satisfaction scores
- Time to market improvements
- Cost savings and efficiency gains
- Community engagement and contribution levels

### Qualitative Indicators
- Brand recognition and industry reputation
- Employee retention and recruitment success
- Customer satisfaction and trust levels
- Innovation capacity and market responsiveness

The benefits of open source participation compound over time, creating sustainable competitive advantages and fostering innovation that drives long-term business success.
43 changes: 43 additions & 0 deletions source/companies/employ.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
---
title: Employing Open Source Contributors
url: /companies/employ.html
tags: ["companies", "employment", "contributors"]
---

# Employing Open Source Contributors

If your business relies on an open source project, employing
contributors to the project is the most effective way to ensure that
your priorities influence project decisions.

This goes [far beyond code contributions](/contributors/non-code.html),
although that is the most obvious and visible way that you can participate.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So how do companies find these people to support?

## Effective ways to contribute

### Allocate Dedicated Time
Allow employees to spend work time on open source contributions, typically 10-20% of their schedule.

### Recognize Contributions
Include open source contributions in performance reviews and career advancement considerations.

### Support Conference Participation
Fund employee attendance at relevant conferences and encourage speaking opportunities.

### Respect Project Independence
Ensure contributions align with long-term project goals rather than solely short-term company priorities.

### Long-term Commitment

Earning individual trust takes long-term participation. Trust earned by
one contributor does not necessarily rub off on your other employees.

## Getting Started

1. Identify projects your company already uses or depends on
2. Connect with existing contributors in your organization
3. Start with small, manageable contributions
4. Build relationships within project communities
5. Gradually increase involvement and responsibility

Companies that invest in employing open source contributors create a sustainable model that benefits the entire ecosystem while building internal expertise and community relationships.
26 changes: 26 additions & 0 deletions source/companies/sponsor.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
title: Financial Sponsorship of Open Source
url: /companies/sponsor.html
tags: ["companies", "sponsorship", "funding"]
---

# 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.

Companies can sponsor the ASF with an [annual
donation](https://apache.org/foundation/sponsorship.html),
[conferences sponsorship](https://communityovercode.org),
targeted donations to a particular project, or in-kind donations of
products or services.

Supporting local gatherings of open source enthusiasts is a great way to
foster community growth, and can help your company attract and retain
experts in your employ.

Learn more at [apache.org/foundation/sponsorship](https://apache.org/foundation/sponsorship.html)


Binary file added static/images/company-advocacy.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/images/company-employ.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/images/company-sponsor.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.