Linux IIO development
 help / color / mirror / Atom feed
From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: Saalim Quadri <danascape@gmail.com>
Cc: jic23@kernel.org, dragos.bogdan@analog.com,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	marcelo.schmitt@analog.com
Subject: Re: GSoC Proposal 2025
Date: Sat, 5 Apr 2025 15:26:17 -0300	[thread overview]
Message-ID: <Z_F1ybM7B3g2WHvx@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20250405062348.43025-1-danascape@gmail.com>

Hi Saalim,

On 04/05, Saalim Quadri wrote:
> Thank you very much for the responses, albeit late, it took me sometime
> I was studying about the working on IIO, and the proposed driver on the GSoC page [1]
> 
> This is my draft proposal: [2]
> I am continuing on the same thread, as you mentioned, to keep it on the public list.
> I have enabled comments, to ease up the review on your end, such that you can identify if any issue is present and point it out.
> 
> My major doubt in the proposal is regarding the timeline of the project.

I've added a proposal template to the IIO project page. The template has a
timeline initial draft. You may check out the template and adapt/extend the
initial timeline from there.

Elaborating a good work plan is probably the hardest part of making a good
proposal and requires students to either study the provided material in the
project page or have some development experience (or both). The work schedule
doesn't need to describe everything in detail, but the more reasonable your plan
to achieve project goals is, the better it may convey you as a good candidate.

I'll review all proposals after they are submitted.

> 
> I also would like to suggest, if we are able to complete our first driver before the evaluation, then we can discuss working on
> a second sensor, if that is alright and if we are able to complete it within the time.

When time and energy allow, the sky is the limit. My estimation, though, is that
developing a driver for one part will be more than enough work for a GSoC.
Still, if you are excited about doing more for IIO, then sure, add that to your
proposal.

> 
> [1]: https://wiki.linuxfoundation.org/gsoc/2025-gsoc-iio-driver
> [2]: https://docs.google.com/document/d/18R_ZNWn36mAG9gb2TqepuxBwj-Hck3CrZHFfWUuNmyo/edit?usp=sharing
> 
> Thank you very much,
> 
> Sincerely,
> Saalim Quadri

Regards,
Marcelo

  reply	other threads:[~2025-04-05 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 11:33 GSoC Proposal 2025 Saalim Quadri
2025-03-03  5:05 ` Marcelo Schmitt
2025-03-06  0:31   ` Saalim Quadri
2025-03-08 15:27     ` Marcelo Schmitt
2025-03-09 16:19       ` Jonathan Cameron
2025-04-05  6:23         ` Saalim Quadri
2025-04-05 18:26           ` Marcelo Schmitt [this message]
2025-04-06 13:31             ` Saalim Quadri

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_F1ybM7B3g2WHvx@debian-BULLSEYE-live-builder-AMD64 \
    --to=marcelo.schmitt1@gmail.com \
    --cc=danascape@gmail.com \
    --cc=dragos.bogdan@analog.com \
    --cc=jic23@kernel.org \
    --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