From: Saalim Quadri <danascape@gmail.com>
To: danascape@gmail.com
Cc: linux-erofs@lists.ozlabs.org
Subject: [question] GSoC Proposal 2026
Date: Sun, 22 Feb 2026 03:12:58 +0530 [thread overview]
Message-ID: <20260221214258.129214-1-danascape@gmail.com> (raw)
Hi everyone, I am Saalim Quadri an undergrad student at Dayananda Sagar College of Engineering, pursuing Electronics and Communications.
I wish to participate in the GSoC 2026 as a part of the EROFS filesystem.
I have been contributing to the Linux Kernel and have more than 10 accepted patches.
I have also worked with Android Linux Ecosystem in the past years, and have worked on several subsystems, backports and fixes.
I started looking into https://erofs.docs.kernel.org/en/latest/roadmap.html, and I am interested in expanding erofs-utils to stabilize liberofs APIs.
In that sense, I would like to know if anyone in the community could provide with some suggestions for my proposal, and a positive impact.
Any suggestion or hint is appreciated!
Sincerely,
Saalim Quadri
next reply other threads:[~2026-02-21 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 21:42 Saalim Quadri [this message]
2026-02-24 5:52 ` [question] GSoC Proposal 2026 Gao Xiang
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=20260221214258.129214-1-danascape@gmail.com \
--to=danascape@gmail.com \
--cc=linux-erofs@lists.ozlabs.org \
/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