<div dir="ltr"><div dir="ltr">On Mon, Apr 1, 2019 at 2:31 PM Jed Brown <<a href="mailto:jed@jedbrown.org">jed@jedbrown.org</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Matthew Knepley via petsc-dev <<a href="mailto:petsc-dev@mcs.anl.gov" target="_blank">petsc-dev@mcs.anl.gov</a>> writes:<br>
<br>
> <a href="https://ford-foundation-6.forms.fm/digital-infrastructure-research-rfp/forms/4770" rel="noreferrer" target="_blank">https://ford-foundation-6.forms.fm/digital-infrastructure-research-rfp/forms/4770</a><br>
<br>
"Submissions were due on Jun 13, 2018 at 9:59pm."<br>
<br>
> Perhaps we would get funds to<br>
><br>
> 1) Cloudize our usage, along the lines Jed has been going<br>
><br>
> 2) Harden the automatic testing infrastructure, maybe incorporate<br>
> performance regression<br>
><br>
> 3) Bring the tutorials infrastructure into the 21st century<br>
<br>
GSoC could be appropriate. The big issue is people. Most developers<br>
here are not intrinsically motivated by devops, and people with devops<br>
expertise can make real money so what makes devops for PETSc more<br>
interesting than devops in any other setting?<br>
</blockquote></div><br clear="all"><div>The problems are much cooler than cat pictures?</div><div><br></div><div> Matt</div><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener</div><div><br></div><div><a href="http://www.cse.buffalo.edu/~knepley/" target="_blank">https://www.cse.buffalo.edu/~knepley/</a><br></div></div></div></div></div></div></div></div>