[petsc-dev] Apply for Google Summer of Code 2023?

Karl Rupp rupp at iue.tuwien.ac.at
Wed Feb 22 22:48:11 CST 2023


Dear all,

unfortunately our application for the Google Summer of Code 2023 got 
rejected. I haven't received any feedback on the reasons yet; however, 
looking at our GSoC ideas list I can see that we haven't done a good 
enough job to describe our GSoC-projects.

Well, we can take this as input for a better application next year :-)

Best regards,
Karli


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


More information about the petsc-dev mailing list