# Gsoc'26 introduction

**URL:** https://precice.discourse.group/t/gsoc26-introduction/2823
**Category:** Google Summer of Code
**Tags:** gsoc-configuration, gsoc-period-reachout
**Created:** [March 11, 2026, 3:40pm UTC](https://precice.discourse.group/t/gsoc26-introduction/2823 "2026-03-11T15:40:57Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![nots1dd](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/nots1dd/32/3308_2.png) [@nots1dd](https://precice.discourse.group/u/nots1dd)
#### Post date: [March 11, 2026, 3:40pm UTC](https://precice.discourse.group/t/gsoc26-introduction/2823/1 "2026-03-11T15:40:57Z")

</div>

Hello everyone, sid here, am a pre final year cse student and i generally like to dive into low level software involving c, cpp or even asm on the off chance i understand it

I just happened to find precice on the orgs list and was always tempted to get involved with a hpc or scientific computing org just to try my hand and see how i fare and just learn from much more experienced devs and maintainers.

Not sure what else i need to add but i have had a pr merged and 2 are currently open, and i hope to do more (particular add MRs that resolve existing issues) and gradually understand the end-to-end logical flow of the project before i can start pitching ideas for the proposal

Looking forward to working with u guys 🙂

@Makis if i need to add anything else do let me know

---

<div class="post-metadata">

### Author: ![nots1dd](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/nots1dd/32/3308_2.png) [@nots1dd](https://precice.discourse.group/u/nots1dd)
#### Post date: [March 31, 2026, 5:37pm UTC](https://precice.discourse.group/t/gsoc26-introduction/2823/2 "2026-03-31T17:37:22Z")

</div>

Hi, just wanted to update on this, I have submitted my proposal for “Clean multi-step configuration” and I added something extra that I felt could potentially be added would love to hear your feedback on it regardless of my selection @fsimonis @Makis @uekerman (not sure if I can talk about it here now)

I would like to thank @fsimonis for taking the time to review my work, despite being really busy you were ready to help and providing the guidance to approaching a patch or code review. It may not have seemed like much at first glance but getting to know how seasoned devs or maintainers approach a problem really helps me analyze my shortcomings, and gives me a chance to reflect and do better.
