potiuk commented on code in PR #216:
URL: https://github.com/apache/comdev-site/pull/216#discussion_r2658477905


##########
source/companies/_index.md:
##########
@@ -0,0 +1,69 @@
+---
+title: Companies and Open Source
+url: /companies/
+tags: ["companies", "business", "navigation"]
+---
+
+# Why your company should participate in ASF projects
+
+All modern digital infrastructure is dependent on open source software,
+and **ASF projects are everywhere**.
+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, including talent
+acquisition, influence over industry standards, strong company
+partnerships, and greater customer trust.<br />
+[[Read more ...](/companies/benefits.html)]
+
+## Ways to contribute
+
+There are three primary ways that companies can engage with ASF
+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)

Review Comment:
   > 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 
have (see my "aligining incentives" proposal). 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to