linux-kernel - Re: GSoC Proposal 2025

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z_F1ybM7B3g2WHvx@debian-BULLSEYE-live-builder-AMD64>
Date: Sat, 5 Apr 2025 15:26:17 -0300
From: Marcelo Schmitt <marcelo.schmitt1@...il.com>
To: Saalim Quadri <danascape@...il.com>
Cc: jic23@...nel.org, dragos.bogdan@...log.com, linux-iio@...r.kernel.org,
	linux-kernel@...r.kernel.org, marcelo.schmitt@...log.com
Subject: Re: GSoC Proposal 2025

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