<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 folks,
<div class=""><br class="">
</div>
<div class="">For those who aren’t also subscribed to the Information Maintainers list, please note our monthly community call coming up this Friday on exactly this topic – doing our best to make sure our lives don’t hinge on a single person in Nebraska!</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><b class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">This month our guest speaker will be Ross Spencer, who will be joining us to discuss working within and maintaining decentralized, small-group systems and development infrastructures
in different organizational and national contexts. </b><span class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Ross has a ten year background in digital preservation, and an off, and now on-again relationship with professional software development.
Having spent the last decade putting together bespoke tooling (all open source) for Archives New Zealand, and The National Archives, UK, in pursuit of looking after the archival record. Ross now works for Artefactual Systems Inc. applying some of the knowledge
gained in that time to the open source Archivematica system and the various Artefactual clients. Ross now resides in Canada and has a keen interest in staying indoors (but is looking forward to being able to go out again soon along with everybody else). You
can find out more about Ross' work via the various links on his blog </span><a href="http://exponentialdecay.co.uk/blog" target="_blank" data-saferedirecturl="https://www.google.com/url?q=http://exponentialdecay.co.uk/blog&source=gmail&ust=1597239981543000&usg=AFQjCNFa97Y0IgusuFNo586ofa4dS82Gpg" class="">http://exponentialdecay.co.uk/<wbr class="">blog</a><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""></span>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class="">
</div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<div class="" style="margin-left: 40px;"><span class="gmail-JtukPc">August 21st at 8am PST / 9am MST / 10am CST / 11am EST / 3pm GMT<br class="">
</span></div>
<div class="" style="margin-left: 40px;"><span class="gmail-JtukPc">Description:<a href="https://www.google.com/url?q=https://us02web.zoom.us/j/81790200032&sa=D&source=calendar&usd=2&usg=AOvVaw1Xo3DYCcBKboYWFdxMc0_n" target="_blank" class="">https://us02web.zoom.us/j/81790200032</a> Meeting
ID: 817 9020 0032 One tap mobile +13462487799,,81790200032# US (Houston) +12532158782,,81790200032# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 9128 US (San Jose) +1 312 626 6799 US (Chicago) +1 646
558 8656 US (New York) +1 301 715 8592 US (Germantown) Meeting ID: 817 9020 0032 Find your local number: <a href="https://us02web.zoom.us/u/kbpYZXJhKu" class="">https://us02web.zoom.us/u/kbpYZXJhKu</a></span></div>
<div class="" style="margin-left: 40px;"><br class="">
</div>
<span class="">My best,</span></div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span class="">Jordan</span></div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span class="">Information Maintainers Community Co-Facilitator</span></div>
<span class="">
<div class="">---<br class="">
Jordan Hale (they/them/theirs)<br class="">
Digital Repositories Librarian, University of Waterloo<br class="">
<a href="mailto:jordan.hale@uwaterloo.ca" class="">jordan.hale@uwaterloo.ca</a><br class="">
519 888 4567 x40135<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
</div>
</span>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Aug 19, 2020, at 10:37 AM, Edward Summers <<a href="mailto:ehs@POBOX.COM" class="">ehs@POBOX.COM</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class=""><br class="">
<blockquote type="cite" class="">On Aug 18, 2020, at 9:59 PM, Sims, Benjamin Hayden <<a href="mailto:bsims@lanl.gov" class="">bsims@lanl.gov</a>> wrote:<br class="">
Related to Andy’s point, not a lot of modern infrastructures have embraced layers of abstraction as enthusiastically as computing has. The idea behind layers of abstraction is to hide complexity behind simpler interfaces, which makes it possible to think of
software as a “stack” of components (and consequently as a Jenga-like construct as depicted in the cartoon). So part of me wants to say that weird dependencies might be better hidden, and hence more surprising, in software. But on the other hand there are
plenty of examples of hidden dependencies in old-school infrastructure. I’m not sure they follow the same stack-like structure though, so the cartoon might look a little different. I’m curious if any of the software developers/maintainers on the list have
some perspective on this. <br class="">
</blockquote>
<br class="">
Actually, in some ways I think dependencies are *more* legible in software than they usually are in "old-school" infrastructures. From makefiles to pom.xml to package.json, software builds need to explicitly list these dependencies, and the dependencies tend
to be actionable. I feel like these lists are largely understudied from an infrastructure perspective--but I'd love to be corrected if people know of some research.<br class="">
<br class="">
Also, i'd be interested to hear if people have found there to be "real world" or non-computational equivalents to these dependency lists for the research, for example accounting ledgers, supply chain data, etc?<br class="">
<br class="">
//Ed<br class="">
_______________________________________________<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>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>