<div dir="ltr">Sorry, that last attachment was just a slide show of the topic 3 recording, here is the full funding opportunity announcement - letter with 200 word abstract are due May 7th</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 3, 2019 at 8:40 AM Mark Mikofski <<a href="mailto:mikofski@berkeley.edu">mikofski@berkeley.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Ralf, and others,<div><br></div><div>Sorry for the late notice, but there is are several funding opportunities in solar, including one for $350,000 to develop open source software to lower soft costs of solar.</div><div><a href="https://eere-exchange.energy.gov/#FoaId45eda43a-e826-4481-ae7a-cc6e8ed4fdae" target="_blank">https://eere-exchange.energy.gov/#FoaId45eda43a-e826-4481-ae7a-cc6e8ed4fdae</a> </div><div>see topic 3.4 specifically in attached PDF - also note to view the recording the password is "<strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:12.8px;vertical-align:baseline;color:rgb(60,67,73);background-color:rgb(238,238,238)">Setofoa2019"</strong> it's about 30 minutes long.</div><div><br></div><div>I know that this is a extremely niche, but as a few others have said, [the DOE] grants tend to be very specific, but perhaps we can creatively think of ways to channel funds to NumPy and SciPy.</div><div><br></div><div>Also there is a cost share that is typically 20%, which would be a non-starter for volunteer projects.</div><div><br></div><div>But here's an idea, perhaps partnering with a company, like mine (DNV GL) who is applying for the grant, and who uses NumPy,and could pay the cost share, and then we collaborate on something that is required to complete the project, which is contributed to NumPy (or SciPy) - but we would have to figure what we could align on.</div><div><br></div><div>Seems like NumFOCUS, Quantsight, or some other company in the OSS space could figure out ways to help connect companies, OSS projects, and funding opportunities like these, where there's a possibility of alignment and mutual benefit?</div><div><br></div><div>The full list of funding opportunities is here:</div><div><a href="https://eere-exchange.energy.gov/" target="_blank">https://eere-exchange.energy.gov/</a> </div><div><br></div><div>Best Regards,</div><div>Mark <br></div><div> <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 2, 2019 at 11:52 PM Ralf Gommers <<a href="mailto:ralf.gommers@gmail.com" target="_blank">ralf.gommers@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 3, 2019 at 3:49 AM Stephen Waterbury <<a href="mailto:waterbug@pangalactic.us" target="_blank">waterbug@pangalactic.us</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>P.S. If anyone wants to continue this discussion at SciPy 2019,<br>
I will be there (on my own nickel! ;) ...<br></p></div></blockquote><div><br></div><div>Thanks for the input Stephen, and looking forward to see you at SciPy'19!</div><div><br></div><div>Ralf</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><p>
</p>
<p>Steve<br>
</p>
<p>On 5/2/19 9:45 PM, Stephen Waterbury wrote:
</p><blockquote type="cite">
<p>I am a NASA pythonista (for 20+ years ;), but you can now say
you know<br>
yet another person at NASA who has no idea this even exists
... :)<br>
Not only do I not know of that, but I know of NASA policies
that make<br>
it very difficult for NASA civil servants to contribute to
open source<br>
projects -- quite hypocritical, given the amount of open
source<br>
code that NASA (like all other large organizations) depends
critically<br>
on, but it's a fact.<br>
</p>
<p>Cheers,<br>
Steve Waterbury<br>
</p>
<p>(CLEARLY **NOT** SPEAKING IN ANY OFFICIAL CAPACITY FOR NASA
OR<br>
THE U.S. GOVERNMENT AS A WHOLE! Hence the personal email<br>
address. :)<br>
</p>
<p>On 5/2/19 9:31 PM, Chris Barker - NOAA Federal wrote: </p>
<blockquote type="cite">
<div dir="ltr">Sounds like this is a NASA specific thing, in
which case, I guess someone at NASA would need to step up.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">I’m afraid I know no pythonistas at NASA. </div>
<div dir="ltr"><br>
</div>
<div dir="ltr">But I’ll poke around NOAA to see if there’s
anything similar.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">-CHB</div>
<div dir="ltr"><br>
On Apr 25, 2019, at 1:04 PM, Ralf Gommers <<a href="mailto:ralf.gommers@gmail.com" target="_blank">ralf.gommers@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Apr 20,
2019 at 12:41 PM Ralf Gommers <<a href="mailto:ralf.gommers@gmail.com" target="_blank">ralf.gommers@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu,
Apr 18, 2019 at 10:03 PM Joe Harrington
<<a href="mailto:jh@physics.ucf.edu" target="_blank">jh@physics.ucf.edu</a>>
wrote:<br>
</div>
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
3. There's such a thing as a
share-in-savings contract at NASA, in
which <br>
you calculate a savings, such as from
avoided costs of licensing IDL or <br>
Matlab, and say you'll develop a
replacement for that product that costs <br>
less, in exchange for a portion of the
savings. These are rare and few <br>
people know about them, but one presenter
to the committee did discuss <br>
them and thought they'd be appropriate.
I've always felt that we could <br>
get a chunk of change this way, and was
surprised to find that the <br>
approach exists and has a name. About 3
of 4 people I talk to at NASA <br>
have no idea this even exists, though, and
I haven't pursued it to its <br>
logical end to see if it's viable.<br>
</blockquote>
<div><br>
</div>
<div>I've heard of these. Definitely worth
looking into.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>It seems to be hard to find any information
about these share-in-savings contracts. The
closest thing I found is this: <a href="https://www.federalregister.gov/documents/2018/06/22/2018-13463/nasa-federal-acquisition-regulation-supplement-removal-of-reference-to-the-shared-savings-policy-and" target="_blank">https://www.federalregister.gov/documents/2018/06/22/2018-13463/nasa-federal-acquisition-regulation-supplement-removal-of-reference-to-the-shared-savings-policy-and</a></div>
<div><br>
</div>
<div>It is called "Shared Savings" there, and was
replaced last year by something called "Value
Engineering Change Proposal". If anyone can
comment on whether that's the same thing as Joe
meant and whether this is worth following up on,
that would be very helpful.</div>
<div><br>
</div>
<div>Cheers,<br>
</div>
<div>Ralf</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><span>_______________________________________________</span><br>
<span>NumPy-Discussion mailing list</span><br>
<span><a href="mailto:NumPy-Discussion@python.org" target="_blank">NumPy-Discussion@python.org</a></span><br>
<span><a href="https://mail.python.org/mailman/listinfo/numpy-discussion" target="_blank">https://mail.python.org/mailman/listinfo/numpy-discussion</a></span><br>
</div>
</blockquote>
<br>
<fieldset class="gmail-m_-198833309036954763gmail-m_-6347244135149987628gmail-m_4561481477175257535mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_-198833309036954763gmail-m_-6347244135149987628gmail-m_4561481477175257535moz-quote-pre">_______________________________________________
NumPy-Discussion mailing list
<a class="gmail-m_-198833309036954763gmail-m_-6347244135149987628gmail-m_4561481477175257535moz-txt-link-abbreviated" href="mailto:NumPy-Discussion@python.org" target="_blank">NumPy-Discussion@python.org</a>
<a class="gmail-m_-198833309036954763gmail-m_-6347244135149987628gmail-m_4561481477175257535moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/numpy-discussion" target="_blank">https://mail.python.org/mailman/listinfo/numpy-discussion</a>
</pre>
</blockquote>
<p><br>
</p>
</blockquote>
<p></p>
<p><br>
</p>
</div>
_______________________________________________<br>
NumPy-Discussion mailing list<br>
<a href="mailto:NumPy-Discussion@python.org" target="_blank">NumPy-Discussion@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/numpy-discussion" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/numpy-discussion</a><br>
</blockquote></div></div>
_______________________________________________<br>
NumPy-Discussion mailing list<br>
<a href="mailto:NumPy-Discussion@python.org" target="_blank">NumPy-Discussion@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/numpy-discussion" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/numpy-discussion</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_-198833309036954763gmail_signature"><div dir="ltr"><div><div><span style="font-size:12.8px">Mark Mikofski, PhD (2005)</span><br></div><div><span style="font-size:12.8px"><i>Fiat Lux</i></span><br></div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div><span style="font-size:12.8px">Mark Mikofski, PhD (2005)</span><br></div><div><span style="font-size:12.8px"><i>Fiat Lux</i></span><br></div></div></div></div>