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


##########
source/companies/benefits.md:
##########
@@ -0,0 +1,65 @@
+---
+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.

Review Comment:
   > But companies can directly influence the direction of a project.
   
   I am not saying it's different. Quite the contrary. I am even proposing to 
explain how (by aligining incentives). What I am really telling that "influence 
the project" is ambiguous. And can be understood differently. There are quite a 
few projects that have more influence than what we want - maybe because we 
leave the "influence" up for interpretation. I think it should be clear that 
"people" have decision making power, where their decisions might be subject to 
having aligned incentives.
   
   That leaves explicitly power for the people to decide, where companies might 
only do everything to make people incentivised, but not telling them what to 
do. I think being explicit is better than implicit here. Having explicit 
statement about it so that those people can simply send links to their 
employees - "look I am just following what ASF expects, and my decision is 
different than what you asked me to do" is very powerful for the individuals.
   
   If we leave it as "influence", then the manager will be entitled to say "but 
ASF wrote that I can have influence, so they want you to follow what I tell 
you". 
   
   I think It's a chance to not be vague about it. But be very clear that we 
expect employees who contribute to ASF to make their own decisions. Just 
stating it at the page where we say "companies can have influence" does not 
seem a bad idea I think?



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