From 9fb6ca1c3cc4366a61b947145525f9e0dce3bd6c Mon Sep 17 00:00:00 2001
From: TinasheMTapera <15770644+TinasheMTapera@users.noreply.github.com>
Date: Mon, 15 Jun 2026 21:16:43 -0400
Subject: [PATCH 01/11] Start newsletter PR
---
_data/newsletter-events-opportunities.yml | 124 ++++-
_data/newsletter_bib.bib | 127 +++--
_data/newsletter_bib_yml.yml | 164 ++++--
_posts/newsletters/2026-06-15-newsletter.md | 526 ++++++++++++++++++++
_posts/newsletters/quarto/_headline.md | 161 +++---
_posts/newsletters/quarto/_news.md | 23 +-
_posts/newsletters/quarto/_preamble.md | 14 +-
_posts/newsletters/quarto/params.yml | 34 +-
_posts/newsletters/quarto/template.md | 377 +++++++-------
9 files changed, 1185 insertions(+), 365 deletions(-)
create mode 100644 _posts/newsletters/2026-06-15-newsletter.md
diff --git a/_data/newsletter-events-opportunities.yml b/_data/newsletter-events-opportunities.yml
index c002c74ff..a78a36a43 100644
--- a/_data/newsletter-events-opportunities.yml
+++ b/_data/newsletter-events-opportunities.yml
@@ -177,8 +177,96 @@
links: |
More information: [Click here](https://hpc-days.github.io/Durham-HPC-Days-2026/)
+- expires: 2026-06-24
+ type: event
+ title: Build Portable CPU/GPU Code in Julia with Minimal Effort
+ when: Jun 24, 2026, 11:00 AM EDT
+ where: Online
+ preamble: |
+ Join Oak Ridge National Laboratory scientists William F Godoy and Philip W Fackler for a live webinar exploring how JACC.jl enables vendor-neutral parallel computing in Julia across CPUs and GPUs.
+ High-performance computing development often requires engineers and researchers to manage multiple programming models and vendor-specific GPU frameworks. JACC.jl simplifies this process by enabling portable Julia code that runs across CPUs and GPUs from different vendors, all from a single source code base.
+ In this webinar, Oak Ridge National Laboratory experts will introduce JACC.jl and demonstrate how Julia users can build vendor-neutral parallel applications while maintaining performance and developer productivity.
+ links: |
+ Register now to discover how Julia and JACC.jl are enabling the next generation of portable high-performance computing workflows: [Click here to register](https://juliahub.com/events/build-portable-cpu-gpu-code-in-julia-with-minimal-effort)
+
+- expires: 2026-07-14
+ type: event
+ title: Levels of Software Testing Webinar
+ when: Tuesday, July 14, 12:00 PM - 1:00 PM MST
+ where: Online
+ preamble: |
+ Join us for the next webinar of the National Laboratories Sustainable Scientific Software Conference's Community of Practice, as community member Jason M. Gates gives us an introduction to different types and levels of software testing, where manual testing is appropriate, and how all this ties into your project documentation.
+ links: |
+ Click [here](https://events.gcc.teams.microsoft.com/event/0200afeb-a59c-40f3-9be9-be60e28b067c@7ccb5a20-a303-498c-b0c1-29007381b574) to register!
+
+- expires: 2026-07-24
+ type: event
+ title: PyOhio 2026
+ when: July 24-25, 2026
+ where: Online
+ preamble: |
+ PyOhio 2026 is the 19th annual Python Community Conference in Cleveland, Ohio. It will be held at Cleveland State University Student Center on July 25-26, 2026.
+ links: |
+ Details are available on the conference website: [https://www.pyohio.org/2026/](https://www.pyohio.org/2026/)
+
+
+- expires: 2026-09-22
+ type: event
+ title: LLNL HPC Webinars
+ when: Tuesday, July 14, 12:00 PM - 1:00 PM MST
+ where: Online
+ preamble: |
+ LLNL’s High Performance Computing Innovation Center is once again putting on a series of **Free, Virtual Open Source Software Tutorials**!
+
+ This July through September, you can hear it straight from the developers of these projects.
+ We’re kicking things off with Spack July 7-8, but hope to see you at all 13 tutorials!
+
+ links: |
+ Dates:
+ - July 7-8: Spack, HPC package manager
+ - July 14: BLT, build link and test HPC apps
+ - July 21: Flux, HPC scheduler and resource manager
+ - July 28: YGM, manage irregular communication
+ - Aug 4: Caliper & Thicket: measure and analyze performance data
+ - Aug 1: Axom, modeling and simulation infrastructure
+ - Aug 18: Jacamar CI: Secure Gitlab runners for HPC centers
+ - Aug 25: Ascent, in-situ visualization
+ - Sep 1: Benchpark, reproducible continuous benchmarking framework
+ - Sep 15: RAJA & Umpire, performance portability and accelerator memory management
+ - Sep 22: MFEM, scalable, higher order finite element meshing library
+
+ Sign up here: [https://hpcic.llnl.gov/tutorials/2026-hpc-tutorials](https://hpcic.llnl.gov/tutorials/2026-hpc-tutorials)
+
#-------------------
# Opportunities
+- expires: 2026-08-30
+ type: opportunity
+ title: Research Opportunity
+ preamble: |
+ Community member Ellie O'Brien recruiting participants for a study about how scientists program with agentic code tools. Scientists from any career stage, any level of programming experience, and research topic are welcome. Here are details:
+ Eligibility: scientists (grad students, postdocs, faculty, researchers) who regularly use an agentic coding tool for research-related programming.
+ The study involves a single Zoom session (~45–75 min) where you share your screen and work on a programming project from your own research. The experimenter will observe and ask occasional questions as you work, then follow up with a short interview about your experience with these tools.
+ links: |
+ Participants receive $50 for their time. Please fill out [this short survey](https://umich.qualtrics.com/jfe/form/SV_86BHNNPRzArnOBw) if you're interested in participating and feel free to send any questions via DM to Ellie on Slack!
+
+- expires: 2026-08-30
+ type: opportunity
+ title: Connect with Spanish Speaking RSEs!
+ preamble: |
+ 🤓 Keen to connect en español with engineers & researchers in Europe and across the pond?
+ 🦉 Curious to see how far your Duolingo skills can take you in a tech talk?
+ ❓ Tired of announcements full of questions?
+
+ Then come join us at the monthly Charlas RSE en español! 👏
+
+ An initiative started by Carlos (@cptanalatriste, from the Alan Turing Institute) and Sofía (@sfmig, from the Sainsbury Wellcome Centre) from a conversation at the DEI workshop during RSECon24. Our aims are:
+ - to showcase the RSE role across the Spanish-speaking world
+ - to connect with the cool research and tech carried out by hispanophones all over the world
+ - to selfishly speak our mother tongue before we forget it!
+ links: |
+ Check out the [GitHub](https://charlas-rse-espanol.github.io/#about) for more information!
+
+
- expires: 2026-07-31
type: opportunity
title: ACL Caregiver Artificial Intelligence Prize Challenge
@@ -377,8 +465,8 @@
Join the community in Washington, DC, September 23–25, 2026, to share solutions, tackle challenges, and build connections that will power the next generation of research.
Key dates and deadlines:
- - Tutorials — May 22, 2026
- - Papers — June 8, 2026
+ - ~~Tutorials — May 22, 2026~~
+ - ~~Papers — June 8, 2026~~
- Talk-only, BYOP, and Posters — July 20, 2026
Can't attend the full conference? Free Virtual Tutorials sessions will be held September 1–3 and September 8–11, 2026.
@@ -428,4 +516,34 @@
Submission deadline (extended): August 30, 2026.
links: |
- Journal and submission information: [Click here](https://link.springer.com/journal/10766/updates/27768048)
\ No newline at end of file
+ Journal and submission information: [Click here](https://link.springer.com/journal/10766/updates/27768048)
+
+- expires: 2026-10-01
+ type: opportunity
+ title: AI Carpentry GenAI + Teaching Discussion
+ preamble: |
+ The Software Carpentries are launching a new series of AI Carpentry community sessions: GenAI + Teaching Discussions, with the goal of fostering a Community of Practice around the teaching of programming/data analysis skills in the presence of genAI.
+ These sessions will be a space for educators to connect and share their current experiences, reflections, and questions around the teaching of computational research skills.
+ The first calls will take place on Thursday 18 June, at [12:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=GenAI+%2B+Teaching+Community+Discussion&iso=20260618T12&p1=%3A&ah=1) and [19:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=GenAI+%2B+Teaching+Community+Discussion&iso=20260618T19&p1=%3A&ah=1) (follow links to see these converted to your local time). Register to participate in the conversation.
+ Sessions will begin with an invited presentation from Elle O’Brien, co-author of Scientific Software in the Age of Vibe Coding and A survey of generative AI adoption and perceived productivity among scientists who program, and Director of the AI & Data Science Graduate Data Science Certificate at the University of Michigan.
+ links: |
+ Visit the AI Carpentry website to learn more about the calls: [Click here](https://aicarpentry.org/community/discussions/)
+
+- expires: 2026-08-01
+ type: opportunity
+ title: Connect with the PESO Project!
+ preamble: |
+ The PESO Project seeks to establish robust and sustainable scientific software capabilities aligned with the interests of the Department of Energy Office (DOE) of Advanced Scientific Computing Research (ASCR) via partnerships with software teams and communities within DOE, other US agencies, commercial scientific software developers, and the broader open source software community.
+ In addition, the PESO project is going to start an occasional UX newsletter that will include some resources on conducting UX research and ensuring usability/positive UX. If you have UX resources that should be highlighted as the newsletter launches, please reach out to the `wg-ux` channel!
+ links: |
+ PESO Project website: [Click here](https://pesoproject.org/)
+
+- expires: 2026-08-01
+ type: opportunity
+ title: Call for Papers - High-Productivity Programming Systems for HPC Applications (IJPP)
+ preamble: |
+ In the ever-evolving world of computing, the line between software and hardware has become increasingly larger. As we push the boundaries of what is possible with technology, the need for high-productivity programming solutions that can harness the power of modern hardware has never been more critical.
+ This Special Issue (SI) aims to bring points of discussion into the High-performance Computing (HPC) and scientific community about key issues on finding a compromise between high levels of abstraction (programming productivity) and meeting the challenges of performance, power consumption, and fault tolerance. This SI addresses the recent experiences in programming languages/models design for exa-scale computing systems, which can contribute to the problem of programming complex HPC systems in a productive, efficient, and reliable way. This SI provides a great opportunity for the HPC community to present new approaches for exploiting the massive parallelism that is provided by the abundance of different kinds of parallelism in today's and future HPC systems. Besides the conventional use for coarse or fine-grain parallelism in applications, our scope is to explore new approaches that enable future software systems to become more self-aware, reasoning about its internal state, and making decisions to prioritize changes in the execution of applications when necessary, putting the focus on areas such as performance tuning and power management.
+ links: |
+ Submission Deadline (extended): August 30, 2026. See [here](https://link.springer.com/journal/10766/updates/27768048) for more information on the journal and submission process.
+
diff --git a/_data/newsletter_bib.bib b/_data/newsletter_bib.bib
index d7f0254a8..a59dc9370 100644
--- a/_data/newsletter_bib.bib
+++ b/_data/newsletter_bib.bib
@@ -12,8 +12,8 @@ @article{armstrongCharacterizingSecurityCulture2026
url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002050},
urldate = {2026-05-21},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T23:31:57.963Z}
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
}
@article{armstrongPreparingResearchSoftware2026,
@@ -30,8 +30,8 @@ @article{armstrongPreparingResearchSoftware2026
url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002062},
urldate = {2026-05-21},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T23:31:57.963Z}
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
}
@report{barkerResearchSoftwareEngineering2026,
@@ -45,8 +45,8 @@ @report{barkerResearchSoftwareEngineering2026
urldate = {2026-05-28},
abstract = {The Research Software Engineering in the Age of Generative AI: Building a Community Vision workshop, held in March in Edinburgh, UK, brought together participants to explore how Generative AI may reshape the research software ecosystem, and to help inform a broader community vision for the future of the field.~ Before the workshop, attendees contributed to a draft vision statement that workshop organisers used to identify areas of agreement and difference. A version of this, published as Research Software in an Age of AI-Assisted Development: Reflections from Edinburgh, is intended to provide principles that will guide the community during this time of rapid change. In the workshop, the participants also discussed emerging practices, identified opportunities and risks, and proposed a range of high-impact pilot activities to support the safe, reproducible, and effective use of AI in research software and workflows. The areas focused on included: Suggesting policies and narratives for research-performing institutions Developing a framework to discover, document and address costs, benefits, and risks Understanding future incentives around publishing, preserving and crediting software Verifying and validating research software Defining pathways for the evolution of the research software engineers (RSE) role Identifying and developing necessary training Developing a playbook for RSE managers and open-source software project leaders Making GenAI accessible to all Collaborating together across people, community, and disciplines, not just with AI Across these areas, participants identified 46 different activities, ranging from writing sprints and community-of-practice activities that could begin soon, to longer-term research studies to investigate how verification practices, collaboration patterns, and training needs are changing as AI tools become embedded in research workflows. These projects shared a common focus on community-maintained practices, actionable guidance, and sustained coordination.},
keywords = {community,generative AI,research software,research software engineering},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.904Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/9GNVA3UV/Barker et al. - 2026 - Research Software Engineering in the Age of Generative AI Building a Community Vision.pdf}
}
@@ -83,8 +83,8 @@ @video{ByteSizedCreateYour2026
urldate = {2026-05-21},
abstract = {English Edition:\ In this ByteSized episode \& online class we're talking about GitHub Pages and how it can help you to create a web-site for your research project (reasonably) quickly. With me are Sarah Gibson and Jeremy Cohen.\ I'd li...},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.411Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/2EWWF4FT/19133793-en-bytesized-create-your-web-site-with-github-pages-j-cohen-s-gibson.html}
}
@@ -99,8 +99,8 @@ @article{carverSustainingResearchSoftware2021
urldate = {2026-05-21},
abstract = {Research software is a class of software developed to support research. Today a wealth of such software is created daily in universities, government, and commercial research enterprises worldwide. The sustainability of this software faces particular challenges due, at least in part, to the type of people who develop it. These Research Software Engineers (RSEs) face challenges in developing and sustaining software that differ from those faced by the developers of traditional software. As a result, professional associations have begun to provide support, advocacy, and resources for RSEs. These benefits are critical to sustaining RSEs, especially in environments where their contributions are often undervalued and not rewarded. This paper focuses on how professional associations, such as the United States Research Software Engineer Association (US-RSE), can provide this support.},
keywords = {career paths,Conferences,Faces,Government,Knowledge engineering,people,research software,Software,software sustainability,Sustainable development},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.413Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/MBQI2WMD/Carver et al. - 2021 - Sustaining Research Software via Research Software Engineers and Professional Associations.pdf;/Users/tit420/Zotero/storage/PETA3B2D/9470770.html}
}
@@ -196,8 +196,8 @@ @video{ComputingNotYou2026
urldate = {2026-05-21},
abstract = {English Edition: In a follow up about "unusual" computers I want to focus on field programmable gate arrays - FPGAs. With my guest and former colleague at UCL, Michael McLeod, we talk about what they are, where they are used and what's so special ...},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.412Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/HFYACMW9/19019174-en-computing-but-not-as-you-know-it-field-programmable-gate-arrays-fpga-with-michael-m.html}
}
@@ -215,8 +215,19 @@ @article{cosdenDesigningImplementingComprehensive2026
url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002086},
urldate = {2026-05-21},
langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
+}
+
+@online{CrankGPTLocalHumanpowered,
+ title = {{{CrankGPT}} — {{Local Human-powered AI}}},
+ url = {https://crankgpt.com/},
+ urldate = {2026-06-16},
+ abstract = {A human-powered, fully local, fully private AI solution.},
+ langid = {english},
annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T23:31:57.963Z}
+Read\_Status\_Date: 2026-06-16T01:04:20.125Z},
+ file = {/Users/tit420/Zotero/storage/QGJ3I4WD/crankgpt.com.html}
}
@article{crouchSoftwareSustainabilityInstitute2013,
@@ -234,8 +245,8 @@ @article{crouchSoftwareSustainabilityInstitute2013
urldate = {2026-05-21},
abstract = {To effect change, the Software Sustainability Institute works with researchers, developers, funders, and infrastructure providers to identify and address key issues with research software.},
keywords = {domain engineering,Domain engineering,maintainability,Programming,reliability,scientific computing,Scientific computing,Software development,software engineering,Software engineering,Software reliability,Training},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.413Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/ALBPHA5I/6731384.html}
}
@@ -276,8 +287,8 @@ @report{druskatResearchSoftwareEngineers2026
abstract = {Research software and its creators have long played a critical role in the advancement of research worldwide. This role is changing in the age of “generative AI” (GenAI), but both the software and the people remain of key importance. Understanding these changes is essential in enabling Research Software Engineers (RSEs) to continue contributing the same high value to the research process and its outputs.~ Before GenAI, the RSE movement had learned to clearly articulate the value proposition of embedding expert software engineering in research to its stakeholders. This blog post highlights how RSEs use GenAI to increase their capacity in both software engineering and research, and visualize this evolution. While GenAI is changing - perhaps considerably - how RSEs work in practice, their value and the value of their work for research remains steady and likely to increase.},
langid = {english},
keywords = {GenAI,Research,Research software,Research software engineers},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.904Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/UY727H52/Druskat et al. - 2026 - Research Software Engineers in the Age of GenAI Same Value, Changing Practice.pdf}
}
@@ -342,8 +353,8 @@ @article{hasselbringTechnologyResearchSoftware2026
urldate = {2026-05-28},
abstract = {Research software has been categorized for various goals. One fundamental dimension of such categorizations is the role that the software plays in the research process. Recently, a new role category has emerged: technology research software, which covers research software developed in technology research. Until now, this category of technology research software has often been overlooked and neglected within the research software engineering community. In this article, we explain technology research software and its primary subroles. Technology readiness levels are an established method of estimating the maturity of technologies, including software systems. For technology research software, these readiness levels define secondary subroles. To illustrate the concept of technology research software and to make it more tangible, we present examples of research software that, depending on its specific use within or outside of research, take on the role of technology research software as well as that of another research software category.},
keywords = {Research and development,Software development management,Technology planning},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.905Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/6BSWQ8MR/Hasselbring et al. - 2026 - Technology Research Software An Often Overlooked Category of Research Software.pdf;/Users/tit420/Zotero/storage/2UK2DMNQ/11482008.html}
}
@@ -376,8 +387,8 @@ @article{kamaliCommunitySoftwareFacility
url = {https://opensky.ucar.edu/islandora/object/technotes%3A45415},
urldate = {2026-05-28},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.905Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/UDUNTTC9/Kamali et al. - Community Software Facility Discovery Workshop Report Scientific software best practices, tools, an.pdf}
}
@@ -392,8 +403,8 @@ @report{katzResearchSoftwareAge2026
urldate = {2026-05-28},
abstract = {Important: This document began as a draft vision statement prepared in advance of the “Research Software Engineering in the Age of Generative AI” workshop, March 2026. It was intended to lead to discussion in the document before and discussion in-person at the workshop, including disagreement, and refinement. The current version of the document is a snapshot of that draft vision statement and some of the discussion. It captures a sense of the identified principles, benefits, challenges, and open questions, rather than having a single point of view that represents all of the workshop attendees and contributors. Not all authors necessarily agree with all the points in the document. A note on terminology: We use AI-assisted software development throughout this document to refer to tools and practices often described as Generative AI, GenAI, LLM-enabled development, or AI-assisted coding. We chose this term because it focuses on the activity we care about here, namely the production, verification, documentation, and maintenance of research software, rather than on a particular technology label or marketing category. Research software, the source code, scripts, computational workflows, and infrastructure that power modern research, have never been more central to human discovery. And the scholarly community (funders, publishers, societies, etc.) increasingly recognizes this, though there is still a long way to go before such recognition is widespread or leads to systemic change. At the same time, in the last few years, the rise of AI-assisted tools, i.e., those that can generate code and documentation by using large language and multimodal trained models, and act in semi-autonomous “agentic modes,” has caused significant disruption in software creation and society at large. These tools raise legitimate questions about training data provenance, licensing, quality, security, attribution, environmental cost, and accountability that are hard to ignore. Yet the conversation around AI-assisted tools too often seems to oscillate between hype and dystopian predictions. Neither of these extremes serve research well. This document also starts from the assumption that these tools are and will continue to be used, regardless of the concerns raised above, and aims to guide further usage within this context. This document outlines some ideas about how research software can and should be produced in the era of AI-assisted research tools by Research Software Engineers, computational researchers, and domain experts writing their own code. It focuses on the software production function: building and maintaining software that meaningfully advances research, but also includes the people involved. Workshop participants discussed both, including the role of RSEs and how it will change, such as leveraging the ADSA/USE-RSE-led Position Statement on Generative AI in the RSE Workplace and related work in this space. We believe that developing a shared vision of the future of research software is urgent: AI tools act as an amplifier of existing practices at every level: individual coding habits, institutional incentives, and the commercial priorities of the companies building these tools – accelerating whatever patterns they encounter, both good and bad. Applied without thought, AI-assisted tools can proliferate bugs, embed and reinforce biases, and generate plausible-looking results faster than our existing systems of peer review and verification can check and absorb them. Applied with care and discipline, it has the potential to expand access to computational methods from those with software development skills to those without them, at least for those who can afford it, and allow all researchers to focus on the work that most requires human skill and judgment.},
keywords = {generative AI,research software,research software engineering},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.904Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/MABEB35L/Katz et al. - 2026 - Research Software in an Age of AI-Assisted Development Reflections from Edinburgh.pdf}
}
@@ -406,11 +417,26 @@ @online{KindofBriefShared00:00:00+0000
abstract = {United States Research Software Engineer Association},
langid = {english},
organization = {US-RSE},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.412Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/DS3WJMXT/2022-02-06-a-brief-history-of-usrse.html}
}
+@online{macdonaldSTAMPEDPrinciplesReproducible2026,
+ title = {{{STAMPED}} Principles for Reproducible Research Objects},
+ author = {Macdonald, Austin and Baker, Cody and To, Isaac and Halchenko, Yaroslav O},
+ date = {2026-05-26},
+ number = {f3h82\_v1},
+ url = {https://osf.io/preprints/metaarxiv/f3h82_v1/},
+ urldate = {2026-06-15},
+ abstract = {Scientific claims increasingly rely upon the interplay of code, data, and computational environments. Yet the record of how they are used together is often incomplete, scattered, or lost. This undermines rigor, reproducibility, reusability, and efficiency. Previous approaches have improved the governance of digital objects but do not specify how research objects ought to be structured and managed so they can be re-executed and extended. The community is missing a shared vocabulary for this operational layer. Building on recurrent practices and convergent patterns across disciplines, we formalize seven principles: Self-containment, Tracking, Actionability, Modularity, Portability, Ephemerality, and Distributability (STAMPED). Together they give researchers guidelines for building and assessing research objects that others can trust, rerun, and build upon. We frame each principle as a spectrum so that adoption is incremental and starts from existing practice. We support each principle with normative requirements, an interactive checklist, and a map of enabling tools. As conventions mature, tooling improves, and AI agents become increasingly involved in research workflows, the goals of rigor, reproducibility, reusability, and efficiency are becoming more attainable. STAMPED gives researchers, collaborators, reviewers, and agents a common language, concrete goals, and an aligned direction for making computational research more durable. https://github.com/stamped-principles/stamped-paper/},
+ pubstate = {prepublished},
+ keywords = {open science,provenance,reproducibility,research objects},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T01:04:20.126Z},
+ file = {/Users/tit420/Zotero/storage/TJ2BGX9N/Macdonald et al. - 2026 - STAMPED principles for reproducible research objects.pdf}
+}
+
@video{ManagingPackagesPixi2026,
entrysubtype = {video},
title = {[{{EN}}] {{Managing Packages}} with {{Pixi}} - {{Raniere}} de {{Silva}} and {{Wolf Vollprecht}} - {{Code}} for {{Thought}}},
@@ -421,8 +447,8 @@ @video{ManagingPackagesPixi2026
urldate = {2026-05-21},
abstract = {English Edition:\ there is a (relatively) new kid on the block - of open source package managers. It's called Pixi: and in this episode I talk to Raniere de Silva (GESIS) and Wolf Vollprecht (Prefix - the company behind Pixi), what the tool br...},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.412Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/8C38H95J/19064274-en-managing-packages-with-pixi-raniere-de-silva-and-wolf-vollprecht.html}
}
@@ -431,8 +457,8 @@ @online{ManagingResearchSoftware
author = {Wilson, Greg},
url = {https://third-bit.com/mrsp/},
urldate = {2026-05-28},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.905Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/GKTHZ5R8/mrsp.html}
}
@@ -449,8 +475,8 @@ @article{martinaEmpiricalEvaluationLLMs2026
url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002219},
urldate = {2026-05-21},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T23:31:57.962Z}
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
}
@article{mcmahonPhysicsOpticalComputing2023,
@@ -484,16 +510,16 @@ @book{millerIntroductionSoftwareSecurity
isbn = {9798195700508},
langid = {english},
pagetotal = {390},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.412Z}
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
}
@article{mineaultGoodResearchCode,
title = {Good {{Research Code}} Handbook},
author = {Mineault, Patrick},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.412Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/VN9MWNVD/Mineault - Good Research Code handbook.pdf}
}
@@ -524,8 +550,8 @@ @online{NotsobriefHistoryResearch
author = {Hettrick, Simon},
url = {https://www.software.ac.uk/blog/not-so-brief-history-research-software-engineers-0},
urldate = {2026-05-21},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.413Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/QJB9WWQZ/not-so-brief-history-research-software-engineers-0.html}
}
@@ -576,8 +602,8 @@ @article{posadaOakRidgeComputing2026
url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26001470},
urldate = {2026-05-21},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T23:31:57.962Z}
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z}
}
@book{ramanathanIntroductionNeuromorphicComputing2025,
@@ -595,6 +621,15 @@ @book{ramanathanIntroductionNeuromorphicComputing2025
file = {/Users/tit420/Zotero/storage/JCZQ8GXY/853942021D89F82AED182F9021E7E0F5.html}
}
+@online{RealScorelineReveals,
+ title = {The {{Real Scoreline}} Reveals Nations Facing Climate Penalties - {{University}} of {{Reading}}},
+ url = {https://www.reading.ac.uk/news/2026/University-News/The-Real-Scoreline-reveals-nations-facing-climate-penalties},
+ urldate = {2026-06-16},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T01:04:20.125Z},
+ file = {/Users/tit420/Zotero/storage/926BIU3J/The-Real-Scoreline-reveals-nations-facing-climate-penalties.html}
+}
+
@unpublished{ruchtiUSRSE25Rapid2025,
title = {{{USRSE}} 25 Rapid Access Micro Talks},
author = {Ruchti, Carol and Ogundipe, Michael and Ward, Brian and Hillegas, Curt and Mizrachi, Eli and Brownell, Dave and Tapera, Tinashe Michael and Soules, Jeff and Lackie, Paula and Ruchti, Carol and Ogundipe, Michael and Ward, Brian and Hillegas, Curt and Mizrachi, Eli and Brownell, Dave and Tapera, Tinashe Michael and Soules, Jeff and Lackie, Paula},
@@ -799,6 +834,20 @@ @report{teranishiS4PSTStewardshipAdvancement2026
file = {/Users/tit420/Zotero/storage/UYMG4WYZ/Teranishi et al. - 2026 - S4PST Stewardship and Advancement for Programming Systems and Tools 2024-2025 Project Report.pdf}
}
+@online{udellHowMakeBest2026,
+ title = {How to Make Best Use of Git and {{GitHub}} for {{AI-assisted}} Software Development},
+ author = {Udell, \textasciitilde{} Jon},
+ date = {2026-06-02T19:41:11+00:00},
+ url = {https://blog.jonudell.net/2026/06/02/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development/},
+ urldate = {2026-06-16},
+ abstract = {I’m working on a new tool whose tagline is the title of this post: Make best use of git and GitHub for AI-assisted software development. Called Bram (“Bram runs agents mindfully”)…},
+ langid = {american},
+ organization = {Jon Udell},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T01:04:20.126Z},
+ file = {/Users/tit420/Zotero/storage/74BXFIZD/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development.html}
+}
+
@online{UnderstandingAdvancingResearch2025,
title = {Understanding and Advancing Research Software Grant Funding Models},
date = {2025-07-25},
diff --git a/_data/newsletter_bib_yml.yml b/_data/newsletter_bib_yml.yml
index f462111a9..dafa37b78 100644
--- a/_data/newsletter_bib_yml.yml
+++ b/_data/newsletter_bib_yml.yml
@@ -3,8 +3,8 @@ nocite: "[@*]"
references:
- accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T23:31:57.963Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
author:
- family: Armstrong
given: Matthew
@@ -33,8 +33,8 @@ references:
volume: 183
- accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T23:31:57.963Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
author:
- family: Armstrong
given: Matthew
@@ -92,8 +92,8 @@ references:
guidance, and sustained coordination."
accessed: 2026-05-28
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-28T20:09:36.904Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
author:
- family: Barker
given: Michelle
@@ -216,8 +216,8 @@ references:
li\\..."
accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T03:25:52.411Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
id: ByteSizedCreateYour2026
issued: 2026-05-19
language: en-US
@@ -242,8 +242,8 @@ references:
(US-RSE), can provide this support.
accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T03:25:52.413Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
author:
- family: Carver
given: Jeffrey C.
@@ -392,8 +392,8 @@ references:
what they are, where they are used and what's so special \\..."
accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T03:25:52.412Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
id: ComputingNotYou2026
issued: 2026-05-05
language: en-US
@@ -404,8 +404,8 @@ references:
url: "https://www.buzzsprout.com/1326658/episodes/19019174-en-computing-but-not-as-you-know-it-field-programmable-gate-arrays-fpga-with-michael-mcleod"
- accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T23:31:57.963Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
author:
- family: Cosden
given: Ian A.
@@ -428,13 +428,23 @@ references:
type: article-journal
url: "https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002086"
volume: 183
+- abstract: A human-powered, fully local, fully private AI solution.
+ accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T01:04:20.125Z
+ id: CrankGPTLocalHumanpowered
+ language: en-US
+ title: CrankGPT --- [Local Human-powered AI]{.nocase}
+ type: webpage
+ url: "https://crankgpt.com/"
- abstract: To effect change, the Software Sustainability Institute
works with researchers, developers, funders, and infrastructure
providers to identify and address key issues with research software.
accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T03:25:52.413Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
author:
- family: Crouch
given: Stephen
@@ -537,8 +547,8 @@ references:
remains steady and likely to increase.
accessed: 2026-05-28
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-28T20:09:36.904Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
author:
- family: Druskat
given: Stephan
@@ -681,8 +691,8 @@ references:
software category."
accessed: 2026-05-28
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-28T20:09:36.905Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
author:
- family: Hasselbring
given: Wilhelm
@@ -742,8 +752,8 @@ references:
volume: 119
- accessed: 2026-05-28
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-28T20:09:36.905Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
author:
- family: Kamali
given: "Author: Soudeh"
@@ -820,8 +830,8 @@ references:
work that most requires human skill and judgment."
accessed: 2026-05-28
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-28T20:09:36.904Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
author:
- family: Katz
given: Daniel S.
@@ -889,10 +899,10 @@ references:
type: report
url: "https://zenodo.org/records/20321134"
- abstract: United States Research Software Engineer Association
- accessed: 2022-05-21
+ accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T03:25:52.412Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
author:
- family: Sochat
given: Vanessa
@@ -925,14 +935,59 @@ references:
title: A kind-of brief shared early history of US-RSE
type: webpage
url: "https://us-rse.org/2022-02-06-a-brief-history-of-usrse/"
+- abstract: "Scientific claims increasingly rely upon the interplay of
+ code, data, and computational environments. Yet the record of how
+ they are used together is often incomplete, scattered, or lost. This
+ undermines rigor, reproducibility, reusability, and efficiency.
+ Previous approaches have improved the governance of digital objects
+ but do not specify how research objects ought to be structured and
+ managed so they can be re-executed and extended. The community is
+ missing a shared vocabulary for this operational layer. Building on
+ recurrent practices and convergent patterns across disciplines, we
+ formalize seven principles: Self-containment, Tracking,
+ Actionability, Modularity, Portability, Ephemerality, and
+ Distributability (STAMPED). Together they give researchers
+ guidelines for building and assessing research objects that others
+ can trust, rerun, and build upon. We frame each principle as a
+ spectrum so that adoption is incremental and starts from existing
+ practice. We support each principle with normative requirements, an
+ interactive checklist, and a map of enabling tools. As conventions
+ mature, tooling improves, and AI agents become increasingly involved
+ in research workflows, the goals of rigor, reproducibility,
+ reusability, and efficiency are becoming more attainable. STAMPED
+ gives researchers, collaborators, reviewers, and agents a common
+ language, concrete goals, and an aligned direction for making
+ computational research more durable.
+ https://github.com/stamped-principles/stamped-paper/"
+ accessed: 2026-06-15
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T01:04:20.126Z
+ author:
+ - family: Macdonald
+ given: Austin
+ - family: Baker
+ given: Cody
+ - family: To
+ given: Isaac
+ - family: Halchenko
+ given: Yaroslav O
+ id: macdonaldSTAMPEDPrinciplesReproducible2026
+ issued: 2026-05-26
+ keyword: open science,provenance,reproducibility,research objects
+ number: f3h82_v1
+ status: pre-published
+ title: STAMPED principles for reproducible research objects
+ type: webpage
+ url: "https://osf.io/preprints/metaarxiv/f3h82_v1/"
- abstract: "English Edition:\\ there is a (relatively) new kid on
the block - of open source package managers. It's called Pixi: and
in this episode I talk to Raniere de Silva (GESIS) and Wolf
Vollprecht (Prefix - the company behind Pixi), what the tool br\\..."
accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T03:25:52.412Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
id: ManagingPackagesPixi2026
issued: 2026-05-12
language: en-US
@@ -942,8 +997,8 @@ references:
url: "https://www.buzzsprout.com/1326658/episodes/19064274-en-managing-packages-with-pixi-raniere-de-silva-and-wolf-vollprecht"
- accessed: 2026-05-28
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-28T20:09:36.905Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
author:
- family: Wilson
given: Greg
@@ -953,8 +1008,8 @@ references:
url: "https://third-bit.com/mrsp/"
- accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T23:31:57.962Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
author:
- family: Martina
given: Tobia
@@ -1031,8 +1086,8 @@ references:
can pick up whenever you need to a refresher or to learn a new
topic.
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T03:25:52.412Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
author:
- family: Miller
given: Barton P.
@@ -1046,8 +1101,8 @@ references:
title: Introduction to Software Security
type: book
- annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T03:25:52.412Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
author:
- family: Mineault
given: Patrick
@@ -1083,8 +1138,8 @@ references:
url: "https://nesbitt.io/2026/03/15/guided-meditation-for-developers.html"
- accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T03:25:52.413Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
author:
- family: Hettrick
given: Simon
@@ -1130,8 +1185,8 @@ references:
volume: 7
- accessed: 2026-05-21
annote: |
- Read_Status: To Read\
- Read_Status_Date: 2026-05-21T23:31:57.962Z
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
author:
- family: Posada
given: Edwin F.
@@ -1187,6 +1242,15 @@ references:
title: Introduction to Neuromorphic Computing
type: book
url: "https://www.cambridge.org/core/books/introduction-to-neuromorphic-computing/853942021D89F82AED182F9021E7E0F5"
+- accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T01:04:20.125Z
+ id: RealScorelineReveals
+ title: The Real Scoreline reveals nations facing climate penalties -
+ University of Reading
+ type: webpage
+ url: "https://www.reading.ac.uk/news/2026/University-News/The-Real-Scoreline-reveals-nations-facing-climate-penalties"
- abstract: Slide set of the accepted rapid access micro talks at USRSE
25.
accessed: 2026-04-09
@@ -1540,6 +1604,24 @@ references:
title-short: S4PST
type: report
url: "https://www.osti.gov/biblio/3016977"
+- abstract: "I'm working on a new tool whose tagline is the title of
+ this post: Make best use of git and GitHub for AI-assisted software
+ development. Called Bram (\"Bram runs agents mindfully\")..."
+ accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T01:04:20.126Z
+ author:
+ - family: Udell
+ given: \~ Jon
+ id: udellHowMakeBest2026
+ issued: 2026-06-02
+ language: en-US
+ publisher: Jon Udell
+ title: How to make best use of git and GitHub for
+ [AI-assisted]{.nocase} software development
+ type: webpage
+ url: "https://blog.jonudell.net/2026/06/02/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development/"
- abstract: Read the latest article version by Daniel S. Katz, Eric A.
Jensen, Michelle Barker at Open Research Europe
accessed: 2025-11-07
diff --git a/_posts/newsletters/2026-06-15-newsletter.md b/_posts/newsletters/2026-06-15-newsletter.md
new file mode 100644
index 000000000..ff651f0cb
--- /dev/null
+++ b/_posts/newsletters/2026-06-15-newsletter.md
@@ -0,0 +1,526 @@
+---
+layout: post
+title: "US-RSE June 2026 Newsletter"
+subtitle: "🤔 Arrestive Curiosity & RSEs: How to Turn the Shiny Toy Syndrome Bug into a Feature 🤔"
+category: newsletter
+tags: [newsletter, June]
+date: 2026-06-15 00:00:00 -0400
+author: "Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden (Editor)"
+image: "/assets/img/newsletter-202606/us-rse_4k_members.png" #TODO
+img_alttext: "Colourful poster with the words \"Celebrating 4,000+ Member Milestone\" and a progression of trees growing from a seedling to a full tree, with the number 4011 prominently displayed." #TODO
+next_meeting_date: Thursday, July 9, 2026, 12:00PM EST #Done
+sections:
+ preamble: true #Done
+ headline: true #Done
+ conference: true #Done
+ execupdate: false #TODO
+ scupdate: false #TODO
+ orgmember: true #TODO
+ communityfunds: false #TODO
+ news: true #TODO
+ events: true #TODO
+ reads: true #TODO
+ involved: true
+ jobs: true
+
+---
+
+
+
+First of all, Happy Pride Month 🌈, and Happy Juneteenth 🎉! We hope you
+are all having a wonderful summer celebrating the diversity and
+resilience of our communities.
+
+It’s been another busy month for US-RSE, as conference planning
+continues to ramp up, membership continues to grow, and the organization
+continues to expand its offerings and impact to the research software
+community. In this issue, we’ll discuss shiny toy syndrome in
+technology, celebrate the LGBTQ+ community, and share all the latest and
+greatest news from US-RSE.
+
+
+
+
+
+In this issue:
+
+- [1 🤔 Arrestive Curiosity &
+ RSEs: How to Turn the Shiny Toy Syndrome Bug into a Feature
+ 🤔](#thinking-arrestive-curiosity--rses-how-to-turn-the-shiny-toy-syndrome-bug-into-a-feature-thinking)
+- [2 📣 Mark Your Calendars for
+ USRSE’26! 📣](#mega-mark-your-calendars-for-usrse26-mega)
+- [3 🤝 Organizational Founding
+ Membership
+ 🤝](#handshake-organizational-founding-membership-handshake)
+- [4 🗞️ Community News
+ 🗞️](#newspaper_roll-community-news-newspaper_roll)
+- [5 Community
+ Spotlight](#community-spotlight)
+- [6 👀 Interesting Events and
+ Opportunities 👀](#eyes-interesting-events-and-opportunities-eyes)
+- [7 📚 Featured Reads, Videos,
+ and Podcasts 📚](#books-featured-reads-videos-and-podcasts-books)
+- [8 🏃 Get Involved!
+ 🏃](#running-get-involved-running)
+- [9 🧑💼 Recent Job Postings
+ 🧑💼](#office_worker-recent-job-postings-office_worker)
+
+------------------------------------------------------------------------
+
+## 🤔 Arrestive Curiosity & RSEs: How to Turn the Shiny Toy Syndrome Bug into a Feature 🤔
+
+
+
+This month, I had the pleasure of meeting some fellow R users at the
+Boston R User Group meetup, where I can say I finally felt safe opening
+a conversation with a hot take like, “R is the best,” knowing it would
+likely not spark a flame war. I’m sure many of you having read that
+sentence are already compiling the several counterarguments in your
+head, mashing away your response in a text editor, choosing all your
+best and worst use cases as examples and calling on the greats of your
+respective community to back you up. But this discussion is actually not
+about flame wars; in fact, as I’m sure you’ve experienced, we as
+technologists often care less about what tool is objectively best, and
+more about what tool is best for us, our project, and our team.
+
+And while this can sound like a freeing stance on tooling in general, it
+leaves us with an acute conundrum: how do we know when to *switch*
+tools? When do we know that the tool we’re using is no longer best for
+us, and that we should switch to something else? As computing becomes
+more accessible and capable, more individuals are building tools that
+avow to *finally* and *decisively* solve the problem of \[insert other
+tools’ shortcomings here\]. Indeed, whether it was Markdown’s attempt to
+become the de facto standard for writing on the web Anaconda claim to be
+the last word in environment management for data science, or the eternal
+paradox of Apple’s latest OS somehow always having “the best feature,
+ever,” technology is rife with shiny toys that promise to solve all our
+problems. On the one hand, it can be incredibly overwhelming trying to
+keep up with the latest and greatest, and on the other, you could easily
+risk missing out on a tool that could be a game changer for you and your
+team if you don’t branch out and experiment from time to
+time[1^](In%20fact,%20at%20this%20UseR%20Boston%20meetup,%20we%20ourselves%20had%20a%20hard%20time%20rectifying%20our%20excitement).
+
+This decision fatigue can end up being a significant job hazard for
+people who work with technology. What if your organization is one of the
+unfortunate few that decided to go all-in on Skype\[2^\], or what if you
+can’t ship a new product or publish a paper because your team has not
+ported over its legacy libraries to Python 3 yet? As RSEs, part of our
+responsibility is to help scientific teams navigate this ever-changing
+landscape of tools and technologies, and it can be very tricky to draw
+the line between productive experimentation and [shiny toy
+syndrome](https://nesslabs.com/shiny-toy-syndrome). How does one justify
+several afternoons’ worth of tinkering, only to come to the conclusion
+that the new tool actually *doesn’t* do what it says on the box - or at
+least, not to your satisfaction — and continue to be trusted with the
+responsibility of guiding your team’s technological vision?
+
+But as I thought about this more, I realized that this activity of
+tinkering and experimenting with new tools is actually a critical part
+of our job as RSEs, and that we can turn this “bug” of shiny toy
+syndrome into a “feature” of arrestive curiosity. Arrestive curiosity is
+the tendency to be so curious about new tools and technologies that you
+cannot move forward with your own work until you’ve proven a new tool is
+either better or worse for you than the one you’re currently
+using\[3^\]. If you’ve ever been up late at night trying to get a VSCode
+extension to run without error, trying to figure out why a new library
+can’t just install on your system, or drawing out your ultimate
+note-taking entourage of apps for never losing a thought, I see you!
+This kind of curiosity can be a disastrous time sink — but it can also
+be a powerful way to stay on top of the latest and greatest, and to make
+sure you’re using the best tools for you and your team.
+
+So, how do we cultivate arrestive curiosity without falling into the
+trap of time-wasting? Having wrestled with this for several years, I
+think I can provide a few considerations that have helped me strike this
+balance:
+
+1. *Stop being distracted by the perfect tool until you know what
+ perfect is supposed to look like.* Before seriously investigating a
+ new tool, write down exactly what problem or need you think it is
+ trying to solve for you. In the simple process of articulating this,
+ you may find that your existing workflow just needs some refinement,
+ or a simple adjustment or reframing of the problem. 95% of the time,
+ my tinkering does not pass this step.
+
+2. *Get comfortable with the discomfort of your current tools.* If
+ you’ve successfully passed the first step, then you know for a fact
+ that your current workflow needs are not being met, and a new tool —
+ or repurposing an old one — is likely the solution. But before you
+ dive into the new tool, now is the time to measure the discomfort of
+ your current workflow. How much time are you losing to this problem?
+ How much mental energy are you spending on it? How much is it
+ costing your team in productivity and morale? If the cost of your
+ current workflow is not high enough, then it may not be worth the
+ time and effort to switch to a new tool. If you can tolerate the
+ discomfort, then the tool search ends here.
+
+3. *Refine to absurdum.* If you are still convinced that something is
+ missing, then it is time to start looking for what is missing.
+ Surely someone has felt this acute pain, right? The internet is a
+ vast place, and there are several billion of us using it at any
+ given time. It’s more than likely that someone, somewhere, has been
+ in the exact position you’re in, with an install that is too slow, a
+ link that doesn’t work, or a workflow that is too clunky and just
+ missing that, *secret something*. Go out into dark corners of the
+ second, third, and fourth pages of Google search, ask around on
+ Reddit and Facebook groups, or find forums and communities that are
+ relevant to the problem space. Surely **someone** has faced this
+ problem, too?
+
+4. If the solution is identified, use it. If not, build it. By this
+ point, if you have found a niche problem that 1) arrests your
+ productivity, 2) causes measurable discomfort, and 3) has not been
+ solved by anyone else, then this is a problem worth solving. In
+ fact, as an RSE, this is the *perfect* problem to have, because it
+ is within this narrow gap between your vision and the status quo
+ that you can actually make valuable impact to your team. If you
+ can’t or don’t want to build the solution yourself, one of two
+ things must be true: either the problem is not worth solving, or you
+ are *not yet* the right person to solve it.
+
+In my experience, the really interesting Research Software Engineering
+is what happens when as an engineer I have become *obsessed* with a
+particular technological blocker to the success of my or my colleagues’
+scientific endeavors.
+
+It is the moment we look at the scientific engine and say, “I know we
+*could* just use \[X Tool\] to write this part of the paper, but I just
+can’t accept that this is the best way to do it. I simply can’t. There
+*must* be a better way.”
+
+This is the “arrestive,” part of the “arrestive curiosity” — the part
+that literally keeps you up at night, ceases you in your tracks every
+time you think about it, and continues to consume all of your mental
+energy until you have either found a solution or come to terms with the
+fact that there is no solution.
+
+And if you ask me, that tendency to be obsessed with finding the best
+way to do science is what makes a good RSE a *great* RSE. So, the next
+time you find yourself in the throes of shiny toy syndrome, try to
+channel that energy into arrestive curiosity using the flowchart I
+outlined above, and see where it takes you. You might just find that the
+perfect tool was right in front of you all along, or you might end up
+building something that changes the game for, your team, and perhaps
+even the science itself.
+
+vs. hesitation around all things AI in the R world. We could barely come
+to a consensus on whether we could be convinced to switch over to the
+new native pipe `|>` or stick with the beloved `magrittr` pipe `%>%`
+that we’ve been using for years, all the while doing our best “old man
+yells at cloud” impression. Spoiler alert: I’m yelling at the cloud.
+\[2^\]: Shout out to everyone currently being held hostage by their
+CTO’s contract with Microsoft and having to wake up every morning to the
+sound of a Teams notification. We see you, and we feel your pain.
+\[3^\]: Yes, I just came up with it. No, I will not be answering
+questions. ————————————————————————
+
+## 📣 Mark Your Calendars for USRSE’26! 📣
+
+
+
+Save the date for USRSE’26: **Advancing Science in the Age of AI**
+
+
+
+
+
+
+We’re thrilled to announce that USRSE’26 will be held at the San Jose
+Marriott from October 19-21, 2026 in San Jose, California, with the
+theme **“Advancing Science in the Age of AI”.**
+
+Chairs have been appointed to lead each of the core committees for
+USRSE’26. These chairs have begun assembling sub‑teams from the pool of
+volunteers who expressed interest in supporting the respective areas. If
+you were not selected for a chair position, please stay tuned, as chairs
+reach out for volunteers for these committee positions.
+
+**What’s next?**
+
+- **Call for Proposals:** Submit your work via papers, short talks,
+ BoFs, workshops, or posters. [View
+ More](https://us-rse.org/usrse26/participate/)
+- **Call for Reviewers:** Play a key role in creating a dynamic and
+ varied technical program that will appeal to conference attendees from
+ all RSE backgrounds. [Apply to
+ Review](https://forms.gle/hDGsK52sJFqUA2MA7)
+- **Committee Formation:** Sub‑teams will be formed shortly; be on the
+ lookout for an email from a perspective committee chair with details.
+- **Stay Informed:** Regular updates will be posted at
+ [us-rse.org/usrse26](https://us-rse.org/usrse26). Please bookmark the
+ page and check back frequently for the latest information.
+
+Your continued involvement is essential to the success of USRSE’26. We
+look forward to collaborating with you to deliver a vibrant, inclusive,
+and impactful conference.
+
+#### 📧 Join Our Mailing List 📧
+
+Want to stay updated on all things US-RSE? Join our mailing list to
+receive direct news about all US-RSE conferences. Sign up
+[here](https://groups.google.com/a/us-rse.org/g/usrse-conference).
+
+#### 💬 Have Questions? 💬
+
+If you have any questions, feel free to reach out to the organizers at
+usrse26-conference@us-rse.org.
+
+#### 📅 Save the Date 📅
+
+More details about the conference program, registration, and travel
+information will be coming your way in the months ahead. Stay tuned at
+[us-rse.org/usrse26](https://us-rse.org/usrse26)!
+
+We’re looking forward to seeing you all in **San Jose**!
+
+------------------------------------------------------------------------
+
+## 🤝 Organizational Founding Membership 🤝
+
+
+
+
+
+US-RSE envisions a future where Research Software Engineers are
+universally respected for advancing science, technology, and society
+through the transformative power of research software engineering. We’re
+excited to share that the momentum around our Organizational Founding
+Membership continues to grow! See the list below for the current members
+(six more are onboarding at the moment).
+
+Organizations that join **on or before June 30, 2026**, will be
+recognized in perpetuity as founding members. Founding organizations
+will also lock in current membership fees through December 31, 2028.
+Organizational support helps sustain and expand vital community
+offerings, including the annual conference, monthly calls and
+newsletter, job board, working groups, and new resources.
+
+Please reach out to Sandra Gesing at if you are
+interested in becoming an organizational founding member!
+
+### Premier Members
+{% for org in site.data.org-members.premier %}
+
+- [{{ org.name }}]({{ org.url }})
+
+{% endfor %}
+
+### Standard Members
+{% for org in site.data.org-members.standard %}
+
+- [{{ org.name }}]({{ org.url }})
+
+{% endfor %}
+
+### Basic Members
+{% for org in site.data.org-members.basic %}
+
+- [{{ org.name }}]({{ org.url }})
+
+{% endfor %}
+
+------------------------------------------------------------------------
+
+## 🗞️ Community News 🗞️
+
+
+
+
+
+### **Community Shoutouts**
+
+🥳 Congratulations to members of the RSE community recognized with
+[Stanford Data Science
+(CORES)](https://datascience.stanford.edu/cores/awards) awards!
+
+- Malcolm Barrett & Alex Koufos : OpenSource@Stanford Community Prize
+- Ellianna Abrahams: Open Science Innovator Prize
+
+These awards recognize individuals who have made significant
+contributions to open science and data science, and we’re thrilled to
+see members of our community being honored for their impactful work!
+
+Additionally, The RAPTOR team from Argonne National Laboratory and
+collaborating institutions recently won the SC25 Best Reproducibility
+Advancement Award, using Chameleon Cloud to make their artifact fully
+reproducible. This marks the second consecutive year a Chameleon user
+has taken home this honor!
+
+Read the announcement
+[here](https://blog.chameleoncloud.org/posts/sc25-best-reproducibility-advancement-award/).
+
+> Did you know that we have a community Code of Conduct? Anyone is able
+> to view it in the `#code_of_conduct` Slack channel, under `Files`!
+
+### In Memoriam
+
+We mourn the loss of a dear friend and colleague, Cleve Moler, who
+passed away on May 20, 2026, at the age of 86 at his home surrounded by
+his family. Cleve was chief mathematician and cofounder of MathWorks and
+the author of the first version of MATLAB. Please join us in remembering
+their contributions to science and engineering by reading Mathworks
+official announcement
+[here](https://www.mathworks.com/company/aboutus/founders/clevemoler.html).
+
+## Community Spotlight
+
+🌱 Our community is full of people doing fascinating research and
+software work, and we want to put a face to it. Starting this month,
+we’ll be featuring a group of different members in a regular spotlight:
+what they work on, a tool they can’t live without, and how they found
+their way into RSE work.
+
+We’d love to feature YOU. It takes about 5 minutes to fill out, and
+nothing gets posted without your okay:
+
+
+Email [Pengyin Shan](mailto:pengyins@illinois.edu) for any questions!
+
+### **Community Calls**
+
+
+
+
+
+Our next meeting is scheduled for Thursday, July 9, 2026, 12:00PM EST.
+We hope to see you there!
+
+------------------------------------------------------------------------
+
+## 👀 Interesting Events and Opportunities 👀
+
+
+
+{% assign today = "now" | date: "%Y-%m-%d" %}
+{% for opp in site.data.newsletter-events-opportunities %}
+{% assign expires = opp.expires | date: "%Y-%m-%d" %}
+{% if opp.type == "opportunity" and expires >= today %}
+{% include opportunity-box.html
+ title=opp.title
+ when=opp.when
+ where=opp.where
+ preamble=opp.preamble
+ links=opp.links
+%}
+{% endif %}
+{% endfor %}
+
+{% for event in site.data.newsletter-events-opportunities %}
+{% assign expires_formatted = event.expires | date: "%Y-%m-%d" %}
+{% if expires_formatted >= today %}
+{% if event.type == "event" %}
+{% include event-box.html
+ title=event.title
+ when=event.when
+ where=event.where
+ preamble=event.preamble
+ links=event.links
+%}
+{% endif %}
+{% endif %}
+{% endfor %}
+
+Have an event or opportunity you want to promote? Reach out on Slack in
+the `#newsletters` channel!
+
+------------------------------------------------------------------------
+
+## 📚 Featured Reads, Videos, and Podcasts 📚
+
+
+
+{% assign refs = site.data.newsletter_bib_yml.references
+ | where_exp: "r", "r.annote contains 'Read_Status: To Read'" %}
+
+{% assign professional = refs | where: "type", "article-journal" %}
+
+{% if professional.size > 0 %}
+### 📑 Recent Publications
+{% for ref in professional %}
+{% include citation-publication.html ref=ref %}
+{% endfor %}
+{% endif %}
+
+{% assign podcasts = refs | where: "type", "motion_picture" %}
+
+{% if podcasts.size > 0 %}
+### 🎧 Podcast Episodes
+{% for ref in podcasts %}
+{% include citation-podcast.html ref=ref %}
+{% endfor %}
+{% endif %}
+
+{% assign other = refs | where: "type", "webpage" %}
+
+{% if other.size > 0 %}
+### 📇 Blog Posts, Videos, & Other Reads
+{% for ref in other %}
+{% include citation.html ref=ref %}
+{% endfor %}
+{% endif %}
+
+Did you read something interesting this week? Want to share your own
+publications in the community? Reach out on Slack in the `#newsletters`
+channel!
+
+------------------------------------------------------------------------
+
+## 🏃 Get Involved! 🏃
+
+
+
+US-RSE Working Groups:
+
+{% assign wgs = site.data.menus["working-groups"][0].items %}
+
+
+------------------------------------------------------------------------
+
+## 🧑💼 Recent Job Postings 🧑💼
+
+
+
+{% assign today = 'now' | date: "%Y-%m-%d" %}
+
+{% for job in site.data.jobs %}
+ {% assign expires_formatted = job.expires | date: "%Y-%m-%d" %}
+ {% if expires_formatted >= today %}
+ -
+ {{ job.name }}
+ 📍 {{ job.location }}
+ 🗓️ Posted: {{ job.posted }} | Expires: {{ job.expires }}
+
+ {% endif %}
+{% endfor %}
+
+
+### Other Job Boards
+
+
+{% for board in site.data.job-boards.boards %}
+ - {{ board.name }}
+{% endfor %}
+
+
+You can learn more about job boards in the `#jobs` Slack channel!
+
+------------------------------------------------------------------------
+
+**This newsletter is a joint effort of members of the US-RSE
+Association.**
+
+© US-RSE • 2021–{{ 'now' | date: "%Y" }} • US-RSE is a fiscally sponsored project of [Community Initiatives](http://communityin.org/)
+
+[Email](mailto:contact@us-rse.org) [Mastodon](https://fosstodon.org/@us_rse) [Twitter](https://twitter.com/us_rse) [YouTube](https://youtube.com/@us_rse) [LinkedIn](https://linkedin.com/company/us-rse/) [GitHub](https://github.com/USRSE)
diff --git a/_posts/newsletters/quarto/_headline.md b/_posts/newsletters/quarto/_headline.md
index d97c64bab..753c6627c 100644
--- a/_posts/newsletters/quarto/_headline.md
+++ b/_posts/newsletters/quarto/_headline.md
@@ -1,62 +1,107 @@
-## 🤩 Wait a Minute, I'm an RSE, I Know How to Do That! 🤩
+## 🤔 Arrestive Curiosity & RSEs: How to Turn the Shiny Toy Syndrome Bug into a Feature 🤔
-*I know how to do that!*
-
-It is one of the most rewarding thoughts you can have as a research software engineer: that moment when you notice a colleague, PI, collaborator, or student struggling with a software problem and realize you can help.
-
-Not because they are unmotivated. Not because they are bad scientists. But because things are not working, not moving quickly enough, or not being recognized for what they are: software problems that can be solved with the right tools, techniques, and expertise. Maybe the scientist is looking toward industry and thinking, "I wish we could move as quickly as Google, Facebook, or Microsoft." Or, more recently, "I wish we could figure out how to really use all this LLM stuff." Ever persistent, the scientist keeps chasing their research questions. They want to discover the next big thing in their field. They want to make an impact. But because their workflow was essentially written in 2012, and because they do not have the time, support, or expertise to modernize it, they are stuck moving at the pace of 2012.
-
-And as RSEs, we get it! Code can be fragile — and scary. If a new student or postdoc touches it, they might break it. If the code breaks, so might every paper, grant, and project built on top of it. When was the last time it was updated? Months ago? Years ago? So the scientist does not touch it. They treat it like a Rube Goldberg machine: they know it works, but they no longer remember how. At this point, they are too afraid to find out.
-
-As RSEs, we see this...and get excited.
-
-Because we know how to help. 🥹
-
-I first came across the term "RSE" in the wonderfully cute and informative 2019 YouTube video, [The Story of the Research Engineer](https://www.youtube.com/watch?v=trAfA9VWLTQ), and I instantly fell in love with the idea. Here was a name for the squeaky wheel that gets the grease: the person who helps scientists get unstuck, move faster, and work more sustainably. But then as now, the field was young. There was not much consensus about what an RSE was, where they belonged, or how institutions should support them.
-
-The term itself emerged in the UK [in 2012](https://www.software.ac.uk/blog/not-so-brief-history-research-software-engineers-0), after a group of researchers and software practitioners began formalizing a role that many people were already doing but few institutions knew how to recognize. Since then, definitions have been proposed, refined, and debated.
-
-Ian Cosden, one of our newsletter editors and Director of *Research Software Engineering for Computational & Data Science* at Princeton, defines the role partly by what it is not. An RSE, he argues, is not simply a researcher, not simply a facilitator, and not simply a pure software engineer. The role lives in the productive space between those identities.
-
-
-
-
-
-
-
-Goth et al. ([2025](https://f1000research.com/articles/13-1429)) offer one recent attempt to concretize the foundational competencies and responsibilities of an RSE, including software development, building and distributing software assets, understanding the research lifecycle, and supporting reproducible, sustainable research. [Vanessa Sochat's EasyBuild talk](https://www.youtube.com/watch?v=FB2yV8TNnSw), on the other hand, emphasizes just how broad this space can be: among roughly 400 people surveyed who identified themselves to be working on "research software" in some capacity, there were more than *190 unique job titles*. That degree of diversity can be both a strength and a challenge. It shows how widely research software work appears across institutions, but it also explains why the role can be so difficult to define, hire for, promote, and reward. Another one of our US-RSE members, Dan Katz, proposes a 3-dimensional schematic
-to isolate the Super RSE role who commands "a superset of the responsibilities of the traditional RSE role, combining both service and the RSE’s own research."
-
-
-
-
-
-By identifying this RSE unicorn, Katz highlights the fact that as we define
-the breadth of the scope of the RSE, we also need to think about its
-potentially necessary boundaries.
-
-In a 2022 [career Q&A in *Nature*](https://www.nature.com/articles/d41586-022-01516-2), Paul Richmond predicted that RSEs could become equals in the academic environment if they receive proper recognition for their contributions. James Schloss, in his [YouTube talk](https://www.youtube.com/watch?v=t2BjZ5hSjHo) highlights some of the barriers still standing in the way: the publication economy, academic resistance to software engineering best practices, and the difficulty of competing with industry salaries for people with similar technical expertise. In fact, one of my very first suggestions for newsletter topics was to discuss the definition of the title "Research Software Engineer" itself, and I was told very firmly to avoid the topic as much as possible — not because it was inflammatory, but because it remains a particularly sensitive topic. While many are strongly attached to the name for its truthiness, just as many others are more concerned with defining the tasks, responsibilities, and competencies of the role, regardless of what it is called, because funding sources will pay a great deal of attention to those details.
-
-But friends, there is hope. 🌱
-
-Just as a small group of concerned scientists and software practitioners began with an idea, a conversation, and a Google Group, we can continue making the role visible at our own institutions. This can be through formal titles, clearer career paths, better credit, stronger communities of practice, or simply naming the work when we see it as we help research software engineering become easier to recognize and harder to ignore. This week, celebrate yourself by encouraging your colleagues, coworkers, PIs, and students to **make this role visible**. Look around. We are once again watching technology change the fabric of research itself. Rigorous science, and the software that powers it, cannot afford to be left behind. Now more than ever, research needs talented, driven, curious technology specialists who can ask new questions, solve impossible bugs, push compute clusters to their limits, and preserve the code — and the science — that so many people depend on.
-
-Our Executive Director had this to say about the importance of this community:
-
-"Reaching more than 4,000 members is not just a milestone in numbers - it reflects a growing
-community of people who care deeply about advancing research through software, collaboration, and
-support for one another. As Executive Director, I am incredibly grateful to be part of this community
-and inspired every day by the generosity, expertise, and passion our members bring to US-RSE. Thank
-you for helping build a place where research software engineers can truly belong."
-
-> [Sandra](https://us-rse.org/about/staff/)
-
-This month, we thank the scrappy and passionate group of researchers who helped crystallize the idea of the Research Software Engineer, [one quiet afternoon in Oxford, UK, in 2012](https://www.pure.ed.ac.uk/ws/portalfiles/portal/65195747/DR2012_12_1_.pdf). And the next time you notice a colleague struggling with a technical problem, be the RSE on their shoulder. Gently remind them:
-
-*Hey, I know how to do that.*
-
-> You are braver than you believe, stronger than you seem, and smarter than you think. A. A. Milne, *Winnie the Pooh*
-
+This month, I had the pleasure of meeting some fellow R users at the Boston R User Group meetup,
+where I can say I finally felt safe opening a conversation with a hot take like, "R is the best," knowing
+it would likely not spark a flame war. I'm sure many of you having read that sentence
+are already compiling the several counterarguments in your head, mashing away your response
+in a text editor, choosing all your best and worst use cases as examples and calling on the
+greats of your respective community to back you up. But this discussion is actually not about flame wars;
+in fact, as I'm sure you've experienced, we as technologists often care less about what tool
+is objectively best, and more about what tool is best for us, our project, and our team.
+
+And while this can sound like a freeing stance on tooling in general, it leaves us with
+an acute conundrum: how do we know when to _switch_ tools? When do we know that the tool we're
+using is no longer best for us, and that we should switch to something else? As computing becomes
+more accessible and capable, more individuals are building tools that avow to _finally_ and
+_decisively_ solve the problem of [insert other tools' shortcomings here]. Indeed, whether it
+was Markdown's attempt to become the de facto standard for writing on the web
+Anaconda claim to be the last word in environment management for data science, or the
+eternal paradox of Apple's latest OS somehow always having "the best feature, ever,"
+technology is rife with shiny toys that promise to solve all our problems. On the one hand, it can be
+incredibly overwhelming trying to keep up with the latest and greatest, and on the other,
+you could easily risk missing out on a tool that could be a game changer for you and your team if
+you don't branch out and experiment from time to time[1^].
+
+This decision fatigue can end up being a significant job hazard for people who work with technology.
+What if your organization is one of the unfortunate few that decided to go all-in on Skype[2^],
+or what if you can't ship a new product or publish a paper because your team has not ported
+over its legacy libraries to Python 3 yet? As RSEs, part of our responsibility is to help
+scientific teams navigate this ever-changing landscape of tools and technologies, and it can
+be very tricky to draw the line between productive experimentation and [shiny toy syndrome](https://nesslabs.com/shiny-toy-syndrome).
+How does one justify several afternoons' worth of tinkering, only to come to the conclusion
+that the new tool actually _doesn't_ do what it says on the box - or at least, not to your satisfaction —
+and continue to be trusted with the responsibility of guiding your team's technological vision?
+
+But as I thought about this more, I realized that this activity of tinkering and experimenting
+with new tools is actually a critical part of our job as RSEs, and that we can turn this "bug"
+of shiny toy syndrome into a "feature" of arrestive curiosity. Arrestive curiosity is the
+tendency to be so curious about new tools and technologies that you cannot move forward with your
+own work until you've proven a new tool is either better or worse for you than the one
+you're currently using[3^]. If you've ever been up late at night trying to get a VSCode extension to
+run without error, trying to figure out why a new library can't just install on your system,
+or drawing out your ultimate note-taking entourage of apps for never losing a thought, I see you!
+This kind of curiosity can be a disastrous time sink — but it can also be a powerful way to
+stay on top of the latest and greatest, and to make sure you're using the best tools for you and your team.
+
+So, how do we cultivate arrestive curiosity without falling into the trap of
+time-wasting? Having wrestled with this for several years, I think I can provide a few
+considerations that have helped me strike this balance:
+
+1. _Stop being distracted by the perfect tool until you know what perfect is supposed to look like._
+Before seriously investigating a new tool, write down exactly
+what problem or need you think it is trying to solve for you. In the simple process of
+articulating this, you may find that your existing workflow just needs some refinement,
+or a simple adjustment or reframing of the problem. 95% of the time, my tinkering does not
+pass this step.
+
+2. _Get comfortable with the discomfort of your current tools._ If you've successfully passed
+the first step, then you know for a fact that your current workflow needs are not being met,
+and a new tool — or repurposing an old one — is likely the solution. But before you dive into the new tool,
+now is the time to measure the discomfort of your current workflow. How much time are you losing to this
+problem? How much mental energy are you spending on it? How much is it costing your team in
+productivity and morale? If the cost of your current workflow is not high enough, then it may
+not be worth the time and effort to switch to a new tool. If you can tolerate the discomfort, then the tool search ends here.
+
+3. _Refine to absurdum._ If you are still convinced that something is missing, then it is time to start
+looking for what is missing. Surely someone has felt this acute pain, right? The internet is a vast place,
+and there are several billion of us using it at any given time. It's more than likely that someone,
+somewhere, has been in the exact position you're in, with an install that is too slow, a link that
+doesn't work, or a workflow that is too clunky and just missing that, _secret something_. Go out into dark
+corners of the second, third, and fourth pages of Google search, ask around on Reddit and Facebook groups, or
+find forums and communities that are relevant to the problem space. Surely **someone** has faced this problem, too?
+
+4. If the solution is identified, use it. If not, build it. By this point, if you have found a
+niche problem that 1) arrests your productivity, 2) causes measurable discomfort, and 3) has not been
+solved by anyone else, then this is a problem worth solving. In fact, as an RSE, this is the _perfect_
+problem to have, because it is within this narrow gap between your vision and the status quo that
+you can actually make valuable impact to your team. If you can't or don't want to build the solution yourself,
+one of two things must be true: either the problem is not worth solving, or you are _not yet_ the right person to solve it.
+
+In my experience, the really interesting Research Software Engineering is what happens when as an
+engineer I have become _obsessed_ with a particular technological blocker to the success of my or my colleagues' scientific endeavors.
+
+It is the moment we look at the scientific engine and say, "I know we _could_ just use [X Tool] to write
+this part of the paper, but I just can't accept that this is the best way to do it. I simply can't. There
+_must_ be a better way."
+
+This is the "arrestive," part of the "arrestive curiosity" — the part that literally keeps you up at night,
+ceases you in your tracks every time you think about it, and continues to consume all of your mental
+energy until you have either found a solution or come to terms with the fact that there is no solution.
+
+And if you ask me, that tendency to be obsessed with finding the best way to do science is what makes a good
+RSE a _great_ RSE. So, the next time you find yourself in the throes of shiny toy syndrome, try to
+channel that energy into arrestive curiosity using the flowchart I outlined above, and see where it takes you.
+You might just find that the perfect tool was right in front of you all along, or you might end up building
+something that changes the game for, your team, and perhaps even the science itself.
+
+[1^]: In fact, at this UseR Boston meetup, we ourselves had a hard time rectifying our excitement
+vs. hesitation around all things AI in the R world. We could barely come to a consensus on
+whether we could be convinced to switch over to the new native pipe `|>` or stick with the beloved
+`magrittr` pipe `%>%` that we've been using for years, all the while doing our best "old man yells at cloud" impression.
+Spoiler alert: I'm yelling at the cloud.
+[2^]: Shout out to everyone currently being held hostage by their CTO's contract with Microsoft and having to wake
+up every morning to the sound of a Teams notification. We see you, and we feel your pain.
+[3^]: Yes, I just came up with it. No, I will not be answering questions.
------------------------------------------------------------------------
\ No newline at end of file
diff --git a/_posts/newsletters/quarto/_news.md b/_posts/newsletters/quarto/_news.md
index 7ca41c102..90b5c0f4e 100644
--- a/_posts/newsletters/quarto/_news.md
+++ b/_posts/newsletters/quarto/_news.md
@@ -22,19 +22,24 @@ consecutive year a Chameleon user has taken home this honor!
Read the announcement [here](https://blog.chameleoncloud.org/posts/sc25-best-reproducibility-advancement-award/).
-### RSE's with a New York State of Mind... 🗽
+> Did you know that we have a community Code of Conduct? Anyone is able to view it in the
+`#code_of_conduct` Slack channel, under `Files`!
-The NYC Regional Group recently met up for their inaugural
-in-person hangout! Special thanks to Roger Ferger for spearheading the event!
-
-
-
+### In Memoriam
-As an added bonus, the group also now has a dedicated page on the US-RSE website! Check it out [here](https://us-rse.org/ag/rg-nyc/) to learn more about the group and how to get involved.
+We mourn the loss of a dear friend and colleague, Cleve Moler, who passed away on May 20, 2026, at the age of 86 at his home
+surrounded by his family. Cleve was chief mathematician and cofounder of MathWorks and the author of the first version of MATLAB.
+Please join us in remembering their contributions to science and engineering by reading Mathworks official announcement [here](https://www.mathworks.com/company/aboutus/founders/clevemoler.html).
+
+## Community Spotlight
+
+🌱 Our community is full of people doing fascinating research and software work, and we want to put a face to it. Starting this month, we'll be featuring a group of different members in a regular spotlight: what they work on, a tool they can't live without, and how they found their way into RSE work.
+
+We'd love to feature YOU. It takes about 5 minutes to fill out, and nothing gets posted without your okay: [https://forms.gle/dXqVsHKiHnot2u449](https://forms.gle/dXqVsHKiHnot2u449)
+
+Email [Pengyin Shan](mailto:pengyins@illinois.edu) for any questions!
-> Did you know that we have a community Code of Conduct? Anyone is able to view it in the
-`#code_of_conduct` Slack channel, under `Files`!
### **Community Calls**
diff --git a/_posts/newsletters/quarto/_preamble.md b/_posts/newsletters/quarto/_preamble.md
index fe220c56e..252a230b5 100644
--- a/_posts/newsletters/quarto/_preamble.md
+++ b/_posts/newsletters/quarto/_preamble.md
@@ -1,10 +1,6 @@
-Well, actually, there are thousands — **four thousand and counting**, to be exact! That's
-right, as of April 2026, US-RSE has grown to over 4,000 registered members! That means if you
-tried to count every member one by one, it would take you [over an hour](https://numbermatics.com/n/4000/) to
-count them all. 4000 is also a Harshad number, which means it's divisible by the sum of its digits (4 + 0 + 0 + 0
-= 4). So, in a way, our membership is mathematically harmonious! Also, did you know
-that the recent Artemis mission flew approximately [4000 miles above the moon's surface](https://science.nasa.gov/solar-system/skywatching/night-sky-network/night-sky-network-celebrates-artemis-ii/)?
-Okay, you get the point — that's a lot of RSEs, and we're thrilled to have each and every one of you as part of our community.
+First of all, Happy Pride Month 🌈, and Happy Juneteenth 🎉! We hope you are all having a wonderful summer celebrating the diversity and resilience of our communities.
-So grab a beverage, sit back, and dive in to the latest news and updates from your
-4000-member-strong community of research software engineers!
\ No newline at end of file
+It's been another busy month for US-RSE, as conference planning continues to ramp up,
+membership continues to grow, and the organization continues to expand its offerings and
+impact to the research software community. In this issue, we'll discuss shiny toy syndrome in
+technology, celebrate the LGBTQ+ community, and share all the latest and greatest news from US-RSE.
\ No newline at end of file
diff --git a/_posts/newsletters/quarto/params.yml b/_posts/newsletters/quarto/params.yml
index fa8bca96b..a514e124b 100644
--- a/_posts/newsletters/quarto/params.yml
+++ b/_posts/newsletters/quarto/params.yml
@@ -1,24 +1,24 @@
layout: post
-title: "US-RSE May 2026 Newsletter"
-subtitle: "🙌 There Are Dozens of Us, DOZENS! 🙌"
+title: "US-RSE June 2026 Newsletter"
+subtitle: "🤔 Arrestive Curiosity & RSEs: How to Turn the Shiny Toy Syndrome Bug into a Feature 🤔"
category: newsletter
-tags: [newsletter, May]
-date: 2026-05-20 00:00:00 -0400
+tags: [newsletter, June]
+date: 2026-06-15 00:00:00 -0400
author: "Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden (Editor)"
-image: "/assets/img/newsletter-202605/us-rse_4k_members.png"
-img_alttext: "Colourful poster with the words \"Celebrating 4,000+ Member Milestone\" and a progression of trees growing from a seedling to a full tree, with the number 4011 prominently displayed."
-next_meeting_date: Friday, June 12, 2026, 12:00PM EST
+image: "/assets/img/newsletter-202606/us-rse_4k_members.png" #TODO
+img_alttext: "Colourful poster with the words \"Celebrating 4,000+ Member Milestone\" and a progression of trees growing from a seedling to a full tree, with the number 4011 prominently displayed." #TODO
+next_meeting_date: Thursday, July 9, 2026, 12:00PM EST #Done
sections:
- preamble: true # done
- headline: true # done
- conference: true # done
- execupdate: false # done
- scupdate: false # yay!
- orgmember: true # done
- communityfunds: false # no changes, check back in june
- news: true # add community call summary
- events: true
- reads: true
+ preamble: true #Done
+ headline: true #Done
+ conference: true #Done
+ execupdate: false #TODO
+ scupdate: false #TODO
+ orgmember: true #TODO
+ communityfunds: false #TODO
+ news: true #TODO
+ events: true #TODO
+ reads: true #TODO
involved: true
jobs: true
diff --git a/_posts/newsletters/quarto/template.md b/_posts/newsletters/quarto/template.md
index 4cd7e5bac..78ce7b556 100644
--- a/_posts/newsletters/quarto/template.md
+++ b/_posts/newsletters/quarto/template.md
@@ -1,11 +1,11 @@
-# US-RSE May 2026 Newsletter
+# US-RSE June 2026 Newsletter
Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden
(Editor)
-2026-05-20
+2026-06-15
-- [1 🤩 Wait a Minute, I’m an
- RSE, I Know How to Do That!
- 🤩](#star_struck-wait-a-minute-im-an-rse-i-know-how-to-do-that-star_struck)
+- [1 🤔 Arrestive Curiosity &
+ RSEs: How to Turn the Shiny Toy Syndrome Bug into a Feature
+ 🤔](#thinking-arrestive-curiosity--rses-how-to-turn-the-shiny-toy-syndrome-bug-into-a-feature-thinking)
- [2 📣 Mark Your Calendars for
USRSE’26! 📣](#mega-mark-your-calendars-for-usrse26-mega)
- [3 🤝 Organizational Founding
@@ -13,194 +13,184 @@ Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden
🤝](#handshake-organizational-founding-membership-handshake)
- [4 🗞️ Community News
🗞️](#newspaper_roll-community-news-newspaper_roll)
-- [5 👀 Interesting Events and
+- [5 Community
+ Spotlight](#community-spotlight)
+- [6 👀 Interesting Events and
Opportunities 👀](#eyes-interesting-events-and-opportunities-eyes)
-- [6 📚 Featured Reads, Videos,
+- [7 📚 Featured Reads, Videos,
and Podcasts 📚](#books-featured-reads-videos-and-podcasts-books)
-- [7 🏃 Get Involved!
+- [8 🏃 Get Involved!
🏃](#running-get-involved-running)
-- [8 🧑💼 Recent Job Postings
+- [9 🧑💼 Recent Job Postings
🧑💼](#office_worker-recent-job-postings-office_worker)
-Well, actually, there are thousands — **four thousand and counting**, to
-be exact! That’s right, as of April 2026, US-RSE has grown to over 4,000
-registered members! That means if you tried to count every member one by
-one, it would take you [over an hour](https://numbermatics.com/n/4000/)
-to count them all. 4000 is also a Harshad number, which means it’s
-divisible by the sum of its digits (4 + 0 + 0 + 0 = 4). So, in a way,
-our membership is mathematically harmonious! Also, did you know that the
-recent Artemis mission flew approximately [4000 miles above the moon’s
-surface](https://science.nasa.gov/solar-system/skywatching/night-sky-network/night-sky-network-celebrates-artemis-ii/)?
-Okay, you get the point — that’s a lot of RSEs, and we’re thrilled to
-have each and every one of you as part of our community.
-
-So grab a beverage, sit back, and dive in to the latest news and updates
-from your 4000-member-strong community of research software engineers!
+First of all, Happy Pride Month 🌈, and Happy Juneteenth 🎉! We hope you
+are all having a wonderful summer celebrating the diversity and
+resilience of our communities.
+
+It’s been another busy month for US-RSE, as conference planning
+continues to ramp up, membership continues to grow, and the organization
+continues to expand its offerings and impact to the research software
+community. In this issue, we’ll discuss shiny toy syndrome in
+technology, celebrate the LGBTQ+ community, and share all the latest and
+greatest news from US-RSE.
-
+
In this issue:
------------------------------------------------------------------------
-## 🤩 Wait a Minute, I’m an RSE, I Know How to Do That! 🤩
+## 🤔 Arrestive Curiosity & RSEs: How to Turn the Shiny Toy Syndrome Bug into a Feature 🤔
-*I know how to do that!*
-
-It is one of the most rewarding thoughts you can have as a research
-software engineer: that moment when you notice a colleague, PI,
-collaborator, or student struggling with a software problem and realize
-you can help.
-
-Not because they are unmotivated. Not because they are bad scientists.
-But because things are not working, not moving quickly enough, or not
-being recognized for what they are: software problems that can be solved
-with the right tools, techniques, and expertise. Maybe the scientist is
-looking toward industry and thinking, “I wish we could move as quickly
-as Google, Facebook, or Microsoft.” Or, more recently, “I wish we could
-figure out how to really use all this LLM stuff.” Ever persistent, the
-scientist keeps chasing their research questions. They want to discover
-the next big thing in their field. They want to make an impact. But
-because their workflow was essentially written in 2012, and because they
-do not have the time, support, or expertise to modernize it, they are
-stuck moving at the pace of 2012.
-
-And as RSEs, we get it! Code can be fragile — and scary. If a new
-student or postdoc touches it, they might break it. If the code breaks,
-so might every paper, grant, and project built on top of it. When was
-the last time it was updated? Months ago? Years ago? So the scientist
-does not touch it. They treat it like a Rube Goldberg machine: they know
-it works, but they no longer remember how. At this point, they are too
-afraid to find out.
-
-As RSEs, we see this…and get excited.
-
-Because we know how to help. 🥹
-
-I first came across the term “RSE” in the wonderfully cute and
-informative 2019 YouTube video, [The Story of the Research
-Engineer](https://www.youtube.com/watch?v=trAfA9VWLTQ), and I instantly
-fell in love with the idea. Here was a name for the squeaky wheel that
-gets the grease: the person who helps scientists get unstuck, move
-faster, and work more sustainably. But then as now, the field was young.
-There was not much consensus about what an RSE was, where they belonged,
-or how institutions should support them.
-
-The term itself emerged in the UK [in
-2012](https://www.software.ac.uk/blog/not-so-brief-history-research-software-engineers-0),
-after a group of researchers and software practitioners began
-formalizing a role that many people were already doing but few
-institutions knew how to recognize. Since then, definitions have been
-proposed, refined, and debated.
-
-Ian Cosden, one of our newsletter editors and Director of *Research
-Software Engineering for Computational & Data Science* at Princeton,
-defines the role partly by what it is not. An RSE, he argues, is not
-simply a researcher, not simply a facilitator, and not simply a pure
-software engineer. The role lives in the productive space between those
-identities.
-
-
-
-
-
-
-
-Goth et al. ([2025](https://f1000research.com/articles/13-1429)) offer
-one recent attempt to concretize the foundational competencies and
-responsibilities of an RSE, including software development, building and
-distributing software assets, understanding the research lifecycle, and
-supporting reproducible, sustainable research. [Vanessa Sochat’s
-EasyBuild talk](https://www.youtube.com/watch?v=FB2yV8TNnSw), on the
-other hand, emphasizes just how broad this space can be: among roughly
-400 people surveyed who identified themselves to be working on “research
-software” in some capacity, there were more than *190 unique job
-titles*. That degree of diversity can be both a strength and a
-challenge. It shows how widely research software work appears across
-institutions, but it also explains why the role can be so difficult to
-define, hire for, promote, and reward. Another one of our US-RSE
-members, Dan Katz, proposes a 3-dimensional schematic to isolate the
-Super RSE role who commands “a superset of the responsibilities of the
-traditional RSE role, combining both service and the RSE’s own
-research.”
-
-
-
-
-
-
-By identifying this RSE unicorn, Katz highlights the fact that as we
-define the breadth of the scope of the RSE, we also need to think about
-its potentially necessary boundaries.
-
-In a 2022 [career Q&A in
-*Nature*](https://www.nature.com/articles/d41586-022-01516-2), Paul
-Richmond predicted that RSEs could become equals in the academic
-environment if they receive proper recognition for their contributions.
-James Schloss, in his [YouTube
-talk](https://www.youtube.com/watch?v=t2BjZ5hSjHo) highlights some of
-the barriers still standing in the way: the publication economy,
-academic resistance to software engineering best practices, and the
-difficulty of competing with industry salaries for people with similar
-technical expertise. In fact, one of my very first suggestions for
-newsletter topics was to discuss the definition of the title “Research
-Software Engineer” itself, and I was told very firmly to avoid the topic
-as much as possible — not because it was inflammatory, but because it
-remains a particularly sensitive topic. While many are strongly attached
-to the name for its truthiness, just as many others are more concerned
-with defining the tasks, responsibilities, and competencies of the role,
-regardless of what it is called, because funding sources will pay a
-great deal of attention to those details.
-
-But friends, there is hope. 🌱
-
-Just as a small group of concerned scientists and software practitioners
-began with an idea, a conversation, and a Google Group, we can continue
-making the role visible at our own institutions. This can be through
-formal titles, clearer career paths, better credit, stronger communities
-of practice, or simply naming the work when we see it as we help
-research software engineering become easier to recognize and harder to
-ignore. This week, celebrate yourself by encouraging your colleagues,
-coworkers, PIs, and students to **make this role visible**. Look around.
-We are once again watching technology change the fabric of research
-itself. Rigorous science, and the software that powers it, cannot afford
-to be left behind. Now more than ever, research needs talented, driven,
-curious technology specialists who can ask new questions, solve
-impossible bugs, push compute clusters to their limits, and preserve the
-code — and the science — that so many people depend on.
-
-Our Executive Director had this to say about the importance of this
-community:
-
-“Reaching more than 4,000 members is not just a milestone in numbers -
-it reflects a growing community of people who care deeply about
-advancing research through software, collaboration, and support for one
-another. As Executive Director, I am incredibly grateful to be part of
-this community and inspired every day by the generosity, expertise, and
-passion our members bring to US-RSE. Thank you for helping build a place
-where research software engineers can truly belong.”
-
-> [Sandra](https://us-rse.org/about/staff/)
-
-This month, we thank the scrappy and passionate group of researchers who
-helped crystallize the idea of the Research Software Engineer, [one
-quiet afternoon in Oxford, UK, in
-2012](https://www.pure.ed.ac.uk/ws/portalfiles/portal/65195747/DR2012_12_1_.pdf).
-And the next time you notice a colleague struggling with a technical
-problem, be the RSE on their shoulder. Gently remind them:
-
-*Hey, I know how to do that.*
-
-> You are braver than you believe, stronger than you seem, and smarter
-> than you think. A. A. Milne, *Winnie the Pooh*
-
-------------------------------------------------------------------------
+This month, I had the pleasure of meeting some fellow R users at the
+Boston R User Group meetup, where I can say I finally felt safe opening
+a conversation with a hot take like, “R is the best,” knowing it would
+likely not spark a flame war. I’m sure many of you having read that
+sentence are already compiling the several counterarguments in your
+head, mashing away your response in a text editor, choosing all your
+best and worst use cases as examples and calling on the greats of your
+respective community to back you up. But this discussion is actually not
+about flame wars; in fact, as I’m sure you’ve experienced, we as
+technologists often care less about what tool is objectively best, and
+more about what tool is best for us, our project, and our team.
+
+And while this can sound like a freeing stance on tooling in general, it
+leaves us with an acute conundrum: how do we know when to *switch*
+tools? When do we know that the tool we’re using is no longer best for
+us, and that we should switch to something else? As computing becomes
+more accessible and capable, more individuals are building tools that
+avow to *finally* and *decisively* solve the problem of \[insert other
+tools’ shortcomings here\]. Indeed, whether it was Markdown’s attempt to
+become the de facto standard for writing on the web Anaconda claim to be
+the last word in environment management for data science, or the eternal
+paradox of Apple’s latest OS somehow always having “the best feature,
+ever,” technology is rife with shiny toys that promise to solve all our
+problems. On the one hand, it can be incredibly overwhelming trying to
+keep up with the latest and greatest, and on the other, you could easily
+risk missing out on a tool that could be a game changer for you and your
+team if you don’t branch out and experiment from time to
+time[1^](In%20fact,%20at%20this%20UseR%20Boston%20meetup,%20we%20ourselves%20had%20a%20hard%20time%20rectifying%20our%20excitement).
+
+This decision fatigue can end up being a significant job hazard for
+people who work with technology. What if your organization is one of the
+unfortunate few that decided to go all-in on Skype\[2^\], or what if you
+can’t ship a new product or publish a paper because your team has not
+ported over its legacy libraries to Python 3 yet? As RSEs, part of our
+responsibility is to help scientific teams navigate this ever-changing
+landscape of tools and technologies, and it can be very tricky to draw
+the line between productive experimentation and [shiny toy
+syndrome](https://nesslabs.com/shiny-toy-syndrome). How does one justify
+several afternoons’ worth of tinkering, only to come to the conclusion
+that the new tool actually *doesn’t* do what it says on the box - or at
+least, not to your satisfaction — and continue to be trusted with the
+responsibility of guiding your team’s technological vision?
+
+But as I thought about this more, I realized that this activity of
+tinkering and experimenting with new tools is actually a critical part
+of our job as RSEs, and that we can turn this “bug” of shiny toy
+syndrome into a “feature” of arrestive curiosity. Arrestive curiosity is
+the tendency to be so curious about new tools and technologies that you
+cannot move forward with your own work until you’ve proven a new tool is
+either better or worse for you than the one you’re currently
+using\[3^\]. If you’ve ever been up late at night trying to get a VSCode
+extension to run without error, trying to figure out why a new library
+can’t just install on your system, or drawing out your ultimate
+note-taking entourage of apps for never losing a thought, I see you!
+This kind of curiosity can be a disastrous time sink — but it can also
+be a powerful way to stay on top of the latest and greatest, and to make
+sure you’re using the best tools for you and your team.
+
+So, how do we cultivate arrestive curiosity without falling into the
+trap of time-wasting? Having wrestled with this for several years, I
+think I can provide a few considerations that have helped me strike this
+balance:
+
+1. *Stop being distracted by the perfect tool until you know what
+ perfect is supposed to look like.* Before seriously investigating a
+ new tool, write down exactly what problem or need you think it is
+ trying to solve for you. In the simple process of articulating this,
+ you may find that your existing workflow just needs some refinement,
+ or a simple adjustment or reframing of the problem. 95% of the time,
+ my tinkering does not pass this step.
+
+2. *Get comfortable with the discomfort of your current tools.* If
+ you’ve successfully passed the first step, then you know for a fact
+ that your current workflow needs are not being met, and a new tool —
+ or repurposing an old one — is likely the solution. But before you
+ dive into the new tool, now is the time to measure the discomfort of
+ your current workflow. How much time are you losing to this problem?
+ How much mental energy are you spending on it? How much is it
+ costing your team in productivity and morale? If the cost of your
+ current workflow is not high enough, then it may not be worth the
+ time and effort to switch to a new tool. If you can tolerate the
+ discomfort, then the tool search ends here.
+
+3. *Refine to absurdum.* If you are still convinced that something is
+ missing, then it is time to start looking for what is missing.
+ Surely someone has felt this acute pain, right? The internet is a
+ vast place, and there are several billion of us using it at any
+ given time. It’s more than likely that someone, somewhere, has been
+ in the exact position you’re in, with an install that is too slow, a
+ link that doesn’t work, or a workflow that is too clunky and just
+ missing that, *secret something*. Go out into dark corners of the
+ second, third, and fourth pages of Google search, ask around on
+ Reddit and Facebook groups, or find forums and communities that are
+ relevant to the problem space. Surely **someone** has faced this
+ problem, too?
+
+4. If the solution is identified, use it. If not, build it. By this
+ point, if you have found a niche problem that 1) arrests your
+ productivity, 2) causes measurable discomfort, and 3) has not been
+ solved by anyone else, then this is a problem worth solving. In
+ fact, as an RSE, this is the *perfect* problem to have, because it
+ is within this narrow gap between your vision and the status quo
+ that you can actually make valuable impact to your team. If you
+ can’t or don’t want to build the solution yourself, one of two
+ things must be true: either the problem is not worth solving, or you
+ are *not yet* the right person to solve it.
+
+In my experience, the really interesting Research Software Engineering
+is what happens when as an engineer I have become *obsessed* with a
+particular technological blocker to the success of my or my colleagues’
+scientific endeavors.
+
+It is the moment we look at the scientific engine and say, “I know we
+*could* just use \[X Tool\] to write this part of the paper, but I just
+can’t accept that this is the best way to do it. I simply can’t. There
+*must* be a better way.”
+
+This is the “arrestive,” part of the “arrestive curiosity” — the part
+that literally keeps you up at night, ceases you in your tracks every
+time you think about it, and continues to consume all of your mental
+energy until you have either found a solution or come to terms with the
+fact that there is no solution.
+
+And if you ask me, that tendency to be obsessed with finding the best
+way to do science is what makes a good RSE a *great* RSE. So, the next
+time you find yourself in the throes of shiny toy syndrome, try to
+channel that energy into arrestive curiosity using the flowchart I
+outlined above, and see where it takes you. You might just find that the
+perfect tool was right in front of you all along, or you might end up
+building something that changes the game for, your team, and perhaps
+even the science itself.
+
+vs. hesitation around all things AI in the R world. We could barely come
+to a consensus on whether we could be convinced to switch over to the
+new native pipe `|>` or stick with the beloved `magrittr` pipe `%>%`
+that we’ve been using for years, all the while doing our best “old man
+yells at cloud” impression. Spoiler alert: I’m yelling at the cloud.
+\[2^\]: Shout out to everyone currently being held hostage by their
+CTO’s contract with Microsoft and having to wake up every morning to the
+sound of a Teams notification. We see you, and we feel your pain.
+\[3^\]: Yes, I just came up with it. No, I will not be answering
+questions. ————————————————————————
## 📣 Mark Your Calendars for USRSE’26! 📣
@@ -297,7 +287,6 @@ interested in becoming an organizational founding member!
{% for org in site.data.org-members.standard %}
- [{{ org.name }}]({{ org.url }})
-- [Flatiron Institute](https://www.simonsfoundation.org/flatiron/)
{% endfor %}
@@ -338,22 +327,32 @@ has taken home this honor!
Read the announcement
[here](https://blog.chameleoncloud.org/posts/sc25-best-reproducibility-advancement-award/).
-### RSE’s with a New York State of Mind… 🗽
+> Did you know that we have a community Code of Conduct? Anyone is able
+> to view it in the `#code_of_conduct` Slack channel, under `Files`!
+
+### In Memoriam
-The NYC Regional Group recently met up for their inaugural in-person
-hangout! Special thanks to Roger Ferger for spearheading the event!
+We mourn the loss of a dear friend and colleague, Cleve Moler, who
+passed away on May 20, 2026, at the age of 86 at his home surrounded by
+his family. Cleve was chief mathematician and cofounder of MathWorks and
+the author of the first version of MATLAB. Please join us in remembering
+their contributions to science and engineering by reading Mathworks
+official announcement
+[here](https://www.mathworks.com/company/aboutus/founders/clevemoler.html).
-
+## Community Spotlight
-
-
+🌱 Our community is full of people doing fascinating research and
+software work, and we want to put a face to it. Starting this month,
+we’ll be featuring a group of different members in a regular spotlight:
+what they work on, a tool they can’t live without, and how they found
+their way into RSE work.
-As an added bonus, the group also now has a dedicated page on the US-RSE
-website! Check it out [here](https://us-rse.org/ag/rg-nyc/) to learn
-more about the group and how to get involved.
+We’d love to feature YOU. It takes about 5 minutes to fill out, and
+nothing gets posted without your okay:
+
-> Did you know that we have a community Code of Conduct? Anyone is able
-> to view it in the `#code_of_conduct` Slack channel, under `Files`!
+Email [Pengyin Shan](mailto:pengyins@illinois.edu) for any questions!
### **Community Calls**
@@ -369,8 +368,8 @@ more about the group and how to get involved.
-->
-Our next meeting is scheduled for Friday, June 12, 2026, 12:00PM EST. We
-hope to see you there!
+Our next meeting is scheduled for Thursday, July 9, 2026, 12:00PM EST.
+We hope to see you there!
------------------------------------------------------------------------
From 7e87724b04db3b8310a00c4a2dfb9cafefa22a0d Mon Sep 17 00:00:00 2001
From: github-actions
Date: Tue, 16 Jun 2026 06:34:57 +0000
Subject: [PATCH 02/11] Automated push to update jobs files 2026-06-16
---
_data/jobs.yml | 5 -----
1 file changed, 5 deletions(-)
diff --git a/_data/jobs.yml b/_data/jobs.yml
index e5df609db..96766198d 100644
--- a/_data/jobs.yml
+++ b/_data/jobs.yml
@@ -53,11 +53,6 @@
name: Software Engineer (Astropy)
posted: 2026-04-09
url: https://apply.interfolio.com/184639
-- expires: 2026-04-16
- location: Laboratory for Atmospheric and Space Physics, CU Boulder, Boulder, CO
- name: Data Systems Team Lead
- posted: 2026-04-02
- url: https://jobs.colorado.edu/jobs/JobDetail/Data-Systems-Team-Lead/71009
- expires: 2026-05-01
location: Science & Technology Corp (STC), Greenbelt, MD / remote
name: Support Scientist
From 586b2c9f2f065f06f5d7a260ad1dba72ba2165a0 Mon Sep 17 00:00:00 2001
From: TinasheMTapera <15770644+TinasheMTapera@users.noreply.github.com>
Date: Tue, 16 Jun 2026 12:22:31 -0400
Subject: [PATCH 03/11] edits
---
_data/newsletter-events-opportunities.yml | 10 ---
_data/newsletter_bib.bib | 55 +++++++++++++++-
_data/newsletter_bib_yml.yml | 61 +++++++++++++++++-
_posts/newsletters/2026-06-15-newsletter.md | 22 ++++---
_posts/newsletters/quarto/_headline.md | 5 +-
_posts/newsletters/quarto/params.yml | 4 +-
_posts/newsletters/quarto/template.md | 18 +++---
.../tasha-kostyuk-TtMKq3lJm-U-unsplash.jpg | Bin 0 -> 2295028 bytes
8 files changed, 137 insertions(+), 38 deletions(-)
create mode 100644 assets/img/newsletter-202506/tasha-kostyuk-TtMKq3lJm-U-unsplash.jpg
diff --git a/_data/newsletter-events-opportunities.yml b/_data/newsletter-events-opportunities.yml
index a78a36a43..c557e532f 100644
--- a/_data/newsletter-events-opportunities.yml
+++ b/_data/newsletter-events-opportunities.yml
@@ -537,13 +537,3 @@
In addition, the PESO project is going to start an occasional UX newsletter that will include some resources on conducting UX research and ensuring usability/positive UX. If you have UX resources that should be highlighted as the newsletter launches, please reach out to the `wg-ux` channel!
links: |
PESO Project website: [Click here](https://pesoproject.org/)
-
-- expires: 2026-08-01
- type: opportunity
- title: Call for Papers - High-Productivity Programming Systems for HPC Applications (IJPP)
- preamble: |
- In the ever-evolving world of computing, the line between software and hardware has become increasingly larger. As we push the boundaries of what is possible with technology, the need for high-productivity programming solutions that can harness the power of modern hardware has never been more critical.
- This Special Issue (SI) aims to bring points of discussion into the High-performance Computing (HPC) and scientific community about key issues on finding a compromise between high levels of abstraction (programming productivity) and meeting the challenges of performance, power consumption, and fault tolerance. This SI addresses the recent experiences in programming languages/models design for exa-scale computing systems, which can contribute to the problem of programming complex HPC systems in a productive, efficient, and reliable way. This SI provides a great opportunity for the HPC community to present new approaches for exploiting the massive parallelism that is provided by the abundance of different kinds of parallelism in today's and future HPC systems. Besides the conventional use for coarse or fine-grain parallelism in applications, our scope is to explore new approaches that enable future software systems to become more self-aware, reasoning about its internal state, and making decisions to prioritize changes in the execution of applications when necessary, putting the focus on areas such as performance tuning and power management.
- links: |
- Submission Deadline (extended): August 30, 2026. See [here](https://link.springer.com/journal/10766/updates/27768048) for more information on the journal and submission process.
-
diff --git a/_data/newsletter_bib.bib b/_data/newsletter_bib.bib
index a59dc9370..9c0856e87 100644
--- a/_data/newsletter_bib.bib
+++ b/_data/newsletter_bib.bib
@@ -221,6 +221,7 @@ @article{cosdenDesigningImplementingComprehensive2026
@online{CrankGPTLocalHumanpowered,
title = {{{CrankGPT}} — {{Local Human-powered AI}}},
+ author = {Squeez Labs},
url = {https://crankgpt.com/},
urldate = {2026-06-16},
abstract = {A human-powered, fully local, fully private AI solution.},
@@ -275,6 +276,22 @@ @article{dicosmoStopTreatingCode2025
file = {/Users/tit420/Zotero/storage/ZDISSPC7/d41586-025-03196-0.html}
}
+@video{DoesSpecDrivenDevelopment2026,
+ entrysubtype = {video},
+ title = {[{{EN}}] {{Does Spec-Driven Development}} Replace Agile? {{With Graham Lee}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{Does Spec-Driven Development}} Replace Agile?},
+ namea = {Schmidt, Peter},
+ nameatype = {collaborator},
+ date = {2026-06-02},
+ url = {https://codeforthought.buzzsprout.com/1326658/episodes/19163979-en-does-spec-driven-development-replace-agile-with-graham-lee},
+ urldate = {2026-06-16},
+ abstract = {English Edition: Will spec-driven development replace agile processes? My guest Graham Lee\ (https://chironcodex.com/ ) and I discuss if there is still a place for agile software engineering in a world of AI assisted coding.Links:https://mart...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/QWCZ298A/19163979-en-does-spec-driven-development-replace-agile-with-graham-lee.html}
+}
+
@report{druskatResearchSoftwareEngineers2026,
title = {Research {{Software Engineers}} in the {{Age}} of {{GenAI}}: {{Same Value}}, {{Changing Practice}}},
shorttitle = {Research {{Software Engineers}} in the {{Age}} of {{GenAI}}},
@@ -623,6 +640,7 @@ @book{ramanathanIntroductionNeuromorphicComputing2025
@online{RealScorelineReveals,
title = {The {{Real Scoreline}} Reveals Nations Facing Climate Penalties - {{University}} of {{Reading}}},
+ author = {The University of Reading},
url = {https://www.reading.ac.uk/news/2026/University-News/The-Real-Scoreline-reveals-nations-facing-climate-penalties},
urldate = {2026-06-16},
annotation = {Read\_Status: To Read\\
@@ -836,15 +854,15 @@ @report{teranishiS4PSTStewardshipAdvancement2026
@online{udellHowMakeBest2026,
title = {How to Make Best Use of Git and {{GitHub}} for {{AI-assisted}} Software Development},
- author = {Udell, \textasciitilde{} Jon},
+ author = {Udell, Jon},
date = {2026-06-02T19:41:11+00:00},
url = {https://blog.jonudell.net/2026/06/02/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development/},
urldate = {2026-06-16},
abstract = {I’m working on a new tool whose tagline is the title of this post: Make best use of git and GitHub for AI-assisted software development. Called Bram (“Bram runs agents mindfully”)…},
langid = {american},
- organization = {Jon Udell},
+ organization = {How to make best use of git and GitHub for AI-assisted software development},
annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-06-16T01:04:20.126Z},
+Read\_Status\_Date: 2026-06-16T16:18:22.799Z},
file = {/Users/tit420/Zotero/storage/74BXFIZD/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development.html}
}
@@ -861,3 +879,34 @@ @online{UnderstandingAdvancingResearch2025
Read\_Status\_Date: 2026-03-16T02:12:49.786Z},
file = {/Users/tit420/Zotero/storage/UVZXHIQE/v1.html}
}
+
+@video{WhatHappenedAgile2026,
+ entrysubtype = {video},
+ title = {[{{EN}}] {{What}} Happened to Agile Development? - {{A}} Review with {{Dave Thomas}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{What}} Happened to Agile Development?},
+ namea = {Schmidt, Peter},
+ nameatype = {collaborator},
+ date = {2026-06-16},
+ url = {https://www.buzzsprout.com/1326658/episodes/19292687-en-what-happened-to-agile-development-a-review-with-dave-thomas},
+ urldate = {2026-06-16},
+ abstract = {English Edition:\ I want to come back to agile development practices with my guest Dave Thomas, or Pragmatic Dave as he is also known in the trade. Dave is one of the authors of the manifesto for agile development - and we talk about what has ...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/NBJV5ZD6/19292687-en-what-happened-to-agile-development-a-review-with-dave-thomas.html}
+}
+
+@video{WhenBitsRot2026,
+ entrysubtype = {video},
+ title = {[{{EN}}] {{When Bits Rot}} - with {{C McKean}}, {{L Talboom}}, {{A Page-Mitchell}} - {{Code}} for {{Thought}}},
+ namea = {Schmidt, Peter},
+ nameatype = {collaborator},
+ date = {2026-06-09},
+ url = {https://codeforthought.buzzsprout.com/1326658/episodes/19221837-en-when-bits-rot-with-c-mckean-l-talboom-a-page-mitchell},
+ urldate = {2026-06-16},
+ abstract = {English Edition: floppy disks, hard drives, CDs, DVDs, SSD drives - no matter what you choose to store your data on - ultimately they all decay. With my guests Callum McKean, Leontien Talboom and Adrian Page-Mitchell, we're going to talk about wha...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/YGL4ZLC9/19221837-en-when-bits-rot-with-c-mckean-l-talboom-a-page-mitchell.html}
+}
diff --git a/_data/newsletter_bib_yml.yml b/_data/newsletter_bib_yml.yml
index dafa37b78..bae57911a 100644
--- a/_data/newsletter_bib_yml.yml
+++ b/_data/newsletter_bib_yml.yml
@@ -433,6 +433,9 @@ references:
annote: |
Read_Status: To Read\
Read_Status_Date: 2026-06-16T01:04:20.125Z
+ author:
+ - family: Labs
+ given: Squeez
id: CrankGPTLocalHumanpowered
language: en-US
title: CrankGPT --- [Local Human-powered AI]{.nocase}
@@ -531,6 +534,22 @@ references:
type: article-journal
url: "https://www.nature.com/articles/d41586-025-03196-0"
volume: 646
+- abstract: "English Edition: Will spec-driven development replace agile
+ processes? My guest Graham Lee\\ (https://chironcodex.com/ )
+ and I discuss if there is still a place for agile software
+ engineering in a world of AI assisted coding.Links:https://mart\\..."
+ accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T16:05:28.241Z
+ id: DoesSpecDrivenDevelopment2026
+ issued: 2026-06-02
+ language: en-US
+ title: \[EN\] Does Spec-Driven Development replace agile? With Graham
+ Lee - Code for Thought
+ title-short: \[EN\] Does Spec-Driven Development replace agile?
+ type: motion_picture
+ url: "https://codeforthought.buzzsprout.com/1326658/episodes/19163979-en-does-spec-driven-development-replace-agile-with-graham-lee"
- abstract: Research software and its creators have long played a
critical role in the advancement of research worldwide. This role is
changing in the age of "generative AI" (GenAI), but both the
@@ -1246,6 +1265,10 @@ references:
annote: |
Read_Status: To Read\
Read_Status_Date: 2026-06-16T01:04:20.125Z
+ author:
+ - dropping-particle: of
+ family: Reading
+ given: The University
id: RealScorelineReveals
title: The Real Scoreline reveals nations facing climate penalties -
University of Reading
@@ -1610,14 +1633,15 @@ references:
accessed: 2026-06-16
annote: |
Read_Status: To Read\
- Read_Status_Date: 2026-06-16T01:04:20.126Z
+ Read_Status_Date: 2026-06-16T16:18:22.799Z
author:
- family: Udell
- given: \~ Jon
+ given: Jon
id: udellHowMakeBest2026
issued: 2026-06-02
language: en-US
- publisher: Jon Udell
+ publisher: How to make best use of git; GitHub for AI-assisted
+ software development
title: How to make best use of git and GitHub for
[AI-assisted]{.nocase} software development
type: webpage
@@ -1637,5 +1661,36 @@ references:
models
type: webpage
url: "https://open-research-europe.ec.europa.eu/articles/5-199/v1"
+- abstract: "English Edition:\\ I want to come back to agile
+ development practices with my guest Dave Thomas, or Pragmatic Dave
+ as he is also known in the trade. Dave is one of the authors of the
+ manifesto for agile development - and we talk about what has \\..."
+ accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T16:05:28.241Z
+ id: WhatHappenedAgile2026
+ issued: 2026-06-16
+ language: en-US
+ title: \[EN\] What happened to agile development? - A review with Dave
+ Thomas - Code for Thought
+ title-short: \[EN\] What happened to agile development?
+ type: motion_picture
+ url: "https://www.buzzsprout.com/1326658/episodes/19292687-en-what-happened-to-agile-development-a-review-with-dave-thomas"
+- abstract: "English Edition: floppy disks, hard drives, CDs, DVDs, SSD
+ drives - no matter what you choose to store your data on -
+ ultimately they all decay. With my guests Callum McKean, Leontien
+ Talboom and Adrian Page-Mitchell, we're going to talk about wha\\..."
+ accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T16:05:28.241Z
+ id: WhenBitsRot2026
+ issued: 2026-06-09
+ language: en-US
+ title: \[EN\] When Bits Rot - with C McKean, L Talboom, A
+ Page-Mitchell - Code for Thought
+ type: motion_picture
+ url: "https://codeforthought.buzzsprout.com/1326658/episodes/19221837-en-when-bits-rot-with-c-mckean-l-talboom-a-page-mitchell"
---
diff --git a/_posts/newsletters/2026-06-15-newsletter.md b/_posts/newsletters/2026-06-15-newsletter.md
index ff651f0cb..d1a3fe747 100644
--- a/_posts/newsletters/2026-06-15-newsletter.md
+++ b/_posts/newsletters/2026-06-15-newsletter.md
@@ -6,8 +6,8 @@ category: newsletter
tags: [newsletter, June]
date: 2026-06-15 00:00:00 -0400
author: "Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden (Editor)"
-image: "/assets/img/newsletter-202606/us-rse_4k_members.png" #TODO
-img_alttext: "Colourful poster with the words \"Celebrating 4,000+ Member Milestone\" and a progression of trees growing from a seedling to a full tree, with the number 4011 prominently displayed." #TODO
+image: "/assets/img/newsletter-202606/tasha-kostyuk-TtMKq3lJm-U-unsplash.jpg" #Done
+img_alttext: "A railway traffic controller with his back to the camera, looking at several screens with train camera feed and data." #Done
next_meeting_date: Thursday, July 9, 2026, 12:00PM EST #Done
sections:
preamble: true #Done
@@ -39,7 +39,7 @@ technology, celebrate the LGBTQ+ community, and share all the latest and
greatest news from US-RSE.
-
+
In this issue:
@@ -188,11 +188,11 @@ It is the moment we look at the scientific engine and say, “I know we
can’t accept that this is the best way to do it. I simply can’t. There
*must* be a better way.”
-This is the “arrestive,” part of the “arrestive curiosity” — the part
-that literally keeps you up at night, ceases you in your tracks every
-time you think about it, and continues to consume all of your mental
-energy until you have either found a solution or come to terms with the
-fact that there is no solution.
+This is the “arrestive,” part of “arrestive curiosity” — the part that
+keeps you up at night, ceases you in your tracks every time you think
+about it, and continues to consume all of your mental energy until you
+have either found a solution or come to terms with the fact that there
+is no solution.
And if you ask me, that tendency to be obsessed with finding the best
way to do science is what makes a good RSE a *great* RSE. So, the next
@@ -200,7 +200,7 @@ time you find yourself in the throes of shiny toy syndrome, try to
channel that energy into arrestive curiosity using the flowchart I
outlined above, and see where it takes you. You might just find that the
perfect tool was right in front of you all along, or you might end up
-building something that changes the game for, your team, and perhaps
+building something that changes the game for you, your team, and perhaps
even the science itself.
vs. hesitation around all things AI in the R world. We could barely come
@@ -212,7 +212,9 @@ yells at cloud” impression. Spoiler alert: I’m yelling at the cloud.
CTO’s contract with Microsoft and having to wake up every morning to the
sound of a Teams notification. We see you, and we feel your pain.
\[3^\]: Yes, I just came up with it. No, I will not be answering
-questions. ————————————————————————
+questions.
+
+------------------------------------------------------------------------
## 📣 Mark Your Calendars for USRSE’26! 📣
diff --git a/_posts/newsletters/quarto/_headline.md b/_posts/newsletters/quarto/_headline.md
index 753c6627c..48f7586d2 100644
--- a/_posts/newsletters/quarto/_headline.md
+++ b/_posts/newsletters/quarto/_headline.md
@@ -86,7 +86,7 @@ It is the moment we look at the scientific engine and say, "I know we _could_ ju
this part of the paper, but I just can't accept that this is the best way to do it. I simply can't. There
_must_ be a better way."
-This is the "arrestive," part of the "arrestive curiosity" — the part that literally keeps you up at night,
+This is the "arrestive," part of "arrestive curiosity" — the part that keeps you up at night,
ceases you in your tracks every time you think about it, and continues to consume all of your mental
energy until you have either found a solution or come to terms with the fact that there is no solution.
@@ -94,7 +94,7 @@ And if you ask me, that tendency to be obsessed with finding the best way to do
RSE a _great_ RSE. So, the next time you find yourself in the throes of shiny toy syndrome, try to
channel that energy into arrestive curiosity using the flowchart I outlined above, and see where it takes you.
You might just find that the perfect tool was right in front of you all along, or you might end up building
-something that changes the game for, your team, and perhaps even the science itself.
+something that changes the game for you, your team, and perhaps even the science itself.
[1^]: In fact, at this UseR Boston meetup, we ourselves had a hard time rectifying our excitement
vs. hesitation around all things AI in the R world. We could barely come to a consensus on
@@ -104,4 +104,5 @@ Spoiler alert: I'm yelling at the cloud.
[2^]: Shout out to everyone currently being held hostage by their CTO's contract with Microsoft and having to wake
up every morning to the sound of a Teams notification. We see you, and we feel your pain.
[3^]: Yes, I just came up with it. No, I will not be answering questions.
+
------------------------------------------------------------------------
\ No newline at end of file
diff --git a/_posts/newsletters/quarto/params.yml b/_posts/newsletters/quarto/params.yml
index a514e124b..c0abd38b2 100644
--- a/_posts/newsletters/quarto/params.yml
+++ b/_posts/newsletters/quarto/params.yml
@@ -5,8 +5,8 @@ category: newsletter
tags: [newsletter, June]
date: 2026-06-15 00:00:00 -0400
author: "Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden (Editor)"
-image: "/assets/img/newsletter-202606/us-rse_4k_members.png" #TODO
-img_alttext: "Colourful poster with the words \"Celebrating 4,000+ Member Milestone\" and a progression of trees growing from a seedling to a full tree, with the number 4011 prominently displayed." #TODO
+image: "/assets/img/newsletter-202606/tasha-kostyuk-TtMKq3lJm-U-unsplash.jpg" #Done
+img_alttext: "A railway traffic controller with his back to the camera, looking at several screens with train camera feed and data." #Done
next_meeting_date: Thursday, July 9, 2026, 12:00PM EST #Done
sections:
preamble: true #Done
diff --git a/_posts/newsletters/quarto/template.md b/_posts/newsletters/quarto/template.md
index 78ce7b556..125a0ba4e 100644
--- a/_posts/newsletters/quarto/template.md
+++ b/_posts/newsletters/quarto/template.md
@@ -38,7 +38,7 @@ technology, celebrate the LGBTQ+ community, and share all the latest and
greatest news from US-RSE.
-
+
In this issue:
@@ -166,11 +166,11 @@ It is the moment we look at the scientific engine and say, “I know we
can’t accept that this is the best way to do it. I simply can’t. There
*must* be a better way.”
-This is the “arrestive,” part of the “arrestive curiosity” — the part
-that literally keeps you up at night, ceases you in your tracks every
-time you think about it, and continues to consume all of your mental
-energy until you have either found a solution or come to terms with the
-fact that there is no solution.
+This is the “arrestive,” part of “arrestive curiosity” — the part that
+keeps you up at night, ceases you in your tracks every time you think
+about it, and continues to consume all of your mental energy until you
+have either found a solution or come to terms with the fact that there
+is no solution.
And if you ask me, that tendency to be obsessed with finding the best
way to do science is what makes a good RSE a *great* RSE. So, the next
@@ -178,7 +178,7 @@ time you find yourself in the throes of shiny toy syndrome, try to
channel that energy into arrestive curiosity using the flowchart I
outlined above, and see where it takes you. You might just find that the
perfect tool was right in front of you all along, or you might end up
-building something that changes the game for, your team, and perhaps
+building something that changes the game for you, your team, and perhaps
even the science itself.
vs. hesitation around all things AI in the R world. We could barely come
@@ -190,7 +190,9 @@ yells at cloud” impression. Spoiler alert: I’m yelling at the cloud.
CTO’s contract with Microsoft and having to wake up every morning to the
sound of a Teams notification. We see you, and we feel your pain.
\[3^\]: Yes, I just came up with it. No, I will not be answering
-questions. ————————————————————————
+questions.
+
+------------------------------------------------------------------------
## 📣 Mark Your Calendars for USRSE’26! 📣
diff --git a/assets/img/newsletter-202506/tasha-kostyuk-TtMKq3lJm-U-unsplash.jpg b/assets/img/newsletter-202506/tasha-kostyuk-TtMKq3lJm-U-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04cc6faf0474ed5ab1a1f1752df184405cb3172d
GIT binary patch
literal 2295028
zcmbTd2Ut_x_BVJE2qhpjpderbln&Ab1Ve8Ep?8qpLAoGd#D<{>3P=w>$mFO`7`zB1H`1KrK<(O;4nxBe4sxc
z>8*6t)g7@WMq0X8G$9xag6MUwc=-pwnIOo|KP1RRTMcbxZG)yBfZz}mmUeXub^-Jq
zK>LP=TqE~?1vJXphfKpM$#f8SKtP`&(;ok#MgNZZ7mXp)u73WmU<~=0uetiUlIb^q
zjtdKQ12n}IK;H}VatjCa7@+xmL;bt}{R7Y_KR2gf2%@AX_lLN-cmnzYpy`9mOw<8=
z34&$rvcx`l*@VVzujoPu1@
z>H&V&octpo=wI(lJ_}+Y^A-)5EGMZTCnqK)4%q)c?SFaje@6YU39@YeHDbs3ugqZV
z{r~Cv&$<8U3n+x3i+g}K5C7BWoC!hAcOmH1%zyg$2@u412ZEXg|Lc9&$$0S$3Av^y
zArT%PF7D;#B2H%L|Fr+t0sk}d|C#u&`-zk9_dmQtYq+^Ph5Ck|$xL+#@C^tJLI+=S
za&be8{og_SzkT9=J=T9chp360yIYW(Ke&|zK$(}n2N1Wvt5=9ufIr&H|NlwC|C^`%
z*E5jGf8iPsti`_}l%qJrG>C#IKJ`PCtaK2CT^=|B`yaVop|ya>nrC@t?O(VDG&ufu
z`+wQMlff=L*vkV=?p8N3L%W0qg^_8X6XXp7LPCrX3gUoxAU;SC5`&~5c}NMuK$?&q
zWCWQ(){q0_0(nAyP!JRjMM1Zqdr&;|5K4oxpnRwpDu-&IdZ-y{hh9Q&p+0B`8i!_~
z56}v<1$~9~p`S1qj2dOHtAn+`Uc!1{!?0=CB5VWp9d-n#fYZZKaBlc{xCHznTotYlH-p>5J>Y@x
zNcbIi68s6g5MBjug1?0K!N=hr;9KxL3W$P^f}P?lg&4&}3Uvx23L6S{iXe&@3Oq$R
zMIl8EMJvTSicyLW6x$SslvI?glxRvZN+n7iN^?pV%0S8($^^b`5w#O_2=zVcOzJA?7t|xvE7U(|=xEN+NYQA~*wFaX
z#L}eGRM2$NjL@vn{G?@~Jx8lZYeefx8$p{)TTI(ZJ4m}i`xD8G6hJB?&5+*6TgWHK
z8e|u84!J`|N5@O2Kxa(nMTet%Lid!en{JWrke-EJm|mUUjy{w=iN1{fANpzfof9Wc
zoIim%VRItnMAC`!6R%G!ocO`O${^05%izjzlOda-iD87{Gb1hIIYw1R2gXRobjAk8
zLB?$+TBh?%>P${dF-+M^EliV4d(5oNlFUZTe#{BX70f-%>nzkP=UFsaTv_h06tTQ!
zSz@JNhRuTQI$Jhd2ipgB3ik8t
zy6nE}$?Wy)6YNJPxlgK|bUXRrWX;KulLx0xpTeASJB2@0dusgD5eJ$>lf#E2g`=5c
zo|BSOnA4auoHLKJi*x%l>a@~nm(%#u^`~dJ;9SC7CR{hTin#i@_PBYtwYjfxXL7&h
z-sWNF!SHzVJm%@-**L>`M&*pxna5{doY_RPp;gho=qKnm=&xtF&gz^EJzH>g;OtLc
z0bX<7Sl(LRc|IiHMLu`F$9%8&zVe^pH{g%rujHROM|?UlETLZx;V7!7pJWks|R<;`asF3%(bMFU(4^
zNa{((O14UVmlBq8k;;}DlRhD>C4E!+x%4*~5g9j`Jeet3R#^kt`?9ZOkLBd$g5+xC
zHstx`ugd4hPhLb_#9mCe*sXw2P*b?6(5`T(D5n^rSg-g+NleK{sX}S}lE5XmOU0L#
zlzEk%lnazUsGwD@st{B@Tt0i*>2l%aj~G6TE2b2)rYfZBty-n}S?z*akXobKfx4o4
zwE9096dKwZc#Q!~7EN=_EX@TiUM&x;O0BQjvf4Ma|ItC{=*qGqHWoIeHhZ?3wrRF2cCvQ&>?Z65?62GRIB+`nI&?TPIyyNvTt!^9yjpSfmy?lG
zq0^qTu5*s_R~L1c43{lejO%094L4=CRJS#EW%pF~bq{5aM;;rVmp#)xx4qQ8vb?@|
z>v-pTANUygl==Mewe+p^qw%}y*W%CO@8ka_fG6O3!0tmI
za4+cIFhP_r_m{PmlkV;F8drD4F;q@lTR_(m=9Ya^6F#
zhyD*IQZA&G_)-%9H1r{Fx6ke`R@Q
zjc2Q6*XD5LJjgl7b}yzA2Y4FR$RLNUnrehE{G=*;NfyYg9k45vwVvWv`8Y3Ox;dx>|zb_ZKW
zawoF$PUoK&kuUcCx%SWYOOKaJuN+^^zP5Tj_Qv?lK$m`3_gk&EuivS@d(o}j-QJ_v
z)6#pfx4BQQuc=?QzmX(MY8;RoXd09sd_JTw)H-}=xO3$4$jecU(YIr|V}0X>yW2
z(6>L|6LvUu%64UTU+rP{7WV!2e;(j}aQq-1UOaqvWO=mqGyE6zuP4Vs$F0Bhf6x8#
z`}60|ETj%m!YL>y;FMrP2^xZy3IQ4&4Gk6T2|C~)=;-Mgm{80NjI50G^em@XSlQT5
zo;=CG%yF87ofE}=lAU}J82L;D0!c-MWM`yjWdHx&{=9;iY3PO+|Dk~KLU3jn1vBi=
z8;A?UGzbtrkOP%}HyE6P51J|KoCZ{4rYK>_o
zt|Arbg$hin!NzO|43ilG13|{*4W*fcsCNr2SN)`LJAAt#?j1%&P1aZQG
zIB*O?;%Nk92}qnUc?V8N!qhp(>RvD2FKf`!%oDWnb*p2&IWPUoM~>e8MMOvnp)6pepBKdYiNRUNxPq;#cMY5^rB@;GDtJpa~mIo(@Cfbd>sT*{-
zKlS5?zJbAyF%9;JUq@1z#VnIH+gLv<9Buw9F(d$M5GJWX7Ejq
zwG1}O87t+BC090fDSbY8eWAa^zkd{wCpG9ecxk-j%ekwWt)8CaYP+qdi9gUun>Kn~
z*6RsrR1EqyI(J;-E(AeEV%KOY)LngJFXby%S$Wa&p2$MivCgSqvbb*@U-~F*JQOvw
zewck+H~01DQA3oOiFAhEjP+ZGrMKTKd}^~ZrrLJ7U&wY0Mvwaozm+Jx{<&b1YqRyf
zZ{s9GLlLA}X_Df4Se8w&w#-GTO>&$riC=e%e*OyK;+_cp(`vY?j9*pA7p=BMO({FR`CU8kg+{jP@TN~!595=AsN?>yX*S0d
zxnLc3Ctho_2cs0+ym30BVo%TlURHTZ>3lt>6pCo!GAX!ZQy-Uv2_GG+;O7%U^lSPo
z*zSq$jhC1S>HQ|K2FJog7}$DhOihc1_gQ$Oely6hM~kVcMB4Ru^<)KM6u|ex+V6~
zIMt7Im0^7#bfKkp?UJeDXNOH0I&-+;K(c9C+ran?(OuJ93bxG@91KISL7Et2n6U=L
z266!mC@x?jGZf0X@*dxqv(9Z}5(=fw_qMT{S7(@jL__dG91%_6jYZNF!s7(Xc?HvP
zKrIMpNEnWzA@FuXX!Z&uoHF~OYLRBeMcud7HJQp1vc5mLelzD03j-Gg#
z+ofXB-_$A|UVOf{J$={qu&%UL;>KXfZnD*?VsykPsX@hOEUQ&1!pHm>F;18^XpvBe
z1h+(@1#yLfwN4f(w@s=jf{P8g>WIs}p1Xb4fo3_%b?PB@;4O=**nU^Y$+u0Pbd77?WLa{VPjtV@Lv5QVX*|1BNUjp;$q|Y?f@BBFdayKBvEFL
z#k1ajN;5~)*?O2VU3uNZ{%wfXr2M#b#@+3JNZ#*u&kmy{Z!**@l+f(%G+5ND4;JSR
zo^ub`U2x292(IK7)}0tH8_?Efl=Q0}_%g7%^nUg_kK^gw;n%ty3z|t6+pay*O8Ntx
z2`>t>ii`rFGNMX7zyCH9C
z?}$G6a%s9;=Vb{D70CQp`&f4htQz!I+qsgw9LBl2RGBfFs-$bkIGrEGY&J{8yn%bN
z;qRXtZkkz`IG!rV_jd50(7N}nbj=dqA96>d`$AB{HMpRPO+BL*2fq)qB$H@Bf>x!K
zaUzcl7cWH?=Rt#|vfDk9(}soFVDAgl$Cbv9@w{`$uRSpU+yA@=czWR!d0C
zaE2-IhN~u15G4_b#zQp3SbS_802Tztp@|jfN@tov1=u>S5RE+HGo)&x^TrwrT!k45
zh5%e*LQw*bfyIC~`F8_K^S2>1nMrhpr6tL3-^8=!)&$^>dizHGCrKj%ds3f_2i8V>
z5d&q?x)u8^Dk(Rtgen!RT2yj9>V7yXEzRyICRTW~wV#r$vQpI4*
zXit4}#a{tt!~%aiRwvf}(kGeP*&zF-v}dNqA)lN==URj81cq|jBi`Md+Z7mS{{#8;
zZ`?K9wO243avCgYKj@N`!LsYB1j`QEigB0AR_s^5Fy|YKf{ikygdT>4?Vo>_yuNGw
zxF#T9o%Q-)%VAQ?Del4cD|e^+X5Q2p^SN6f`*K+;+?CUXo2~?0_PAX9{bvKw>tkB5
zOmM^=C^tZK4Bktg$cm~6-o{VxXF)W4ci0dpU=V}Op2O!Z`#Tr+L*xhFCe$Cv^g%dHS+-Ug}>d)IO=9BZg
z0sFGV?q$vD!48oru0)s;@Gt}JbMM5i(Qhty&~t)V(cGC
ztDE$CyxVnR?Xpc<*_R=CJ-+^%QPE^kvo?
zEQXQ`N5km$DvN;$t7_&=MDGLjVZhYc5DMAxa5z4$kOuj#Ndu7vp)@%Qad;572;P3E
zid9u*Lt((nkZY{K;FGt18%k9Jg0aE633jC^%{S7eJL8QWPrPmBuN)r8Hn&ZhxM|)O
z^2xUHjPSe5JbHUO&ow8^yyJx7l(AGeq97U+R{;lrai&?VHcav+;AtQ{j?6W3?1X~^
z;e&RH_A1(r`6jhaq(MUaeb~?@$R0O$jZ_DZaiRBgasb
zvo(-rRkV98>*B=XK&-QQvx|4y_J#%BvpJi*uH-XA4z=`4>tBRJ+oIc5WLNTDFXij6
z(u^;7SDscd>}Ec*lV>5BwD@{$@15}*^^Bt2JYoSriFJto
z+hNSLNk*%=TFyK1r}R<^Bx!Wk)m~xl-ihtq<$17jEPncUGG#wFW}#Cw{f6aW>f!fL
zF1xAW7~f3UTz2;o9}eCvaRu?Vpe&zL>%LDm+-CzHPG517?Z-~rxo2PLQMZ>$kv*N0
zR_sod9sC+IaDtL>5-(({ABW_98q0}<7nWi;AxIEi2z)i~gH#;A3onir2jGj31;21)
zEU>{e1R6qY2|7FNs<9KwInZdq76-o4F|TNMF28RWw;*PwU87a+G)lj8G6jLF=D
z@UO9Lg8&=d;&1w_nk%9>
z5)0!*FfathWtJDIhlc}jk)d0Gr*M$9qvsi}NMf#`N}>Yp1P?)l@K|_ZoG{RM5UZ1i
z0Y8ExpovJFBSG7gTG1n>vTW&e=EnPousrTpNrpMY#uymHjH+WpX<~q0ATYpJK@c-0
zM{P`#ysK$k0T>kvJQh*b95Q3pq0{IT0I9lrwcopAUjw^o>h(zfawp9(p69v>erQSxwkG*}32W*_V=62fe5BZ!70hs@P{4yB8C
zLxRmw2u&s!6M{cU)y=QUW+krsftmA>BXt_hu@9*t@rd0=eeSyLlMOoOUF*r-&5!F}
z28Z{qcXkY{vo8inTQsT7Ee5PDmQP%>wu?T^BUE>HebFJZ?x=l)l(iwVH5}o@A(nNe
zCyUf7n-r5*R`;Fc&y(!Zz2n_78Il)4ZD>B7m)oA5_(myk)?LqTb8_$s$>kiY!xgpW
z+(F?`MJ}mHBWk(I;W9aw(&DL7rBJS?dSw0zQwo!f0N^%25jjXBqKHIcg>!#nN=ypE
z01H$7%TzX04{&iH>oVs|(u8@EeVb?y$f&4v3OxbzAOc9Qh~#t!mMRF43Bkb_AWUF<
z!4BB!K)k@rjI#_IYoH)wn5#C6U2E9p?#_tAUH^zDikbt58;!y{?~URy+3wNR2A-SG
zDuZ&rWQ5ysey5-B|1wbj&d4gnd8zQJCakxxbV;}99^WGwO3!O_G4~!_upJtF&B2v5
zg}=8X+*Lj@+>=&YaD7neh{}+)bvkFUF)CbTFmU#8UxT#PL2)as+B~h&ndJi342C7U
zZ44F>Y&VzNtb8&BqwX7#QNGa4ZyrCQ=mN5tXgw_5H-B
zsj5LuSi~P9OYW!9F`odzzNRWjPGMMJ>p(<~z@R|x3)28`6B`={(os*%thHshaJ)j!
z=t4oD0B{f%lQ|{~bQ&;-NPuA8ghFAOLW+C%Z+PKC2F}~#xPw=BdQQhn5a;GQ^9R#?
zn%0Ch*{hfIvYuMtOXt>xYYr|ySwEL;`ykbz#)a^B`F&AlRriQSY(H#7LO#gH@J=Mv
z>9DQy&Qtdz5>W*xN^Q7Ku|e*gMo~3cEDAgold-0Tb!n;lm8tH?w_ZgKt=gLLc3g30
z#5bgn6d^X
zlpq8`{5yRu@CQJRK_f!EI5ZLvh5yRK1zB(q1X7JSstTb0ASnTknHO|Hz%heOY%Hw6
zxqkYlvdLqH5X_J<0&o<9uuNDc1QQz#7ERs*Ax|R~V3P?X`yk^%sDe~WQ*GE>i$T;=
zkn)b}5dQ2Fg)>z}DHB#UJ#H&Sic?p{6RC!EL&TQl7Fy=+wC}t?Su$_WK3|X**yQm~
z+f>e`S-msd_e?z#M3YE7?+Jy%SX>+drw7^G9bOmF2rfL49knUmq=#-6D)c{(_IaK2
zW8L%UWX{8h^yQYjM4B;G4Fn|$g;8BH=`%44^sM>zrn(80CrRBN_mIz*bgIS)6{MXC
zk0Ta>NEI*y0y;xe2pNef&@mZmT1?@yR*4N3fr0%u6%W})v9F8m-8AdRy8ILUKDOFC
z;A0aavjC+D!aW2N0s~YLhJcJwFlG|W905WBHUhB_jUs|6p$gs-U_b$y3c)S@W?aJ0
zP#`WPXNj*tj9`Ysu(9OCAia;S@G)L?=G8A8CwLu@DwphwIanqUqap$XDj
zEE|NC!pM*dGUi15Eg57S3Vhup}BAObyrkYpx}Bm5tP!FSf??nqs(t_yX4%gk-F39?>btE}
z!<+S^H%rJ}@Wrs=mG->ml8Ej3^LE>fd5S!g)LJgRE9GklbtVL92}
zo6U=Onq?7vc%@nEgZ8eqXiW0Nj_a1q%eVE{4QC(DQk-mE4i_p;Trl1?_ZE&TgotQG
zFJ>&(bD0&*K1Rv!H^Yf1E*65fAwYP74iOR()_KD-LAm34C(~!!-=;owZlS`1?Eb-3$_ikBal%OSUuF}D
zf;ih!f8~lN6*wFjDS~&&5&!}q0PX_D3z7pqA_y*k;|6`?I9QPE3CN?MSb{LBuozCj
zqX4)FKz_h_2_u1x1DOXFPlFJ|5img80jR-Ia&%2Yw)sFNOuXqh0Qy*PeK?3s3JK&h
z$o`!?n25w@3bGT}LDT~Ffh7P@45(7T2}B@aporvAWM}{a$-4}ch6v%)ai9-)7$hZ`
z0JlOyG$1md!T~H3Ko9=*LpvPEx3FYetoaPU9zm@$tjhM&{SQ=dXyny<6q0i;s#PNI
zr(v*WcfNXY%dKs$xxDD9Z%vJnG*9^xSrwHvI+W_3i>x0+UymsH60!d6QgF!^-o?p(
zE`G86p7d;l6rkR!a>Gh6;w6G09~UDLRKRn=9dAc
zd5xzP6dT?uGqk1|?Phc@ROaOk{}UQ>D|=@`Vk{@yQCz>xS~`7(<9f##rK&nRt2aS*
zl|0LdJhyGplJ(~#%{Y@NfmmT!tR|&7S=Wf{fXigY0$f0X9B6ht8c3N4A%F?fBNE{y
zvEbm}0ic_lEf9gkz-dHba589Q@qzE(CM;^@OZ9=u6GTjf1acG$K9ocR9UE@f5ndfx-&p99*5*DjH4v5!&3&d%lEFKFg668rK|E86cXMoJ)6c8@oRiHS6!bPi@(KO3L9;X~X-4kR27Z8v@z_+-p*8{AnGN{
zh^*TLKo$PAz`za@__9v#NmDpB?#RYpR*TT?FzmD)`pMlsev@%ca%16)i}+dVs@dDU
z2VBwpx=ylBSUi}dzGrT?Sa}M@RZqY`4ogk1JM@5`3Mg(YfhbrAI4o=h?f?;iM9KbK
zSTMG@0>A-+tRQ5(Fu=#(!(bnYPsIV)SOMJz?Jt1H1Tg&sa4s+cg#;KG4ozqX`B(4&
z30O*i0DL^a3B0fn2h2VWRDB=>0fLi}M7APmBpjy${dfD1J=i-;zYbyhG)Gywl%m%~J}9AH6QF
z_qi%@rY+!ddrO~x3D=yD&59rX*5j{{-``i}1Sm0K%d%hOYS>~WKgzwxx4mW@ZoJf#A6AS=r?#1uSoLDQnbK$tF-x1<90Y3_2{j$*|56-p%r@juYj
zJZqzhG7mnU61y34p$KKnMr)4ZsUv_l0Gx;L=iYNw2r=yX2A@}QBgVQ`}
zR!O`t40#Aj6V#I+7`zK^Y=b20F>gAn8mD;wx!K0p?X8LErKM!wtX<#FN~G^YZM|O_
zZ`IvoSjgxjm`|D}w7zABb7m!{fvt8^e
z%$4{6>#R^H2;If~je@~#$td_Y66y&=VIgOLRS41plETM=3STb{fPt*AFd%_K++8rA
z!$Kf{F0#cT3fc!j5i{{iBr5kwRC(m4es%}SH>HH?|qnKeL6
zPe35}nN>kJ!-NEHO^ISQy?}zjG$1;Vr-Cc8L1qLRP4cffL<XKx!1c_4s#1claRnhZT?Sl{Y_lQEHE|tc
zA#(T?JeGzEADd+CZy~E{v#*!rUD5G?y(n1R{XtbL*KMiRlPqt$hFu=>T1s=W!3KRc
zie~yfm(Oq#yGAM+-{HGZmT#`i)=VIYMdl>0S7LFg`oXA-EuS3AoxAB>+9mE*?vWZv
zS2oz#$3tACM16>>3a?qNH`owe49sk?*q?r#H#azQ?k7b{zstM$XhXuN*J6+V8~vH$
zOI=YfBs!M+8*Cn@fr8UH@W`P3^{Lj**Sj>>ue*v4HCz0nW-T_%@=De9ZWfa{mOP3M
z#exNaIX?vHYidHG&|?syYnatxn2j~etX@oAgCCt_Hs<|2C?6OtUw^o9I5{=9#+oeA
zVzx7=l|G@eFc$TG@Ysd<+d%ll977&-EY%;k>oaZMpq0|3wIw8Dq1_ZRP+*Ci=#(6<
zvT#>2_w(j$oSu=gm{Xg6_~4v@&V9nLDg^wZG4m&;AR6*RgDF3FtdKAnA@EpXP>U84
zJbM+O3KXjK(7^f#@)AH413a%F>?)WEp#cRJ0uCdHEPTPHD7HUPS!CRgZ+{^B{ugJZw;5ayB|EOrlJ;aflar|(%Zh!L+@ooi
z%X>Y-8fEj0!l%xYzJIP~ypqhj^Wx@Ldo9J$#;m*VQ2OPlk(tL6BWZNP7Pd4Rdg{z8
zygH)vH+0#O>O++}BUg_pvS$Xq$sAu!AWg5DTwIO#y!K=x$zMdaEx45EFGyx9yfDe{
z-U`h=xyXZtVmn5|)|@$+fF@g&f49Fu2n(p1
z*+7Eqa8bevAExdVc;{H0tlAwjfw`A2LW>sj7C1Im4P(;I1@%w_8uey
zvNwEIEa9T}>nB9A-y?#!IOGZU{j>P7;PQ$+Uh7ifns+XV5fzbIzU@j%$h|&p5#O~F
zKN8Gl6S`$e#(HF3G6!UO`(%9$oZ2crF`|u%qUNL4HyRRBx5H)Aox2T?#X<_ALKoF^
zhVc*rLer2l13a*f)hH%982c>~NYxx=Y<9Kc0%T@4`gG~1*A1^o1BdA6cX!n;eJm@*
zL=;S|l=5d3^QL>1+?puE2idbXW@c#huO;fwWCr(5buL`m+$dAFwY*qlG4EN+=UwzVry71_JYOoM)=q1hBt1WB4ZgTngKbD(Km62|OLTreXyiI&VY6Rj
zv+=cUAoDOr;B}x+#Va32b-y2sb$!b}Pqn1=b!OCWah-HpY3176oc{93y*>Ee_MyRI
zVmgXBB_Q`sqN+JU6AF~;3bKoh!@(7(>NWY2`r?#o0@M|kt@%Qe?e=O@l?C#C;^zm2
z25U2&_b-)QSzYs73F!(nt(C-(A!gCTFf@H&=+D^mJO6u8@5!6_Q=m-wDI=o(pzrfH
z^Rl4k{Ejbn-%o%U`lhz{gKu?Dqi366FNFc|HFZ?e!E~qO8XJ$<&R6UBMG+jPUChgROOANLD
zyq;hE@hG(Nen+gpvmZ^ZkxdLCRvRwb((PGmPmhfr7@9PVi%3m}-eq4G&wSkMkTXBK
ztrs|R*V$!>6B<9^M8JWd5bsTcCa8gEQkYN=QUqb{TJEVJg(0d!g&JBub?v#|H=73?
zO*ejJ6v^+NVe1VW`O0xdYh9qXE}Cr>%t@{GG-874s5Es~8Kbr{xwKRUGeW@K#yQY#~jG
zaA%9zS@_BIOJA+hIdHk6G094sT~&4dvt0jqe@V&H<=k(BLwILWt?wjYU>ZTN>2J|Z
z0X|!uu-zJ^iJhC~hl(c&i$#-{uTFkl$d(^2+OU;R@#zV)K0>Yyuvm`B#dzi!m8>0B
zj2yF_iQUd?%JV4h*tWAV@LO9RGoW9UE2u`8noGGD+;bICGOz#WV^q2G9%E#?wBL|b
za)N_ZTV3RqLo#9IyXn~Tq%-vy!`DIs4f&Gxo_vl<=c!E7b?8a_{H0sDYBwNDC5I3d
zN6K+O`(S(Ho|KzVw{}H!puuSW2%cWk2_^%1As}e$$L}wkUH!B31J5&Mf_xi>f|E1W
zYxRF*SChv3lAE)Z8+I>@)TBor8$|y$t$KU>$!_-9a^z>Y)|YF$tR$fT4IyP7K{S^v
z7$|j_`E(yT>)r8>WNvxsQs7p#z}?CuZCkhOQu|aP_b_7byZD*booea8Fv-Z^tK1R5
z0g#Pi{OOo%ebQm|{%^aPqwux4+Mq`-<3q!-F#qw6_jkTu*!xj9INrMxS^6F;#8lFe%GcCW;?xQGH
zlk5=&aY&6$mnMRe>$?oL^;x3xYweI;d0QXOrM-%<23E@hBgMBDC;gXpyAtL&tLNTX
z1rIm7j8B|?6m~j&B+_O06mg`b)V0dOUzl1Mx?eK)!qWR!fIWTtiCJs&OOok|k@8it
zbp@o|yt1C7;L%^B9(Er@*iLfGeCr)H;(z?lV{-KnqNGquO1dTtObG~}??5I5mS1QDW?fhLR5hD*n8kGNnk+&)@4;4-K*`Rh@WE)u
zdjsvO$?6&Imm;y5tN7{ktSV`~(OQmSPc3ZHvhQf@ZluY5%?yPeKaSEXy;t|4bMU4v
z<{)M)^b7@xy_!lY`ZdeJ8m1alw^NqN5~q}hU(0q+=>Cm7>Gj8{3gWzlwJMK>hR{edpqP
zeoh|;$GpfNbvDdbb`3kl(d9F+D|YFpW%Wo#=IyD7;w4e)%9(r@ph!F!p9?G3he
zD^|s0zKV63`byq(Upr^?l5}uG&@~QOEeRwYy;E4>zfP76WaIK%O?%+
zuVz0Lt~ZuvO!k#;TtD`ge?FX5z7mtM(v!Gwc%T+(nS7%*fycuJ0q*^D|K@EMwjRU88Vtpx-tkqa+iPvU$FRT4t+@%v{7CmLSinp{>EtAl3~1$oVgMYw2&YxaB;=E?14Ves{1eSZ&=I
zXbehh=1gjaX9u)HOa+KQ-=+P>4tvtWT;veB?h>OMl_%KEHjw49?kmE
z{nE+w;u4v+?k}-h`(G>Hg|6M;lzk&pp_aify?MpWF4zqyFbtB}2>=tIAjJK5gCWR^
zcYr^J_%+qWF(_>ssN)^u%*tCCy)2u%jv>k#L7#UMg*vGx&yEfp?zcty^fw=mjOR-Q
z@f3im_G6L2ODbzaTw{5T9>uFQ4PikI90z$tz(Wo>1oVCE+m0&ZTW3{qOxtp>9%UBh
z%-h-Sys^=KV|e*!AjW6lTWh;;w|l%E)vds+`SY1W8*f^ey|mn3m%-hdwNAL-kzW*)
z>b2Hw;@}s}lad=S59?IEYG%c(%0`E=X2xI`MpL#FL^nP*8&@Q;EiLk-taf~&J^?#(
zmS>N{y>;_au!Z-?l(U~<4@%x+4C67@;(>x0bu
zH8J>n(PN(#?M$ViVk7d|
z%=AgApVa$dYt?zOGV^@E$eBygGQoA8lg%O`mS=N%Z9@8mZN}Y$-SQff4{l!GeK1P8
zc9e78X{j|SP`1-;?Sh>@kcE-L<`1w|t?1cKu27^e328j+G`?`DVMyxdxzDa2
zwlls2pRnOU>^bJwEq=&V@P3!wF1KoAoldPZ6s)Km))4Mhlzmm0f#N(q%V*YU&}7}i
zb7$dMlUPk<3&TW9p0HA@ORLaS+hxr(S<8_hgX)8Z_p8?w&2#UF*pk{l!*Xmx#tu{j
zZi=Z~uiS9(?Kf`8io<6JH5Zn_ORj4$z|tm(d656wMU_O44hjK?AGvQoH&vRrP@
zkwkti*C+Au$c6Z|>WOHPH3_TliMo90wNV|`5=E(k9Zw6Dtih^HO-#zD(d1pVnGllu
zRNvBg6=Ux9wOVbTpyK!pt2zHJ_ig;_ojVMMa6&2QX7A
zrF(a-3|b~<>t_c{T(TT#$om5ge3P!qRzLgm*|);fkde8bm^yI;K65t3R+zUCx2L60
zcwXI`Cer749YIs+3{+{X(OH`l)$@#DL61U`nUZpIRTrX@emHC-N}nZ$u+302&LhidYg)$
zLT88UR>cjo_gkK~e5tzfdwD(lV)VJ~;uTMcjL=_K!T)WG=4+D*Qk8k&~4%m)a
zD!3nAF7uAc9X$5y>)W~V`@!3%EstKh`h}(CWA`H>+kcwAeBYIk)U_dXC2U>WY&Lo|
z$on4;^&*Z(RFAdnIE{6)sS*_3)GMuXres7KOhn4vZ-{A@xEpa$n!day3|3{~(usIv
zJQ_Cj!GCGBlN58$uEoW5{7sRY`(*FBi)=)^aMG|jDXD}b6%R_?>vPeb4OJ$b3
z^1bp)3(5lTq60_%K)o-nM6F1#Rc~z84VHQKT^!ro<}x07S;><)p?xk$e`wBrTllE5
zr{iFaqgI}xOjc7DqTD!4ED!ScAYtJnVBNz+Q1o)=!HA-0ct}b|xm5y}K&g;6!KvljBeADx)zPh9n97(ADTaW
z{Af>ijWbJGEzn$9uQ*S7HdKMyseq+6XUASbWUk7vW{~ii93xF_dWH98wsG&pziE?@N$m77&EClO
z>(js3X=H07rQq*_B6%rB)GbesIoO6F
zt+%!!^BCoMvZf|o=X-0`P1SO)5=4gY*eA7RHXGwd0~*2tR5H{Drm^f88t=O-npY=!
zUgXLmb-FQ(Bbsy^t$e6Tv;ky!>nOvl)Hd_bZ|{GKlK0cD3^&%d*BC9ZUWR>Dg51
z4A^>WnR>%d_SKFY*-qmd)Gqk8I@Xs_lKpTO5oOHtNJ1Ts#=EjxS#p=n)@e
zezksOfA$jpY%cZlUuBTk)qPW2E)@2H!MW3)`lGw&1exp
zK{R_IPEZF5F<+b}z1oiOzc0^w!fv*-H?@A?=Rlj?mnT#wlB)5w9Vx!MDyGG&J3(c(
zO~E51+2pzV)fx96-LP=H{9@a->6=Pm2dPY9_;cj$3n``1h);&+?|b!Z$)0!L8yMuC
z3}(q{F)!W-%d@TMlb
zfHT#M4&ToNHQbFa!(UPvD=nKmb2j?H*CQ-NDH|#Up*BAw|LG034(0|{@GC8_wqGEPDJM1dUQ}I9WD|=%=XCRQKzim*UOwmCVCBcp(vge%UiPmGmJdE8(CwSd$8Enf
znas~V^J39rN0H%Y&r);oy4Is(Ts08=muru
zFLe9lhpusdK`u->y$-GK)b(1j=Uv;}$Q->ot(Xw)S+e#qH{EgTqO$dkD{bK=hc}cK
z+6Br4v-Shz)AQ0@6deLagQL=)J^c(l{(y!yujUPe{4$`%q(>_$-IRBq@EcUxZ2xIt
zSgE+3GLqD1uX0z>cRg$&bXe~5LGQ85;`2{6_97%Tt!R=4e#x^MGHMR=8yRt>v@3xunp(us7BV2G$jZjpe=%2Gk>CX$UZ4lK1Mp^lQ`3
z&%LY%)5>eAR-R(OoZCc)=+045G_Xl%#+u3-0B1si8Et^^-9jKW{crRHrq!*&1rf+gWYZS6y~xu(rTl=yedh+V6c1Sc<&(8t`@ON@pYTi1I_1aqa%?=p
zerZ*`uZWPinUM6oqrWfrvg^0spBG9?LrkOm-tKN}yi16^9%eB
z(s;2g772o>lWmJiR!0@5FMQu^G@hy0e{QasnsIjI@Hp)_MyTMr1ZKxYIB`bklb7M=
zYWkR>q*r3UTEB0X8sIl=_D2p+)*MQOD>_`x8*H@rChWDz=^*)nr}86D`AXM9-<{pP
zZEnWPb|NNRa|4byvnRv@kL4u-{VFn)e#p7|$QQ31FyxD9OXurHpW%2G5-~YjI-bB?
zm=yE*g0`sp7o)Wf(T+1ok@GT#QR{~bIS*A6J=|=4B#lGOXdwhfaqd{$BH-!5n`zSc
z{P2f}c{+1XThp|Luz9OxQhMjUfR6n?W2+qNV#ZEI8!@&U1`+RNt8X*+&<4-_48L`Q
zH8^PAh|22gA1L^Hd|&>2*ZhQ+nzdN>{wj?1GPk)thW2Oc=h|UxMTap
zWA@zb`55V{537VV#oy{y?+{xgr~pNFW|U^MF7gtSt{5@)`@`LN`Vn54f4Q!)kq_%ft24~hqq0#h%l0%Ayn)nBr9SF6q5PegA*GK%i
z!9Wjl`Qf%d
z5YJwWK~uxy0ir>Vb3mDCx2bN~(5S)MIW}=NNOfCVc2;2_^tjaU`C)TIbC*rB7I8O8
zelVM%Kd*%AUWR242iJjhe0%V2tAoE6H1NAG?~zizhr&t%`1exmxSIE{nOw&C^4g`}
z1(|15Og}%rq%~7^me+upy6|vYd*sB<@0UIim!G*>W^U~mCbcHr*c0NnPIc@F^1zT6
zQi3^4z$1_Y#UaT*NU%Bq{NVwD$LbWaR}^L`UMKaBlo;1fMV<7o4H24Kis(!!8eT{X
zIm4g$bujdBL%MLi;iTkj+Ca?f3So`UBt?eP>pT%E5l$sW>019JM6ZbVnrf#8JX{(iZ(9>m
z#iT$>vq6?@M5phhhugG-^w><~*sJ$NTrV<@lI3#VJKZQUl%}g&oZdx-N5)_G2uE46
zM(OXTBEiOd$mXrTZ^{#o}smgQDP-Vr)nvRk_xd$jZk9L2wgUb9b0Qf%#xTb-+$8Y
z`>*T&pX*A_$;ml6C+EE5d7t;W?^_=L^^ZOMB4%O2cBgjkkJ#ZiZWl5|N6=I0o!RBr
zYZ&<(eMtq|>a8(u@4nw!$v`wd4~+C1;b2zC8_uZxzs(bcO!>9-dRODtoH_W
zJdlX*w%RGx~pLxatk`#obtG)PTB!U<>##N{&5vKK49pDgMugPH6Ya;6!WN;
zHZ|NBh5rT3lGW!|8K=mCWz}5OqSTw*bynmiW;(~*>(%l7B7?j
zeoNGc-@rUMg9&PWqGRV69zXV#LO{njdNKptC=2J_u`*e(1Tzg4#b?&o8tFXiOAcOd
zs+8Z6T9j`T(760zfs^P4OLj82vN2LyVai8)CHy9Za^||FV;4B7L^|H*Q1_0H&N<7-
zcbAl%nzN`~pLVUb_Xa(<8|(ypDcn57_g3qFjq9#jgnYV(qqW_e868*4NN?o%o0>Ua
zy}&I{n~%{YAWb6I+R0_ynz7wt&s6XyT}Sl{s^9hb-D_Z-lbO2?Ws;yi
z9U$9;-ucs~+<@dikjV{AX<)Rk`Hr~;_@K#giq#Yd^_eO>I(pB)q+(C=Zt9yzPmz0`
z7nsQp8{CF&-Xd5CJnKMmFH936U!)##5sm`A^L=$3uXaS9p%(Pk-hLdP5MEwlTeE&&
zwoXp^&12Y_sr;_j7yKPBr&pIGn3cYpe41;u6Id8N
z;!|d~aKKT)}$UE+i~Lf<2Ua_OWH}SyMOdH^eL&ZyJ3Uq
z5+s}4=$&ckIb^Nduug4)k8m1=`ei<{9&LXx=^%V(;DCR!{D5RC!x$>N&EH5VbwvKO
zo~#rm2!5tUHtjbb4Tj5Hz!32H+lq@ce-)asQsd6sh673nUh(yMh0wwLaw1ns!m2V?
zS&3z;n*D&1`cczX@8AoCvMk>ptJ)ocWPzif;Y-hXx=TSP6JQyVmOu`asfvsuuJ17U
zp3i(g#q^Qg?(k!qK52aY-8)Z}384jFJw&6X^T*uT69vtc=4rTc_j9w$IhM6nWo^#2yv@{v?H6*mO1|#hY+g$H
zZDnxZQw5-5Wf-UOYY3zFzNI1m0}^fz{xDr(Z-0Jf@lgoG;^AnpzlAyXLBjA%aaOU%
z@HUh)c&WCq^5M1dp&O`?{>E2f0jfY8G~3EnUO=
z77_InS-?Zdj)yPm|<{a@o>BL6$#q#
zHNY9UvD#%D>cZ27D#>z;YN_@05UA~)?x`}{Jr3V$Y^hwhvNntxv=#|UcaIz@Ayn;o
zPJWAqecm}Aw%!5eFV8o;4Xw;5A$8?-80N#L^?AqF|568=XA&|}5}%?ygz*7v>L6c)ojT9^_AsS@{RJvdd~RY4LsUY(v-pdj-$82T2h+4AeYVLl(&lRfWzo&k6!*-fy(js4g)ze_Q)RKUq$z19+s44g$
zHqyZ0$orUG((akO_w?%$b7M$}j$eaO;l!en^jDLC)>OoH?5hKi5D1#z-*g4mlv
z-a1ZyP0ZYEOOdAphxO$}!OHLSRqUh#nYFz`iAL0((ef{?BIQj=(7TA5Z~?u1h>X5Y
z-KN`O@K9u^aeGKT_l(POX2SwUxw&}DgSEqs`~$rLNbs$Tmvq?m7m5oHs7g_yD=n5S
z+7d9vya`DQ3kx=S;PlhlK7q({=)Eh@qQ=F4c2W|G5$2!qz@BV*bK$+=WxgF{?EN8H
zvwxX=p_(Cc@0){YgY^Vm{Ua{X32bB*JY;gqz&0L({1Fkrm3weB_aoxXxx_o66yuDR
zH2-(=jZqrBmI=}ZQT}=4bOWsFG#p8oD{6P$GE6H&k5cSW(1L?irufW}rj#7WhU!w;
zyCNNB3vTy1>%)puh2ZA0p#a!-b7RS3&S&?oE$0>8$#7j$#-eRTuf*KjygR>F6(HyS
zOtEfT+QTOeU%o=)+&;Hz;Wk{?d8c-$Slu7Un3f%^{RkleDUc&633m=)L4_+t5{8$Cf%y;t;#eqN}4KD#{qN}M;+pW!5lxygXE{7eAWie)sv76KCpZt
zDaJ!l&evPsrYWGj;ZKPSxQZ`qd^!rCvs@`5IU**Hn%+$P;NCrKYnPw}V6)5s__#FC)6@HVdY%m<
zkbi0cECERSrG9p1vvi**dlVoVTO48C`qHcP&
zy>^LH0ofgr?g_QM^3f{c-YYAdO_|ly8KVU3rFcU-uu(`N
zdSuWSh!IfVkW1g>vNPOX8Tx)GQkL3i1uNgL-PWJrbLGKc>8>C)9CZU@G>BLyi?h
ziOwd{W4tTQEAY>v;G=EhdoYjM`NOjvKN^x-5OISpILBAV*FvU=Cq@kqS%c!uZjW9*
zNeEax_8y7P!od7Xi#PXWLrX%p}j@1!EQ%DqnZ%qUU~L|MfJ;9HNeNny|@l
zl>*_Py&6%!mbnub;`c4Ne-WABFagZ7X|@@h|04rL-U6q2)|9}RubjU2%{9xfw4!7l
zx_uZcue_6U$n_P%x$&z{Kq`G(^S$!)ak!a5&u}oIFV@@cL4`yPvS*w+Qoi
zjE^;}dhyZAtTxlv&}=kz>Ei^-S$^T3+?us$7P6Z~GOWfxFW+%et2Ya=W02=iAvAZtSXcZ~4x;
zEG?C-9(1RSew^svo;gDC1@75(E#6=00u#2K43KPF*ITB%BTOPc6}L?YIxY77ZTSy?
zPwb&4=Fyr9F$xaaE)IVqRgun)Rc8;+MFm_|&rK&+Wt9@8Y>}l(Z`|KE=+wL9v!`_M
z1Eg9@1Cb{Z%Z$VWCv2xbpXQ0hTA0vbD>B12%)gQy7>k&Z
zkrjTneC*#(u|F-`*wo|r!*&WaR#ujR!1PV69Q#emtjQtHJHZyD-|V&IS3t;RIh=Qe9S$s!yX%-$qh#CONhnJs;@<5nXD-;fNx&;`oq
z*0hL>Z^^u{Ap49*(Dd(p)+2xz3?O31IMCOKIZeV)DgEtreDD(W;wX=+8
zg@l2$b~;@VJ)jTbln{RhiWLIDS#~GdCUWtZIzf|NN
zm1=*hWR*k^-~DSHiVqxx^+-3dUx67CND0qp&rj^kq@>LfjvghsSE?l(-kpl6*#{H#
zqMOWmjzpygJffcQdvbd6L__Kj3R_Aj{fJv{oGCyKBJ({aCI(Gr#=GmEvlb)C`ip-u
z!;jP>W}{k?E2-;cYTs2lqx*rOWya`ZUeR3gc1R+Uus!aF{}z*=FHqmUT_u}0_n1bs
z#?6(hg%@n8|E75yw3VsMsHgb^AB&S*`Mw8H$6sQu=XH*4mF`+>-$=B7(c|AWLF#K2
z=Nv7{d`{jSh5Jz+zs{S;dU7lGAeDtbYv}4{=DJ_~}n8
zmd_vB5noj6fG)mSY2io;dYSe45XjFWG6hg*#d_@N>qCG41KNBd%~w`23eTIqQjd;q
zFr4$jfh>rU4-}ZzGNN`%91$nf>
zH>)s4v3&;vEuRt0>(9pww>lea-u4+=)j02K2rsq^7l~9;&zi^74p^_Z1#is;jI2F|
zv_!qzLZ>%QghaNZ)O0W>uRH9C7ybx}b~UurlDE{P=^?sl$cQN4Fq->sJA=)>lqX&y
zY2drh1D7ItViTW5?|a@Zs#FIPbe&u};N_eKHu~U?Y&yx3V3*L0`jR~5$;?H+GE7@J
z3kCo=(b06LfdK#jvIG!vIY7;$XYl1z-=5-Ghf?weF+rhJq!-{Md6jvbx$brFK2BY{
zd?Dim%ZQ&c`Y4-U*jq&f-Rw6j-(QIspDM;|4ulxl%Q??V%NP`)`ewBcPU03#hwB3n
z{m)J)kcJ{JFKy;*m0T*c#iF-H`Lq3=>ZlmSxjbLfulo3Dq}Jh;_#?UW8)ApJQOQx9
z<6O<t$GXG+=nruU)ARP_OKCK-^O>ynFs!s>qL=f
zo2gj~#6aTjm!nb7h7LZW4;!6QrXp?4mwe@CKRe0d0w?UYZxOB5_>0*?7BkJmUF+Yd
z*j=Iu*#IbHhRH4dF2c+g6ogXK5S1rTmj^)cZ_65ZM;iHj2=ww4(Zxc|wfDIC?T74^
zu!dekUC6E&c%n!w{ynbf_|47YLGQs_yyg;a_m;r~7kr7OK~gp!AzFwSt&Y2{7#*l_
zyTj#sU);(}{@g}=_PX)~Z^u(vYY0n}=p7ja6#Y0s=AK#GM1(C17_n`(v3?aU(IpP<(UB2!gMJ2(1(-N0PaoJrG2M|^{upnzma$f
zkI%=#rZmVM(Xwy95`DHe1S|-Z%Y$AWL6Gf5y|~@7xL=>MUBWIQ3M$dW;0;y%DUr2^
zL>d%-}zV+(uo
zqZ=|y79+?*TK#haqSfc^G@2!hSGU|M_^_FkVBH^isxwkQttlO0&(_~65uCoB%%9=>
z><$5W%u`M??8X^)LK4jL)|%HaxFMu*N`>;#g-W6ie0n($k-5SX8V1Gu7%L%V`)oYX
zhxq51yn>aJt0BErQeK1Y@rP48dL7Uy`Ga_TxSV{gS}YOLIx}~rrs*{}QL=L65p6Nu
z+#J=H0y}#yc=hMJ4GDqi(khBRDII^pQuDnI5Eo-G;b0P}&noGkSV(J%<2%dW{Fgta
z-d_}EJKTf{{J6MUvlwTI*u*Uw`=@-3W&lm(S`SISCXs^_6(|h~FAsE
z4H0qD7Xr8R<&Ms9T8xi8Z>*KNwDcodxkSb-cX=q_=&t$|txvbBOQr5xCO*;?|Mj`#
zT)a@Rsyu@4lvjK3Poa9C1p^F7QFxtazxzb1GuQ!tK222Hyvp)%C5fPD{{kcIBwpD+
zH4xP|E>|b@wfLQDu)|V;_#?j3KlQKw+#R2b8d|ZV7!oZaqvxsT{cSeEs?Ec@
z_4^fsU`j2bueo6wT6+87WttP>+s@;R62A5S#uew7A&>EBwX7)HsXg>>&ESp?
z4L?9V@+-sDm%P7G@21RMgBXgM&D!YDZ|LzYTlMm<{ff((R5G;Z=kD}Yw3Exo8BEYK
zd`tW=Pw6*6@8M)*wOk#GiFlTj^hCef^#*i??G{u21DieBvq_QGjlVSzeLt&IW^56j
zkE$e(;N5tI6=Y^4%+j=4C4NnH4{e1Sz5KH$(DT^7mW(D8A1&du5T
zXJu08ctcDD^~n7U#WA$~kLk9-O#afFRmbcf!7NKrIz#Z#Ot_^Vu0Zo!w`rZ-AfXdg
z-TG}e#W4z-Vq;-%3M4nX-MORw+T|MR!$I~;g!X*(ZiU__CvGyNaiH&hPS=O&RAodB
zD^v!T92C0GNAs#Rk9ro91Uolc-W3scyfSqN8}*;b8gM00+mgIz%U))K)>48)vkAODqnz@z_|bNVcZ
za`jS}iFyCuoeMVGZ&o`c#2kuZ`dc+NLv|lqA^N0yf(u+-(A)?8*FFMw0`&Zu5dCO6
zOM;jXK&|tXG5?M1cYIdjSQ!i|1+%JsQ!IQBz5087$t`e6L;d}V$}Bihk%}oCiJX%v
z%2`uUJJG3@-?@ZLh+(OQd1ZtlD24h!I)n}Z3t1Z!x5USZVghGU$vlfTzCDtCA-QH*
zwds);^m~p}RB-2d(LM^gGHteZBOgBTB9k&`A{IEdVH{{8#5+FUF`OgW+?}(BfmPpP
zViDo@A`2kRY+%*|fod2v>CA!kE5JyyTTKO(H}?o$z00?U4!kVTN>=wn6Q<8n(RK&s
zx_!O;%E7rK(+-t4cZedx)43sK;KLO)71RB_kD;|~^4)3}1!Z8WU25hsm$__2w9dHQ
zQgWTH&cd)#5G_cKFP(_-up#=(TtE*d1Oyt!SJ
zmmn`H+YdidrgM7a%xY1O=N0|U`(RWGC2Z=|LeKKqa)`<)wb3n>UuJYb7LP}CfSPhqXMmlF
zLk@5n1-=zLG>LuVH)?%H#(c3K#Tf~COj*&%sO0x`Bh-+(yh!-V=>LE$on&xLGEP|K
zM6tcK4_iuq9Pfzynth?)7=|tTyoe8u{eVe^>mYzxN9!MM{-OyJ-PHwBZB4jf7X@!Hq0bYgNQJhR&+}dbq^n|}OLX5I
z==E|=ivh$~Ktn+L1Rc-C^iHz97qSD{?%$vg__>nc%+VCZf=s2%nz+%B>>(>A65VSIP0l%}g48t5VNoKO2$
zNm}ByDp(}iqFNp^(c$kbnm0h~nidvn9V6;NGvpa3m5t_=r7$)>EA8&Osf-3!@0nHM
z#U_D4&Z7L3ALB31)o+iWb#CIzzT>YyXxxUcR#H(zd{A`r6TR*Z2JI2(7CTte?1x#$
zIhvpb?aG3v7e-&upCb7aQ{Os)Q5`B>mbiH5%T_u@!W7;Lk!yLD?gWftn3OCI3<>0uY!~Pxb)Ru9Zvt6cn1P)mY(6Y?Q{J!HN6(**8&@X
zD=Wb(o@m&gT?B8}fJH{TX{uiJ68`qNn4Fm0tH$~k*he0=mt6Ju6qRXyD(Vcm#oft1
z3!Mgs78k;4t?A)C;``IxZ@9hapBRVz*`I
z@j*?q;JsixHKyX=QfQJFTtvG2=(=sx^t@F*EdKCv7nYXwgrL@FoPqccs7O^UmLu{+
zx6CO|(v%(Hbn55>sK|wWxxc?ehZ?Z~Ef`1D9UL@1%>cc7qv;26iDUBqR~lzX0Aq&$
z_%5vyya?oeJ1P1MtWNE@^@yT_ZFb8t8q^)UJo*I6gM0^j2a?`*1K>@9A&W)hLm;Zk
z0YLrjKu;N%pa7eK!8?!zz>9TO%k1m={YYMU-id>T6Y!?*l-{$JU<=RhU>6N_7K}Gr&`IWvVqGQlG?xU{BBUtgpp;{5X{#y8E4Zr1
zWX^+BkZX(1lNxx(!`|yJ@y`Ey<`KV9&i$=6nyDXPlO6Udk*$w1_;IPQTpB*hrJQYX6LE4%zkRHH-DGyW+wLrn=?&vxv>IdHWfR
z8+`Cv-NcVfe-wt8z2o>PD|jX3?|N2!r?^>$U#s=9*BxCWi5?BL`*Id(g5Kz?-UCZ2
zHoUgByEXEwr~WFRqGh)-i%KS{qC0JE|`|y?hLeUX2EiLh7B1ex!iDuS}co4b*61?4^47PAG(+jjIba3!?re~
zMG^24Np;js8no&f7$F*Vw_O=bQDK+N^Iqr^f0mAaLHh8~Gv{8O5=e_3#BmXNk&_Aj
z5a5Rc;?n>PiY9wX!%z3`tI83Ko1!20gB-iVvaHLtp`t>;Q#0?>g@>#1lkX4kEg(p`
z&4Vk!a@#Dj=GNIp$PqVXvFGE?6U3)8s0?q~NW+$lrB^;Wx)jJv2S~*Lu`Qr%GUotq
zAW#WF=Lw*00bWm_o{F7j1_0r76MIT-e_3+n-sp=Y5Ic|R6(Gt*XK2U+$>tpF94kM#
zq&NE14q%czU6@1vu`}MU^XNpU0R5>D@KG9F;M4b9))q@H$ryFtFbLJ6hp0rmTc-Y
zQDn)1q*?}E!^l3FkBW((`W304;3$%XSECjWz@PE^4ZR;OWq!)YkXs*DCR^fEncGpe
zd$Xp@xfX5d5xe$zXKi!AI9SE@oYiW>ikF6P`j}n`B%z?$DdUf5qQloa&2uR;o4?kk
zhfAcAe~~z1%pIPS81NmpRKwE8(LtYVn-8O0(>5q`zgBwN3JKleg7+6ylt)APmi1?%
z->8lj-%qO@@xI^Ag^ZF%gnE8;bgX>7-rOeVWELCJl07$5X@V%OLcB+4-+bsfor)EU
z2Z%l&OdGZ_KE1)tD&4!TIz^&rNe5S6`5k5x;}Dv&bhx3Y|IP0wxXS<58!(#2>XiF;
zwH2n{hiADOVP3UhF25|uzN;QGdu5l%HsLWFkuuU?UwP%*E>YP?j{k~`WWl*nh_Mkh
ze0+5oXcTddI3k=^YW{1#i=km*JH@J<%X(ZCMH5IhbJQaSA^wPLB4la;~~
zt~wiMq0I-XB-cD{+jGJFOE@DN2RqPO(H>pqahqY&@M792;&E9y!u~MI>W8UOaryQW
ze^eLJNEYcIrD#pON6x+qe)!O!b55GAIR!_J|6X%%G5MtN86%Y-nboc7(36YFryL*B
zujilL$MpxypfHd8EtF})JKh-V@MV45(g`K&xUBHPh0s*wZ*Ac*bWl2=bKq}SPtY~X
z<}YmeZ1-xGVG=(2D7abB+QYmfgq&IxDvL^Y&)O=xA5N
zazw@n-3OKl>j9B+@v&8TM0Fu5EWBM$xG={jh_u`@JdVmxcH){{3XZ=r$bz)4Y1;oO~%Q^9hH{h5<5P3NftqZp6yX@
zZ;#&-y56BgxxSakbQmHt72!(;@~J=VukweU8l{d2X()jYER95gLVlDmgSV7QHedf-oqTgyUmmMMcR?fOL%RE@#%Rf_Oz<%2R^`C_J
zppC=SWUZ;NH=YSmWIQ@S`@0_DC*y22HbU-6qgI^5$8QvCEvRQxGn_PO5u#yXqt=Ff
zZj?xW6cXRU7B~A?>W`D&yufeL<(RPmJ=Szegk`3m<=@qW!CkjA$Q1;SjyMGWVIIPJ
zr7xr*%Aq=Vy5sF1bEtJjh$Bq)T6|=Cw(pmnAF7qmUa0F-uGM^NKXs$j!4u+VC+`It
z7|xkYttZrW-!{{~)pL6oZea7hh%UqdR1#o_1F!&VTG07bIq00TcTF^N&YH;CuI3H{
z7`wd&^_S#`=eaA*);EKU0XzWE_W-Z}LrM5oS7KYOk_&xcaR>^#)kj}{LZnaZt2;K|J*x7@gRSirfYB18i=P*k>
zt1JVX!quEHT|6r&-LcY8GM_gdPSDVMv4qd)7Bz4Xgm&)ktNz@P9NU~6uiu?^n7NAFiN4R(nXc{I*
zJNY$f{l2Pf=F&7yRo~Trr*y5a$+lEIV7bMuLRtsnNJGh(~;9H-7o^dVC&w!<@g#|wUf$q(iDz?n<#>7;fs^xd_)7SQ9Ml`I}7F241d8^=N~6z}_gHq;PxtNRtvM>`c`V3vGc={cscF;&tQTmDTF
z9DXcc|Es78uP#{r!<}zz09xK!bVTu7BedtH{@2~dg<=_S(Ohyy-?rv
z2bAPf4%hNJfoV*DeCuBaL+AJfyg9}kK)s1hJW4mtr}r4V#po#!fENiEy~mLNNxfFq
zRkrZV8KD!)Y6BuW91P#*tra?)Lqntx$q0>
zq~unuq>1gFF0ugrO~UA>!{Zkf5vaIB#V#7PA|>0IHs&}GC;HxLCqb*inyZYgylXF&
zY+#@cXulZCvLlZ*3=m%@w>E9wG%y8pNip31S=u+9N<3
z$P}Q`qxanZsw|N04gA66KB1)7m;IfbkS(lRCGYk2&APXx`s(FqsXo11DkB1Qb!!zJEWCAsk(rRt}gkupP51
z7Re@oG@H*u(od*B1;dyFTse3%(Z
zqs*Om_dFGHB~sGVv%e`JMbjXJuWnPpqT{8k$XiZ5O0%&|bEPu&b-Z)6b5vZ)>g495
zgyTvK{3y~We7pf%9SsOxJ+>6R9w;o137o`>PtPEzFHZFr*^`BbZH=wb_se5PyH
zAuW^Gx*cc>BbHh}$Qd7ZbM&|WFnT+!UQhbZ*ob@GW9K+Cs~^3>JF{H0Nvxpi#y*^1
z+TAf!5`y)EZIf_#gJ~XjR^LoKwO|)#Gc>s9NHR@lr8F;tB@Kpb?RsGP*4|%&I+=h}
z9>%9Y1p}7c)$E*1sf$7Q8y@$IVZ2=^
z!!gsW-l_hs8>oOra|XvM7N5JiRn1A&)w#Z&LGLS8V!6dPZ|W|EwjY((Q)$Qx@Ly3K
z-G{B2d+Ho^`|2@O6*KqO1iV5cnwSh{T4jtB8|oJi9d6HHpbyj|Dd4FFnYeHb{?C%>
z(^31l>ZQiNhjOZ$!~0A>Q=Yt@5n4waMeNWrHEs{iW>o${R@fJUy*vVFE8FR4)y;6!
zGk8K?zBC^Bd1cz#bb0$R?@^1jz)YBzCCRYGc9SyK9e(~8toh%N5AZ)N02*sx0jkjf
zDj{J1c+LL1)B*A{|7QZjX2Ug?z|f={jR4TP?liw}O?1IqXI`~zG|fCxO>Ca9b>KTC
z(9F(4ujZP-QFJc#-B$LU%+=A17oUz}`
zHZu+tvu)!b6Ak$YwlbtexqBB1mubNVD5|L9o
zvZl5a*Mkjvhj_!o22y}RyxNty671nH3{V!MeqlQ9)38p_{R_W!ISo5y+Vh9fqO
z69^Zcg?DhhJ;=OdHFK>@itDECK9-iKv3{UL3BV-0-rv2P_pF=))mF2>W440>U&_E$*{QnZ
zTX*W{?$G(c&2t`((S6i-l+O4Y_wvtqelnMMf+bVO59En+-#L0se5>
zh0eH)^()5?)rY#-$s9C2mZhtcnc4!gxjz|^(oyFsMveGcClpu|i0j9bncZc-2yn#%9HwlV05R?3wxl1-1$`BD+D+u_+j*WPX0R0aX!vGV>Y0rRLbZ>V
zQA5fqk^7RL?GJL{a=$ZwtR($eYfNdh2`OXzxPe0TahbIvJF-zz4w2Hk8EN(_f}^irAKUV@~Lb+s^cwRHLGHbO`=ZX%hd3M
zv%SS?qMGyPv&}5^Y=x^Hbn7V{ExixU{{+F4?srmWk}yMj#(KGVb?F`@8L!96
zE$AL)l8grj`1*3n9Z~ZnsH}Bg85m=w9+a?Qd>#HUBD_7}i3d4wb>}k@F>>q=&z8~P
zG4v3$Kd%otcMxEN3x7-5s^7vSs(IWvuzPB@p;SL{lA9BcBqc;O-eU6
zxn5kxJ2I)AZ#`KY^!OEYAuCGYX-kxKjwq-&M<7BLIm2;&`PaMkjJCIXZ@#fiiC*OY
z9`z)@p1$??#I!y)R+0zn$I|n@M
zdqCPK{RhQfBm?E1#p2R`M=J$q<`@@}G>0b=?y@q2I3M{Dj_sbM<+Z)Mem0RCv-Hydrj64c*fU9-C>7lgt}2QArj%xl2EY(e&4;q_U&=-IKGnM_oLYSTp^xrU$CP1HHVRF|5fU{a$1i|lB
zNec~T@IlTXa#lnZl2t^vJVS`TUNol=yJ-&`v^&BTvu+@Dq8QFkPf3shkI(fqC&uV(
zZXiA)vt-YGjD0o70H|5gO#-+y5PO~!qx5NDiW5+9cnTDo9N-Ij_5(1Qh$T?k?_mn|MDA&X03v?s}w2~3mYlvrW
z*ge^!QX&P7#YXD?{?S=A955aK_)Ez1{IBzQj8V0Bw3GaZsRE6Yw-E-&A!~1CAES9&0u>imCWYK?D&Z
zUukbaoibMpg~e()r&%oujjc+aW#AGiizTPDN+={Qm#Veu?Me0jfU?P?IF*^df*4x(B*w1Bm$WlGEANaOibdogW9vV6pLC;099D*(YKDq?dZZM2{BDviChu#RF>T2^BbZo_A#U>*>W*=*b4{kB;8JO<^ttTGX6Nx(i7a
z)^=?cJjypTquyHI3}*}EVBlb7)_nX*JMZjAp^sZH#u#Hq>Y1y~Yq71rG|{AwNa$w5
zrU_`d0JC8Xnn3pi;8Qw*9OO&?o)F*@=FwyF0P&32={&$!{I4-`{!{w_YCQ0?#s0VP
zG(gr4Y(5P{m|r&lN0$o43Nf!(FeEeN{BIBX0vPtu)gL7O?06Xmoh*Qv4fK$^?20HufS`IyhUPwAm{2EYlfMKN_Fx7AxU~Z=;(tu8jNxl9^
zFD(VHfxYQsIe;Jquy$Gu*azr)@-67q&q9hL9?Cc4xz;o_%igr!+xGJh|BQ-afj={+
zzefkWwr8ZIV@Up6J4~)z{NvKc3-PqCCQRB!L$PZjpYy^LlWo?%r{bu?sbH#eK{@JP
z4aIAY)O4Z>8%rGQD`{X~#Ao_8`@bCMSPRaID=hgH;t?rM^{?)-Pns%3Rc$r%?tGpm
z+;LG+HNuN*%RE;jkn*rSTO=J1Mbp4QnTNFreGRrt-~yDnI?L}$jhKG;afKsBih5XO
zUC?7>SHF@4YgnWm3Py*EG-;@~g}Xb|6RFzX?txg%VG!R*gavS
z^U>c!_13gmNbrsXQc2&)+s>HxgGBzD!k1pyd+t6rF7>!WmI^+m80xWpP7{;TQq~3T
z7l<+c-9-k60Rp6#;5=*Cu(VFDM&ebQL%haU7FqbY?(Mifos?^1{3g$EtAydEw!y`e
zGiSTgepKFr#hk|421&bCs(<2Phrt#6W%Y$9@-`pGg;$pfP=<-M}5zi8+jo*-qR58faXpA)D{~2czje{X(=eE
zEc=Bw#zO~Lo0?z6@vd4IcC-3kJ^Q7$yVX8pI|{!lPkTJ--05yph3F5u`pr8Whu(=E
z5_jef{Is&!UZI~w!HYjW@knmRxtupc*<;<@)?Xi0!nqR=wAG^DGET*MNM=Md!VZHP
zw*w1Ne@f22ksownSm_{mx{jioE?4jz$={)
z6tP*BT3C*uhHOa8L){%+FWVb`zp;G%TSPrIDfAg*8!#mie#R%MF*rO8ClAR-$cgZNf1;~N&Fn3Ex#V(Z(4-HD!O?dgarOZD(c-o7R?(Di|s^#R$Qlcj*@h?v6TYk*_>PYOWj|LN&~b`bOcXcqtJl+g8afKCx;
z0~vFkdIBvWoi`)r1t2|;z-}#77*vxyBI1^mEOED5>E$QOK&x{c!ocqXp=%2eVDuFe
z9R?F2kk$h&K#7j776fd)7=4i)$gX1Luy+yToOnOD^Cr;R?<;}-MvN5R1(l@2kpPBx
z8JUKk8)8;5RmyK^kj)Utozf$op{Ytz4`{My5lPF-h=Jw6ET0w}Gs0`RL2irem=-8%
zjPuAw6Aa)sa$J_Lyz&O0(ePu_%m!}S&D;)GC1kP&5PFQ}dztJ5#8%Qqvorf|h
zvb|eADRnhy{iAce*&--c6KHHfoFn%85F0_FnUtS(LkULwtgpL-uXBffA2Ns}I)D__
zi$lQ+?pL^@+zi9I`J<&izjf?M8x4^6G5_f4|08ojO}D665VPi}S3c@8J|r&n!23`(
z#i5Tzl%Nq6+w)zMf;+UL3XY=^mQ)1f>yTaAM~LVq4p
zWc;dkgebx?mq_)>`Es%%Z1pr|UYS_#s~}>y^lnyzboiIkoyz!RsmlC)T(#
zg^eFm!`kycNwO{U@v;6550dO-9Ca}_m&YtOZ0d=hHg8o%lU_)FQMm7(!GDzA;&Oj7
zJ&^VDw+7ODz^*x-F^J4un!+y#{RRtb$u>;N%J|h|O%o8U7xtN!A`0Ib|GT|KW--|8
zu68VQeOUh?Me*Li;gwNw_vPgTgo{U(+oHe{PHV@7_7WB4r^
ze^s_pR#(_pA&7ijys(Ym+n_L#(V^pTf3g$x*Ra>uoswV5p569$IsjijTbz7-@pMUm
z^tGc-$x4Tn4x69v`M2lSDTxJS&kjj=O~MZPzcX86$l7yF?tk4>iDoWK;k?wT&ywmvYLcMob++d(sd~`p30q&apS?XZ{+66$A~(m`6-rMAXXT2i
z;Yi*1WdUUTx1<-`L0`A+jRnm}2xyJa{<>(?f<_pVNs+Oh@o3Tyi1&x+&)kbCXRYbX
zI!{)haR?^?x)@?O+1f@0g)m`
zT6Y1^7084r)8^)LYZ{l=Ew^S|jE^w?lhSVj138fZdMNrZPGyH`owvob1xMCCfynfm
z4Ru(%v;ns}C~GR&E|v&fgxX&141i(VSdp1$echlznCmsWGdyJCve3GynqExE&UMXe
zdJVK;r@DqcG;*oEHvVu!7WRZx#7`42C)nVmJRA+en~usGLzJw}wB8z(j>p~@G4=&|
zb$N6JTgN}BAzqsjFL+}=R8?FsIwz;HPAob!%dU6hG8F3VxZ)IT`VD?8FcleC3of)Z
zT7w4CZD{$EMR|_Z_O`eMmm0%zy|zjV_FgAFU9G>goIRcAwgXm1vRb#_|C`Phj?Lts
zYr+(f9{T$C`Z$m4Ah*hFHeH{uH5c=u7SP7mLlSeyOqfZz1GM{Cqjj=7(<9|H&h`x@
z@3iQi>42E-vVMgp;6;JasxzaDl?v(>~zB|-u
zW4x{n`&h)|^(m`D8Dn>CNZrzgiHT68u(!q2^WZshtREaKZ}j2wv5UK(?%WYrlrY!%
zxAg&Pg6j^oejJ%aQ6XUR*<#JgOkT(_5M-i8xr@P9G6K
zo+bMOELfWnTxA@cfiSe%KJISl#O9A*30D{!h}n#ENeMJ8w#*rfx!6XvG<-2(s;=JD
z(PTM{gaytpNXtlOA?67Hu%fDtf96hZU)0lb)Jr&+JJ1n0L4BlB9zF1)jm25Vm~BoA=P@&ILf5Qutrq8R%4x&DDZT@
zI~e2IE}nFr3cv;2^-RiM%_A)Df($9F=QsKNX0&yz96ur$UU9k|-H+X{Hr7WEGa!dh
z&cKLH%vpbWuHA52{oid4ng2-M{poHAX-?KcPU?u|wYyhk|92IZ3___xfeExif+Vj2)J+VXQNbD?tc_*rYrxW_I)*AltW9$c|2z=jl-kXUTT#6_+GRP{
z@pDuVVw5;?Gx&jo5yQBYF~ZI>x_C+#-~gai?V_aEJk!F6!QFf#rg6
zQmc%OwA=6~XExN4+xc*7&t#`sd(au|!aEnd$LKmn=Gu%<^rx}aK}H@?k&TuDH;3r86r4n*M{C
zMK7|R1Va)UH`fyjG2s20{+cX$_cQ9DjP@SYjzt^;
zmi{}EdUv1qSZ35$y(#%)p8_3V&ZX61)DWH4z~M2Vh#5z>8hLjuyML8p!z@}nB!uZ(
zYTfGfI!h~qsH?s4hm5}2op~4&Oi#RaHz!>AZ0HKr-jIUD6`SU=LQ!2%<60T-=ahh^
z%3Ai%`>P-9e@?At;uG-IUzUHYo;cPf-_LQz>2_bzWcNtFJ#tM}^=#O}>C}F&CVWLK
zk(0zb-TEnXBv3Sid(fwZu*=R$4tJ4@Qpuj4TtN5;ZVGR$FUB{G!3Ta#3)yZD{UhRS
z++^2&uOI_^x~Vg(%d|N~N*6hIRtf*IS7>{2o^BT6Ts4;dMi^q!#bMP}6(y2aBdJP{
z_cvJaUU4cez!T?3J)D{0Un%2Tx(7{qjWL_LgDy9E*vuu|gDEjwFtXhRYvnB&qPJxy
zE;q;~I-ZJmn+$$kLvy7)41c1ddHRZ3!r?oT4B7E
zII`)3n_xhzyR$GoGRp&knSm6}ob-3gT+l}VKK;=}mztcs(Jz8{lSmx5uG9+{ZMS95
z5X)ghr8DkW^ZX~-9Ovjp3!H_=(QqLFtCF|?V!D)Pk4p55`uV2=&M9k?w3(LDEe>H@
z5VHr}tZU9lL1}5^A4zp5v6e|JY@Ycsh6VQ*T5RC1y>T-Z@+AcH1f)4-A;B
zWiA#AAZsTV8$8rK0^?@Tfo)ntsdA#+^*X0HoJQF=@pO++B@(o`L3SE#N>xG~yKdDwUa-m{Ley4>qK)k;t`1&+n|uI=J9B1<&iS(a#FY$g;1OeR}KrRm$_9LJ>X
z#6U#cBK3^@0mTyU{pynxwsVc(0CEkOW4mXb9vYB!?e2_T`+V2i>B~#5@mNdcv*Y;O
zd8-x?BXF|?jdhi*1w~Ex@MF762EvpB0Fr4va%`;Kb-)UCUJ~J32^;%W={dpLn+fe&gjTv5qYz>|+Y
zCp`V@836H}>oo(6J=`GA_o3TluE`y+Wc&sMap9K-8R|87!&7bviITEdN+we=?C#l`
zhv;*`U3_93K8s$7N_u`;;{P-rYG+^bT{Ld?elUi5Od%0`{9=3p7R(9Bf&GQt+)H0&
zuiI%|CQxn%j)<)_7iK|+7vP^;gP!Zu%K4F~CRuYq$q5R)K(?s&1Xrj*ho*Ny}%*NaM
zby_heavA^-3iDk5md>+CAl{j?ePYZgM%7jwp0{hD^MCciLDT)m7}2Ty=cp$Gs@cWK
z_4061qvp$*rNzFyxrn?VHYs%NaRge|9>>va{ngjeHIaTX!_qhY=0LG^I_P^{NCdO;
z!<+JV-F(uO(V?7U?kXxj_4$ve-Ud3=Tk`EL+|7m_Na$-JWvH=HM5_K}v?P#d~>
zC7gs$p`arB*HKl751X&{Vi(&UQ{5+$BaO(73-^#1cTXVx^8Boc<&0hW#YJ3MM}*;$
zfC?dHPmRI>_Brgq^O^%Z8oHg?Rsp%7?)@XYb8#9)RVO`U4Fd)m=oM=pMXM6W&02V-
z-Z@qWj%^e_%U9S!qrF>=zWTYrqbG`-S}2gLAd&~%vhPX2uP@g^C2FxP?`%uQ{5`j>
z>U@&gVG6hUDN(ISrH8X?Bh|VFe$JDsiAOnG0f%^in(2nb$0exxJkJL|1?r`Odxr1e
zPK~)R%Eto!{%@?y^${_o9|+4IPl$b-jz{=wlA&O3bFGA}ibcz{Svn~k-x2Ncx!#eNr?XL8w(N*EI5b-~k95{LEEbU
zA<>ah;VGka%g0-(?9iBmJahR)!Kh%@)_+pZ(&?DOt6bFLC5^!<3NOF;+(OE?
zfin?{9-d`wO>CsHO8ifI=($L|Kj!hcU&yvUFd%r!n*4JKqY|INT34i7(%poHzaur9
zfa(JX_x3rfjXsMUM|)ZzJVM)9r=$;zILN6RhU;%^16>F;=_k2{)%@HM4WnGifdbP*rqAFe+!0a;Oh5su_`4y|fZ#)oE@G)ik%;|EkUVQw7o
zHh3P>)V5I#A-BS@5xL&l#Hc=FSpMT$epev_?&zN4%YRDNa4jf!e*X2-LI>08WBZkK
z`ZaQ;z0Q{IJm?n)Kb`U_=F#WdA0_|Ogxw8S0@##w>##(XEi06Q-j42v(2-Vrdet!2
zyZ>;^SOprNQ$NFQQHA#dg2Jg0lQIO9fPgocdiH78RLqVm`scuv*fhpQFEZd4t4
zXL>;Bywgb%I0mS3jC5#xPCJ*qB^mj%7DVD3+~`bm6%q;A@z-`#)puqTg?SL09vjcq
zZSehMn~Oj2T;u%tgl9F$3w}4SCB0;OW&CWFp)o>ojqbj}`@rZW25(wbEXrps5Sw*b
zvJ!Ao-qZy9E9z7X4&W=Lk|%ZRe@Bm0V;r0Mqp?OU>IyGp)rU()qATp&bBnXE*Kc*!
zfW3cG^`nM=$HP@m4+afztIy^1b43f!vfvFK_i5t?-F+G(dWD*S7qzlF-aunkx^Axt
zd~Vl%__B;PbEC!Xo85MKT$xg#bc;nnUaG$?2MLsFy!lU_S$*NYIEX@
z3k|wuP2Pl6iaKu`u)pO)+&PqDdHkUz{!W)yRptdRMcKDMQ_hekLy(cB5i<#iSNAM*
zB+rsk3i4zP1M50o@_I+wpI5D-Tt_-=^5oeh})(T#%qA`ah|nk?_V)%eJP7>eg_k
zzX62ssk!>oyp4DK>Io9o{`Mnk^o6j|xwXy3e*`eRaMQ$g`h5NNwUZ!f6*%p|E(d=2
zRjD2S`X0D<3gO-3DdED$~^GiQYh%>vf%46yS&nt%%h~;R7
z)TsO-lop)UGRyw65t(%?g~2^GpgkSzM(mm}jSitj>}zhc7=O$xBz#wZo@iLrxW}TZ
zUJ**GJ}FlkSj&dI7ZGQpg}fLCaqe`|0+G?Ag|>q|6$9UG1aL*M`2v@0DqFe#)7SNg
ztifYXg9NMluVPw42NA
z_MLiq3`)nCfwD76$eJ!rS&<6ZP};9MdgiQaN3U&V=a0sc{J4C2OwIR@>5lTD=+;q2
zRdGyGIiCnkW3$>~;`vdalPBTDsj;lDg`AtqCRYt1@Jg9OGh1TWB`AgtAkgLpn$#)^
zJ3XSDY1D|72T^B2r4?&~S-68S0b8u#6
zg^4ywU9DF%O+{#>HJH4d^&6Y1-asl;CrWN`6v?4BR@rku2NNNe-3TQvRS7lA(b4hV%kTLMG0y6c!V+;PSJJ)B{Tso`P4#NZ>fVto*>l=i@ayT$
zk8Z&}DwXG-9xYTkS7DQ$buCbaL^meh;5Xf14@Q?KNuxs_&)pS!s<}?DiH0T{`strG
zviu&IWZ8r^2saz&zCST$KI>8oYniEcj{$z2;{6~XfaCoBP%fVxz7F0OH&GInOjJd!
zjrXyU8rs!vS=UH2&L@>pz8bZ(>K5v8yLb=jjoKDGSmGPaKuM--b(oPBxf$o|+i2#2
z7{p&NFbp;|HeMs#D9z2f)j(GhsyGjAX2EFiOJ2Myjhm~4Fxy3JdRpH%-fO9$o!vVm
z$)&dryDFwp`_c731F!JHe)_Z6m8=wHHLYNC_*Sd@5wYh7arUU+Imdz9-JJw2i!5R#
zu22DsWb&=J5z*2=!`nKGBBWVw8SzJ-ETrcRT{QC6@owq=k~i^TgZ{GG!s3?fepT6`
ztiqJ0{w0LwF9F?2P&2^$Qh)4CCx<-7Age2m^T#9NkBm7O)8sDa+nP}g7SO%^r?D94
z>!WTqu|;h4U7iR9b-{$GAQ6jHV&-)pxO31Qr!Wv95U&D4I|M7x*7+hDWfVr`h}lWp
zh(NC<#WE}Qd&3viU2p>mZy=?lq%cB>!mQP2%&u$60Ej~rnLZr^wl#jmCU9bsg-VF;
z7IhpBNR<46f`mi&>Q$7fIOs=NpF_AUF+?^viJ_IB|MGv@-Bm
zUjSO6c@*P`^q2TEXb3T`>E8f72Y{$#f*52+_9Za
z#e_8`|5%!j`cLZE?{DK_M%YUAL@}&F^n($2qjgamXWQAOy}dftR_LpdQy^<9Kx-EV
zsweP_zZ41qGX9vD2BVt-Viq{7c`cDEYU@klo0$E9=LJirxT|8~O6lGLb}7=_>f+v|^B+H-mikz#x8u$}P|DwTWkX&C
z*G6tfbwr^y(IV7n-f3lXP!VGm4h8Wr_qd`1NQRN6IiNxx&0{N)(P;T(6ihp(*4q+k
zaz=dIC>2x0t9y64=bbul^N;s-_GhJ&4I)(-puWe%hc^7diQ`p1YUNgk
zHTYp84b=ksqPq2Oz6)r_-~_EUxeKk=Zs-;poNmso(E8@5-6ad~V!M|IxGId0-H{sr
zg)B=(yHhK^?-k-&wzCZhMt?xtK)H2&_33O0fL7+s!@lq+yfScnEG_5>6>YZoLJU)(
z1|4m}mO{caYf=D(g|sbCdIZ*cfO72f7?*E|C7j@=02re3sg}uJHdRUdNJHDmx^<=I
zY->nuM0VPW|7eQb3H#&YNwtMJN~=%L7aWkmIGQlccf`T%Q?Gd$`;Kaa|sW$OAczc6t4X=np!Idd89wV#9j|1RmWy1LQ$xsGR=2
z#NUm)KZjT@70XXw)FbUP$Cy7BL;MCw@I)Ty2He}otkXlI$5>zxnDNG-z5?(Sf4Vr2
zEjPRA5GI$F>5Rb?SfbLLx+vvNMOe_o#AA`il9ro_8odU?u5#P*Q6*AtqdzBBHy6=@
z1W01@cu{(?H=Q#t)Qw&wnnd`$8O5N9XSy_eW{qV)xKYKrJMKb3WzS>Rw()>a2?pOL
zr1%&D7{+TWyAuMtHYb38fV}zcp_hr^In*-)$B~}8BlF}~86xdr1Tml0!h2BI^@a*o
z*{t8|>$VblPxN^aGV@BCA8{`sZ@3K~m>2^m}y70lX
zS29x44{En_Z+IV?Dkb%wM5uN~`4>JTPHQ4l59=w{ef|qu$!f#{GK41-6(SDGQtHir
zL{gZ7G`fexp9*waFq=r&@flRH$MmLL>Bq~@6P})*AzUmuwP^ce
zjxzp{FF~^um4u~5vc8Z9$+Mv)m_-$q*#yS?~IjKEfjvpi>d8<*h{Q^aYsS(8Rb
z)oJ~)$vqKNk2NwM-{jM7zj~G2s#7h0fxv8S30I(Q<1n)i@Qzii8|l>iJ_zz7S-H9w
zaB-dMoR!2Y5hQCl2A0SzzAEcuJ6D&{{~r3X?dtP}^;-RQvcF4bia~|bY&FQ(QfR20
zJQRt-IzoOXUwDA302;AI7(+gN-G%U-w60R~;Lo1@)TqOxp;NI66|Sf;%#}oJW#i
z947FoRo=*2Twz;o-+h4-dXICnedc!jq@?&J()v{Uj2#99FekoZ2*9M5zrwjYgp2QM
zp%a0_n?*`plnUj*zbHm67rn1a5?H4iPHg!b*cOD9#1|Ifl{6vg-0a33_H%ir>*L^*
z`6nop?LTD?IacF>;?v>H`Q0SU{l!ONn?_elN6f!g&ClJOXLG!NRdOf8Q*0;$-XWP@
zeS<$)x%yVa?UfyY<|_2`CYScnxU9w;Q=72yzMmt_uF;B{YhH>2p$%1bL?7HW{wx0l
z83|9pTd~P;D5tEeszERSbpoDutMR^9(50@EL-Nl2l9FS%+Pmj-d^u4QRREQGo$ICufeA<~~&%
zusSYn@J$}{5qNz7EK5XamZRGi#yKF7#@11o1dp)!1AtZW^Y}cTmq}-0s@!7
zw`U{V#+=<_Uq$&PfqqN+YP+jjA7+ghPxZ}ByTl{=>SutUVZ-v<@|w2b1<~F5A#x@H
z+Bs(EcTM|GU$xtxCpf3+>MPR`$jEuP`>BoP`f-q`!|rQ~KEdQ7+Jzq@vNN^G`zGt)
z00^(c$n=T+UZvOuOn?XBBe6z2vH3eXtgjtIedMY;=dQ6YJ)bo5h(VzA1##M-yTqQvH-f
zC`jC~6#T+wtV*MgUzLE#ICiFBSSS*$pIcy@d{s5&0NjX4Z;QtDf_@qD7uSq)p|4gS
z>mjLzUw;EhNe9{19QIVNxb^QvZ_J|DR&rX27W0j#h}wIL8Br9`bfz8(`KLv!(ODNR
zP-0FTt5BcZ&_38T^0{PMcpyQNMQ!Ub2X==W2)sD{zkOGun|4oQyfmB$=ySZ3m6l0w
z^r4aQfKMOB_`)%~@`uP{{4Ja6z0=I-2saFbXE-33ueW2YDF`db|4AL3;BWkpGZaW^
zisiwYl!{mAB-*!m8+VB`w++66CO})Zd>WGQyGa-9Ticubc8fiK=Jw9Lti5vKd|2gZ
z(${5UV;8hL7iLAq8p>lV^Ci!r>CPt`w#-U>^nlkI30A&
zSi8tle(qFG8;!gE5@Vt}tAbQ?HzkKnEN8Apic)@1G9-dJV6Pg%sfrZ~t_%j9H|)e%
zB^&k)Xhg8nGM!Rj(XiI0p$(D9O}enJ%UD-B!{gRjRL$ZQpNjQLuw%6+Ua&4&oedQX
zc0rm_gfJl9+^;WGr>~j1uYF>I&Q-z(&y2LhovU6H2~FwqtehlAfb_^z*3{N)9ftiO
zY%w=o-_tYU_3F~