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


##########
source/companies/employ.md:
##########
@@ -0,0 +1,191 @@
+---
+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, 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](/companies/benefits.html#recruiting-and-employee-satisfaction))
+
+This goes [far beyond code contributions](/contributors/non-code.html), 
+although that is the most obvious and visible way that you can participate.
+

Review Comment:
   Or - again let me repeat it - you might look for getting a maintainer on 
another type of contract, not employment.
   
   For many companies, this is often a decision to make (and there is a 
significant difference):
   
   * employ peipole
   * contract with external people (software houses for example, or individual 
consultants)
   
   This has very different properties - starting from non-compete (mentioned), 
going through much more flexible part-time or even hourly-based or task-based 
contract models. 
   
   In case of contracting non-employees - for example - companies might even 
use 3rd-parties (such as Tidelift, HeroDev and many similar) to setup those 
relationships - and this is **not** employment - in very strict legal sense of 
it. And it actually might help to solve the "how do companies find those 
people" - because they can do that through those third parties (and many 
already do).
   
   Employment has very concrete definition and a lot of limitations - other 
forms of contract can be much more flexible. 
   
   I would strongly advocate for making it clear that "employment" is not the 
only way companies might make maintainers get money - and I am not really sure 
why this seems to be a controversial thing to add those form of contracts 
explicitly (it seems pretty obvious - both, that is happening already and that 
is very distinct from employment).
   
   



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