Miroirs/cooperative-software-development
1
0
Fork 0
mirror of https://github.com/amyjko/cooperative-software-development synced 2024-12-25 21:58:15 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fixed #54, citing OSS funding.

Browse source
This commit is contained in:
Amy J. Ko 2020-08-14 10:18:24 -07:00
parent fc4ba0b948
commit 14bc7713f5
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
organizations.html
View file

@ -68,6 +68,7 @@
Others like Linux <a href="#lee">(Lee & Cole 2013)</a> rely heavily on contributions both from volunteers <a href="#ye">(Ye & Kishida 2003)</a>, but also paid employees from companies that depend on Linux, like IBM, Google, and others.
In these settings, there are still all of the challenges that come with software engineering, but fewer of the constraints that come from a for-profit or non-profit motive.
In fact, recent work empirically uncovered 9 reasons why modern open source projects fail: 1) lost to competition, 2) made obsolete by technology advances, 3) lack of time to volunteer, 4) lack of interest by contributors, 5) outdated technologies, 6) poor maintainability, 7) interpersonal conflicts amongst developers, 8) legal challenges, 9) and acquisition (<a href="#coelho">Coelho and Valente 2017</a>).
Another study showed that funding open source projects often requires substantial donations from large corporations; most projects don't ask for donations, and those that do receive very little, unless well-established, and most of those funds go to paying for basic expenses such as engineering salaries (<a href="overney">Overney 2020</a>)
Those aren't too different from traditional software organizations, aside from the added challenges of sustaining a volunteer workforce.
</p>
@ -105,6 +106,8 @@
<p id="li">Li, Paul, Ko, Amy J., and Begel, Andrew (2017). <a href ="https://doi.org/10.1109/CHASE.2017.3">Collaborating with Software Engineers: Perspectives from Non-Software Experts.</a> In the Proceedings of the 10th International Workshop on Cooperative and Human Aspects of Software Engineering.</p>
<p id="osterwalder">A. Osterwalder, Y. Pigneur, G. Bernarda, & A. Smith (2015). <a href="https://books.google.com/books?id=jgu5BAAAQBAJ" target="_blank">Value proposition design: how to create products and services customers want</a>. John Wiley & Sons.</p>
<p id="overney">Overney, C., Meinicke, J., Kästner, C., & Vasilescu, B. (2020). <a href="https://cmustrudel.github.io/papers/overney20donations.pdf">How to Not Get Rich: An Empirical Study of Donations in Open Source</a>. International Conference on Software Engineering.</p>
<p>Somers, James (2017). <a href="https://www.theatlantic.com/technology/archive/2017/09/saving-the-world-from-code/540393/">The Coming Software Apocalypse</a>. The Atlantic Monthly.</p>