<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hi all,
<div class=""><br class="">
</div>
<div class="">This conversation is timely, as I saw a new thesis title awaiting approval in the collection I maintain as I read these emails. Now that it has been published, I’d like to share S. Alex Yun’s MMath thesis, <a href="http://hdl.handle.net/10012/16195" class="">Personality
Traits of GitHub Maintainers and Their Effects on Project Success</a>, with their permission, as well as <a href="https://doi.org/10.1109/TSE.2019.2960357" class="">a related IEEE Transactions on Software Engineering proceeding</a>.</div>
<div class=""><br class="">
</div>
<div class="">Jordan<br class="">
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class="">
<div class="">---</div>
<div class="">Jordan Hale (they/them/theirs)</div>
<div class="">Digital Repositories Librarian, University of Waterloo</div>
<div class=""><a href="mailto:jordan.hale@uwaterloo.ca" class="">jordan.hale@uwaterloo.ca</a></div>
<div class="">519 888 4567 x40135</div>
</div>
<div class=""><br class="">
</div>
</div>
<br class="Apple-interchange-newline">
</div>
<br class="Apple-interchange-newline">
<br class="Apple-interchange-newline">
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Aug 27, 2020, at 10:45 AM, Stephanie Beth Jordan <<a href="mailto:stephaniebeth@protonmail.com" class="">stephaniebeth@protonmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class=""><br class="">
</div>
<div class="">Echo! </div>
<div class=""><br class="">
</div>
<div class="">And thank you all for this fantastic thread.</div>
<div class=""><br class="">
</div>
<div class="">This discussion of fairness resonates with my field experience of sensor networks in the climate and ocean sciences (which importantly supports maintenance positions through continued investment from the National Science Foundation and other entrepreneurial
interests, a factor that makes it distinct from open source communities). For my field, a prominent reality for those that have left that may fall under this rubric of fairness is: overt gender inequity and, for some, cases of sexual violence. These realities
draw attention to the intersectional oppressions<caret class=""></caret> faced by maintainers, both those who stay and those who decide to "stop".</div>
<div class=""><br class="">
</div>
<div class="">Thank you for sharing this incredibly rich work with us, Atul! I look forward to engaging more and continued conversations.</div>
<div class=""><br class="">
</div>
<div class="">Warmly,</div>
<div class="">Steph</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Department of Media and Information</div>
<div class="">Center for Gender in a Global Context</div>
<div class="">Michigan State University</div>
<div class=""><a href="http://stephaniebethjordan.com" class="">stephaniebethjordan.com</a></div>
<div class="">
<div id="protonmail_signature_block" class="protonmail_signature_block">
<div class=""></div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div id="protonmail_mobile_signature_block" class="">
<div class="">Sent from ProtonMail Mobile</div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
On Thu, Aug 27, 2020 at 9:54 AM, James Howison <<a href="mailto:jhowison@ischool.utexas.edu" class="">jhowison@ischool.utexas.edu</a>> wrote:
<blockquote class="protonmail_quote" type="cite">
<div dir="ltr" class="">Bravo!
<div class=""><br clear="all" class="">
<div class="">
<div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">James Howison
<div class=""><br class="">
<div class="">Associate Professor</div>
<div class="">School of Information</div>
<div class="">University of Texas at Austin</div>
<div class=""><a href="http://james.howison.name/" class="">http://james.howison.name</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br class="">
</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Aug 27, 2020 at 5:09 AM Atul Pokharel <<a href="mailto:atulpokh@gmail.com" class="">atulpokh@gmail.com</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="">Hi Maintainers,<br class="">
</div>
<div class=""> I've been spending a lot of time (since about 2013) thinking about why people *stop* maintaining shared infrastructure (thanks for the shoutout Andy). Jan, I'd love to talk to you more about how your motivations evolved. I'd also love to learn
from any other maintainers about how their motivations changed (It doesn't have to be software). If you'd be willing to talk, please drop me a line. The gist of my approach is the observation that the negative reasons - why people stop - seem to be more helpful
for understanding the moral reasons underlying maintenance than the positive reasons - why people continue. These reasons can be different because motivations evolve, people learn, maintenance becomes onerous etc.<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">In relation to some of the comments in this thread, I am fairly well versed in the Ostromian approach to shared resources (Governing the Commons, 1990 and a ton of other works). This falls in the "law and economics approach" that Christopher mentioned
above. It is a very common way to analyze free and open source software, particularly when the objective is to come up with metrics for characterizing the projects themselves or to compare different cases. It is also, a very common way of studying natural
resource commons (like forests), physical infrastructure commons (like irrigation systems), and digital infrastructure (like open source software). Some years ago, there was also a big push to try to derive a policy framework for governing the "knowledge
commons" (<a href="http://knowledge-commons.net/gkc/" class="">http://knowledge-commons.net/gkc/</a>) using this approach.
<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Theoretically, a major weakness of this framework is that it conflates initial cooperation (required to build something) with sustained cooperation (required to maintain something). This is largely because of the underlying model of human beings
that it uses (whose motivations for not doing something are assumed to be the exact opposite of the reasons for doing something) but that is another story. There are other key distinctions that these economic frameworks (largely) fail to make: that between
fairness and cooperation (it assumes that if people are cooperating, they think it is fair), that between initital motivations and subsequent motivations (assumes that everyone is isolated) and that between natural resources and infrastructure (assumes that
maintenance means essentially the same thing in both cases). <br class="">
</div>
And practically, very little of the evidence underlying these frameworks follows the same cases over time. It is more likely to look at snapshots across many resources at a point in time.
<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">If you are into doing some research in this area, I am happy to help however is most useful to you. I am also currently working on a project (to submit for the Ford/Sloan grant) to study what fairness means in open source projects, and whether
we can come up with indicators of fairness to throw in the bag of considerations for assessing the health of projects, what can be done to help, etc.. It would be awesome to work together.
</div>
<div class=""> <br class="">
</div>
<div class="">In my own studies so far of decades old farmer managed irrigation systems, I found that people's motivations evolved so that moral motivations became more salient (I followed the same cases over three decades). In particular, a major reason why
people stopped was that they came to perceive their system as unfair. I also found that reasons for stopping maintenance were far more likely to concern moral elements while reasons for initiating cooperation were some mix of personal pleasure, gain, promise,
etc. Hence the early comparison of reasons people stopped maintaining (<a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2802653" class="">https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2802653</a>) . There are a lot of questions here around
what fairness means in the context of maintenance, how it changes, whether user governed irrigation systems are comparable to modern infrastructure (yes, surprisingly so), and what frameworks we should use to understand these moral motivations underlying
maintenance. I am currently working on a book that presents one possibility (working title: Fairness and Cooperation). It is encouraging to see that the observations it is based on might not be completely wrong.
<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">I am still really curious though how these lessons from many thousands of years of physical infrastructure governance translate into our new digital world and the other way around...</div>
<div class=""><br class="">
</div>
<div class="">thanks,<br class="">
</div>
<div class="">-atul <br class="">
</div>
<div class=""> <br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Aug 25, 2020 at 1:21 PM Bruce Caron <<a href="mailto:bruce@nmri.org" class="">bruce@nmri.org</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div dir="ltr" class="">Prof. Neera Singh at U Toronto is working on the role of emotional commitment (affect) as a feature of commoning, <<a href="https://geography.utoronto.ca/profiles/6318/" class="">https://geography.utoronto.ca/profiles/6318/</a>>. I
suspect her work on community forests in India might also apply to open-source software. </div>
<div dir="ltr" class=""><br class="">
</div>
<div class="">bruce caron</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Aug 23, 2020 at 12:24 PM jan <<a href="mailto:dittrich.c.jan@gmail.com" class="">dittrich.c.jan@gmail.com</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="">
<p class="">Hello Maintainers, <br class="">
</p>
<p class="">TL;DR: How are people socialized to continue to maintain (open source software)?</p>
<p class="">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 class="">
</p>
<p class="">Jan</p>
<p class="">[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" class="">http://journals.sagepub.com/doi/10.1177/1461444811422887</a></p>
</div>
_______________________________________________<br class="">
Themaintainers mailing list<br class="">
<a href="mailto:Themaintainers@lists.stevens.edu" class="">Themaintainers@lists.stevens.edu</a><br class="">
<a href="https://lists.stevens.edu/mailman/listinfo/themaintainers" rel="noreferrer" class="">https://lists.stevens.edu/mailman/listinfo/themaintainers</a><br class="">
</blockquote>
</div>
<br clear="all" class="">
<div class=""><br class="">
</div>
-- <br class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">Bruce Caron, PhD<br class="">
Executive Director<br class="">
New Media Studio<br class="">
Santa Barbara, CA USA<br class="">
<a href="http://www.nmri.org/" class="">http://www.nmri.org</a><br class="">
<a href="http://cybersocialstructure.org/" class="">http://cybersocialstructure.org/</a><br class="">
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
Themaintainers mailing list<br class="">
<a href="mailto:Themaintainers@lists.stevens.edu" class="">Themaintainers@lists.stevens.edu</a><br class="">
<a href="https://lists.stevens.edu/mailman/listinfo/themaintainers" rel="noreferrer" class="">https://lists.stevens.edu/mailman/listinfo/themaintainers</a><br class="">
</blockquote>
</div>
</div>
_______________________________________________<br class="">
Themaintainers mailing list<br class="">
<a href="mailto:Themaintainers@lists.stevens.edu" class="">Themaintainers@lists.stevens.edu</a><br class="">
<a href="https://lists.stevens.edu/mailman/listinfo/themaintainers" rel="noreferrer" class="">https://lists.stevens.edu/mailman/listinfo/themaintainers</a><br class="">
>> This message is from an external sender. Learn more about why this <<<br class="">
>> matters at <a href="https://links.utexas.edu/rtyclf" rel="noreferrer" class="">
https://links.utexas.edu/rtyclf</a>. <<<br class="">
</blockquote>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
_______________________________________________<br class="">
Themaintainers mailing list<br class="">
<a href="mailto:Themaintainers@lists.stevens.edu" class="">Themaintainers@lists.stevens.edu</a><br class="">
https://lists.stevens.edu/mailman/listinfo/themaintainers<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>