<div dir="ltr">Karl, <div> Thanks for the effort. I feel we should have had less projects and instead gave a good introduction to one or two. Lessons for next year.<div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">--Junchao Zhang</div></div></div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 22, 2023 at 10:48 PM Karl Rupp <<a href="mailto:rupp@iue.tuwien.ac.at">rupp@iue.tuwien.ac.at</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">Dear all,<br>
<br>
unfortunately our application for the Google Summer of Code 2023 got <br>
rejected. I haven't received any feedback on the reasons yet; however, <br>
looking at our GSoC ideas list I can see that we haven't done a good <br>
enough job to describe our GSoC-projects.<br>
<br>
Well, we can take this as input for a better application next year :-)<br>
<br>
Best regards,<br>
Karli<br>
<br>
<br>
On 2/7/23 18:37, Karl Rupp wrote:<br>
> Dear all,<br>
> <br>
> thanks for all the input and help. Our application has been submitted, <br>
> let's keep our fingers crossed.<br>
> <br>
> Also, this is a friendly reminder to fill out the details on the <br>
> GSoC-topics:<br>
> <a href="https://gitlab.com/petsc/petsc/-/issues/?search=GSoC" rel="noreferrer" target="_blank">https://gitlab.com/petsc/petsc/-/issues/?search=GSoC</a><br>
> Part of the evaluation is whether our ideas are properly communicated. :-)<br>
> <br>
> Thanks and best regards,<br>
> Karli<br>
> <br>
> <br>
> <br>
> On 2/6/23 20:24, Karl Rupp wrote:<br>
>> Hello all,<br>
>><br>
>> thanks for proposing projects. I've created the suggestions so far as <br>
>> 'issues' in the issue tracker on Gitlab, prefixed by 'GSoC:'. Please <br>
>> add a better description to your suggestions so that applicants get a <br>
>> better idea of what that project is all about and how to get started. :-)<br>
>><br>
>> Also, Satish, Junchao, Jed, and Matt should have received invitations <br>
>> to join the PETSc org for GSoC 2023. Please join today, as we need to <br>
>> apply by tomorrow (Tuesday) 18:00 UTC.<br>
>><br>
>> I've got one question regarding payment processing; since that is a <br>
>> bit sensitive, I'll send it to the private list petsc-maint.<br>
>><br>
>> Thanks and best regards,<br>
>> Karli<br>
>><br>
>><br>
>><br>
>> On 2/4/23 20:46, Matthew Knepley wrote:<br>
>>> On Fri, Feb 3, 2023 at 6:28 PM Jed Brown <<a href="mailto:jed@jedbrown.org" target="_blank">jed@jedbrown.org</a> <br>
>>> <mailto:<a href="mailto:jed@jedbrown.org" target="_blank">jed@jedbrown.org</a>>> wrote:<br>
>>><br>
>>> Thanks for proposing this. Some ideas:<br>
>>><br>
>>> * DMPlex+libCEED automation<br>
>>> * Pipelined Krylov methods using Rust async<br>
>>> * Differentiable programming using Enzyme with PETSc<br>
>>><br>
>>><br>
>>> I like all those.<br>
>>><br>
>>> Matt<br>
>>><br>
>>> Karl Rupp <<a href="mailto:rupp@iue.tuwien.ac.at" target="_blank">rupp@iue.tuwien.ac.at</a> <mailto:<a href="mailto:rupp@iue.tuwien.ac.at" target="_blank">rupp@iue.tuwien.ac.at</a>>> <br>
>>> writes:<br>
>>><br>
>>> > Dear PETSc developers,<br>
>>> ><br>
>>> > in order to attract students to PETSc development, I'm thinking<br>
>>> about a<br>
>>> > PETSc application for Google Summer of Code (GSoC) 2023:<br>
>>> > <a href="https://summerofcode.withgoogle.com/programs/2023" rel="noreferrer" target="_blank">https://summerofcode.withgoogle.com/programs/2023</a><br>
>>> <<a href="https://summerofcode.withgoogle.com/programs/2023" rel="noreferrer" target="_blank">https://summerofcode.withgoogle.com/programs/2023</a>><br>
>>> ><br>
>>> > The org application deadline is February 7, i.e. in 4 days. This<br>
>>> > application is - roughly speaking - a form with a state of intent<br>
>>> and a<br>
>>> > justification why the project is a good fit for GSoC. I've done<br>
>>> this in<br>
>>> > the past (~2010-12) and can do the paperwork again this year.<br>
>>> ><br>
>>> > What is required:<br>
>>> > - PETSc developers, who are willing to act as mentors<br>
>>> throughout the<br>
>>> > program.<br>
>>> > - A few good project ideas (e.g. MATDENSE for GPUs) for<br>
>>> > contributors/students to work on<br>
>>> ><br>
>>> > It used to be that new organizations will get at most 2 <br>
>>> contributor<br>
>>> > slots assigned. That's fair, because one must not <br>
>>> underestimate the<br>
>>> > effort that goes into mentoring.<br>
>>> ><br>
>>> > Thoughts? Shall we apply (yes/no)? If yes, are you willing to be<br>
>>> mentor?<br>
>>> > The more mentors, the better; it underlines the importance of the<br>
>>> > project and indicates that contributors will find a good <br>
>>> environment.<br>
>>> ><br>
>>> > Thanks and best regards,<br>
>>> > Karli<br>
>>><br>
>>><br>
>>><br>
>>> -- <br>
>>> What most experimenters take for granted before they begin their <br>
>>> experiments is infinitely more interesting than any results to which <br>
>>> their experiments lead.<br>
>>> -- Norbert Wiener<br>
>>><br>
>>> <a href="https://www.cse.buffalo.edu/~knepley/" rel="noreferrer" target="_blank">https://www.cse.buffalo.edu/~knepley/</a> <br>
>>> <<a href="http://www.cse.buffalo.edu/~knepley/" rel="noreferrer" target="_blank">http://www.cse.buffalo.edu/~knepley/</a>><br>
</blockquote></div>