Linux IIO development
 help / color / mirror / Atom feed
From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: rose <i.roseoriana@gmail.com>
Cc: marcelo.schmitt@analog.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, dragos.bogdan@analog.com
Subject: Re: Guidance on GSoC 2025 and Future Involvement in IIO
Date: Sat, 29 Mar 2025 11:23:15 -0300	[thread overview]
Message-ID: <Z-gCU0apzDaKu1h0@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <Z-HSqixMyrfqAtq1@epsilon>

Hello Roseoriana,

Glad to know about your interest in the IIO driver GSoC project.
If you haven't already, please, have a look at the project page
https://wiki.linuxfoundation.org/gsoc/2025-gsoc-iio-driver.

On 03/25, rose wrote:
> Hi everyone!
> 
> 
> 
> Hope you're all doing well.I'm a CS student and has been interested in Linux kernel development,
> 
> While I'm still new to kernel contributions and open source in general,I'm really eager to learn and get started.
> 
> As a beginner, I find it a bit difficult to find good resources that could help me get comfortable with IIO or kernel
> 
> development. If anyone has some time, I’d really appreciate any suggestions or recommended resources that could help me.

The Linux Foundation offers a free introductory course for kernel development:
A Beginner’s Guide to Linux Kernel Development (LFD103)
https://training.linuxfoundation.org/training/a-beginners-guide-to-linux-kernel-development-lfd103/

Alternatively, I'd suggest to go through some of FLUSP's tutorials
https://flusp.ime.usp.br/kernel/qemu-libvirt-setup/
https://flusp.ime.usp.br/kernel/build-linux-for-arm/
https://flusp.ime.usp.br/kernel/modules-intro/
https://flusp.ime.usp.br/iio/iio-dummy-anatomy/
https://flusp.ime.usp.br/iio/experiment-one-iio-dummy/

> 
> I’m also interested in participating in GSoC 2025, but after looking at past proposals and timelines  that is 
> 
> asking for the exact time line which i  dont  know  yet  and have no experince  in contributing  so ,  I’m not sure if
> 
> someone totally new to the Linux kernel would have a good chance of getting accepted. Do you think it's worth applying,
> 
> or should I focus on contributing first and try in the future? Any advice would be really helpful!
> 
>  Looking forward to your thoughts.

I've added a proposal template to the project's page that might help in planning
a timeline. Though it will help you elaborate a good proposal if you have
previous contribution experience. Anyway, both plans are valid. You may apply
for GSoC 2025, and you may also start contributing to IIO. If you end up not
being accepted for GSoC 2025, you may consider contributing to IIO throughout
2025 and early 2026 to become a strong candidate for GSoC 2026. Choices are yours.

> 
> Thanks,
> Roseoriana
> 

Regards and best of luck,
Marcelo

      reply	other threads:[~2025-03-29 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24 21:46 Guidance on GSoC 2025 and Future Involvement in IIO rose
2025-03-29 14:23 ` Marcelo Schmitt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z-gCU0apzDaKu1h0@debian-BULLSEYE-live-builder-AMD64 \
    --to=marcelo.schmitt1@gmail.com \
    --cc=dragos.bogdan@analog.com \
    --cc=i.roseoriana@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt@analog.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox