<div dir="ltr">v</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Aug 23, 2020 at 2:24 PM jan <<a href="mailto:dittrich.c.jan@gmail.com">dittrich.c.jan@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Hello Maintainers, <br>
</p>
<p>TL;DR: How are people socialized to continue to maintain (open
source software)?</p>
<p>I wonder if you know any studies that analyze what makes
developers continue to maintain a piece of code, often without
pay. A lot of open source culture celebrates (libertarian)
freedom, creating new solutions and avoiding obligations (at least
according to Nafus, 2011 [1] ). Code/Software is provided "as is",
so there is no written social or (or even legal) contract to NOT
leave a project, yet people seem to go through a lot of pain to
maintain old code or adapt old code to changing infrastructure. I
thus wonder how and why they continue to maintain in the face that
a lot of the openly celebrated activities are somewhere else. <br>
</p>
<p>Jan</p>
<p>[1]: ‘Patches don’t have gender’: What is not open in open source
software, Dawn Nafus, 2011
<a href="http://journals.sagepub.com/doi/10.1177/1461444811422887" target="_blank">http://journals.sagepub.com/doi/10.1177/1461444811422887</a></p>
</div>
_______________________________________________<br>
Themaintainers mailing list<br>
<a href="mailto:Themaintainers@lists.stevens.edu" target="_blank">Themaintainers@lists.stevens.edu</a><br>
<a href="https://lists.stevens.edu/mailman/listinfo/themaintainers" rel="noreferrer" target="_blank">https://lists.stevens.edu/mailman/listinfo/themaintainers</a><br>
</blockquote></div>