Skip to content

Commit 887577f

Browse files
authored
Merge pull request #216 from apache/rbowen-company-involvement
Best practice for companies around ASF projects
2 parents d094c4c + 5dae375 commit 887577f

8 files changed

Lines changed: 443 additions & 0 deletions

File tree

source/companies/_index.md

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
title: Companies and Open Source
3+
url: /companies/
4+
tags: ["companies", "business", "navigation"]
5+
---
6+
7+
# Why Your Company Should Participate in ASF Projects
8+
9+
All modern digital infrastructure is dependent on open source software,
10+
and **ASF projects are everywhere**.
11+
Companies must think strategically about how they will engage with the
12+
open source projects on which they rely in order to ensure
13+
sustainability, and **influence the direction of these projects** for the
14+
benefit of their customers.
15+
16+
## [Benefits to Companies](/companies/benefits.html)
17+
18+
Active participation in open source projects provides significant
19+
strategic and operational benefits to companies, including talent
20+
acquisition, influence over industry standards, strong company
21+
partnerships, and greater customer trust.<br />
22+
[[Read more ...](/companies/benefits.html)]
23+
24+
## Ways to Contribute
25+
26+
There are three primary ways that companies can engage with ASF
27+
projects. Each has costs and benefits that should be carefully
28+
considered.
29+
30+
<div class="row">
31+
<!-- Employ -->
32+
<div class="col-md-4">
33+
34+
### [Employ Contributors](/companies/employ.html)
35+
36+
[![employ](/images/company-employ.jpg)](/companies/employ.html)
37+
38+
Support ASF projects by employing, or otherwise financially supporting, developers, and other professionals,
39+
who contribute directly to projects.<br />
40+
[[Read more ...](/companies/employ.html)]
41+
</div><!-- End Employ -->
42+
43+
<div class="col-md-4">
44+
<!-- Sponsor -->
45+
46+
### [Financial Sponsorship](/companies/sponsor.html)
47+
48+
[![sponsor](/images/company-sponsor.jpg)](/companies/sponsor.html)
49+
50+
Sponsor the ASF, the Community Over Code conference, project events,
51+
and local meetups.<br />
52+
[[Read more ...](/companies/sponsor.html)]
53+
54+
</div> <!-- End Sponsor -->
55+
56+
<!-- Advocacy-->
57+
<div class="col-md-4">
58+
59+
### [Advocacy](/companies/advocacy.html)
60+
61+
[![advocacy](/images/company-advocacy.jpg)](/companies/advocacy.html)
62+
63+
Companies can advocate for ASF project adoption both publicly and with
64+
their customers, while appropriately using open source project brands.<br />
65+
[[Read more ...](/companies/advocacy.html)]
66+
</div> <!-- End Advocacy-->
67+
</div> <!-- End Row -->
68+
69+
*The Apache Software Foundation welcomes corporate participation that aligns with our mission of providing software for the public good.*

source/companies/advocacy.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: Open Source Advocacy
3+
url: /companies/advocacy.html
4+
tags: ["companies", "advocacy", "branding"]
5+
---
6+
7+
# Open Source Advocacy
8+
9+
Since the earliest days of the Apache Software Foundation, companies
10+
have built their business and reputation around ASF projects, and we
11+
have always encouraged that. We, in turn, depends on the good will of
12+
companies. How companies speak about ASF projects is a critical part of
13+
our public image.
14+
15+
## Respect Our Brands
16+
17+
Like any organization, the ASF has [Trademark
18+
Policy](https://www.apache.org/foundation/marks/) which describes
19+
appropriate and inappropriate ways to use the brand of the ASF, and of
20+
ASF projects. We expect companies to familiarize themselves with these
21+
policies, just as they would when working with another company or
22+
partner.
23+
24+
## Be Proactive About Education
25+
26+
Be sure that anyone speaking on behalf of your company understands
27+
and respects the [ASF Trademark
28+
Policy](https://www.apache.org/foundation/marks/). Most violations of
29+
these policies have historically come from company spokespeople who do
30+
not understand the nature of the ASF, or of open source software, and
31+
speak of our projects like just another of your company's products.
32+
33+
Be proactive about educating these individuals about appropriate ways to
34+
speak about these projects. Use this website as a reference, and
35+
encourage them to talk directly to projects if they have any questions
36+
about how best to represent your work in and around these communities.
37+
38+
## Community First
39+
40+
When you mention ASF projects, we ask that you put the community first.
41+
It's great to celebrate what your company and employees are doing in and
42+
around ASF projects - we welcome and encourage that! - but be sure to
43+
give credit where it's due. The community as a whole makes our projects
44+
work, and contributes to your success.
45+
46+
Some companies make claims about their involvement in ASF projects that
47+
imply that they own the project, or are primarily responsible for it.
48+
Phrases like "creators of ..." or "primary contributors to ..." devalue
49+
the work that the rest of the community does, and unfairly take credit
50+
for the work that others have done to contribute to your success. We ask
51+
that you not do that.
52+
53+

source/companies/benefits.md

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: Benefits of Open Source Participation
3+
url: /companies/benefits.html
4+
tags: ["companies", "benefits", "business value"]
5+
---
6+
7+
# Benefits of ASF Participation
8+
9+
Companies that actively participate in ASF projects realize significant
10+
strategic and operational advantages that extend far beyond cost savings.
11+
It's important to think strategically about how, where, and why you will
12+
participate and measure impact.
13+
14+
## Influence the Roadmap
15+
16+
While it can sometimes take months, or years, to gain expertise and
17+
trust in an established community, showing up to do the daily
18+
project maintenance -- issue and PR triage; reviewing PRs; planning and
19+
executing community events; answering user questions -- you'll quickly
20+
begin to establish that you can be trusted, which will make it easier
21+
for you to influence the direction of the project.
22+
23+
Decisions about the direction of Apache projects are made by the people
24+
who show up to participate in the conversation. If you don't join the
25+
conversation, then your competitors will decide how tomorrow's
26+
technology will shape up.
27+
28+
Make sure someone on your team is reading the project [mailing
29+
lists](https://www.apache.org/foundation/mailinglists.html) every day,
30+
and advocating for your priorities. That's what community means --
31+
showing up to own the future of the project.
32+
33+
While trust does not necessarily transfer to other employees, over time,
34+
as project participants see your company actively contributing to the
35+
project, and demonstrating ownership, they'll be more willing to work
36+
with you.
37+
38+
## Recruiting
39+
40+
By working upstream on projects, you directly showcase to potential
41+
employees what they might be working on. This helps attract the right
42+
kind of talent to work on your priorities, and they'll begin to see your
43+
company as a partner in the project, and an attractive place to work.
44+
45+
Being involved in the day-to-day life of the project
46+
gives you direct access to the most qualified people in the world to
47+
work on your team. And you know they'll be arriving with the skills you
48+
need.
49+
50+
## Business and Strategic Advantages
51+
52+
For more than 25 years, the ASF has been a place where industry
53+
standards have been set and implemented. Collaborating in those
54+
projects is the most effective way to shape industry standards and best
55+
practices. You'll be building trust with current and potential
56+
customers, and building strategic partnerships with other companies
57+
working in the same space.
58+
59+
And by collaborating with your peers on the common tasks, you'll be able
60+
to better focus on your unique business differentiators.
61+
Collaborate on what all share; Compete where you excel.
62+
63+
*The benefits of open source participation compound over time, creating
64+
sustainable competitive advantages and fostering innovation that drives
65+
long-term business success.*

0 commit comments

Comments
 (0)