From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: GSoC Support <gsoc-support@google.com>
Cc: "linux-erofs@lists.ozlabs.org" <linux-erofs@lists.ozlabs.org>,
"bushrahz.giki@gmail.com" <bushrahz.giki@gmail.com>
Subject: Re: Request for Late Proposal Submission – Medical Emergency During Application Period [ ref:!00D1U013lbu.!500Kd0300s0L:ref ]
Date: Thu, 2 Apr 2026 14:50:59 +0800 [thread overview]
Message-ID: <9ada4eca-3dfa-4f25-8ae4-04ece5d1acbb@linux.alibaba.com> (raw)
In-Reply-To: <d_rMO000000000000000000000000000000000000000000000TCTM2J00loEVDwndQfigB8rc9Ozi4Q@sfdc.net>
Hi Admins,
On 2026/4/1 23:08, GSoC Support wrote:
> Registration and proposal submissions for Google Summer of Code 2026 closed on March 31 at 18:00 UTC.
>
> To maintain fairness for all participants, we do not grant extensions or exceptions for any reason. This includes:
>
> Misinterpretations of the timeline
> Technical issues or submission errors
> Internet outages
> Any other reason
>
> As stated in our guidelines, it is the applicant's responsibility to submit well in advance of the deadline.
>
> While the window for this year has closed, we encourage you to:
>
> Review the Contributor Guide at g.co/gsoc: Specifically the "Choosing an Organization" section.
> Stay Connected: Engage with organizations independently to prepare for future applications.
>
> Note: Due to our team's small size, we cannot respond to further inquiries regarding missed deadlines. We hope to see your application in a future cycle!
Thanks for the reply!
Yeah, we already have enough applications, and we don't
consider (or have any bandwidth to consider) any late
application as well.
Thanks,
Gao Xiang
>
> Best,
>
> GSoC Admins
prev parent reply other threads:[~2026-04-02 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 13:22 Request for Late Proposal Submission – Medical Emergency During Application Period Bushrah Zulfiqar
2026-04-01 15:08 ` Request for Late Proposal Submission – Medical Emergency During Application Period [ ref:!00D1U013lbu.!500Kd0300s0L:ref ] GSoC Support
2026-04-02 6:50 ` Gao Xiang [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=9ada4eca-3dfa-4f25-8ae4-04ece5d1acbb@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=bushrahz.giki@gmail.com \
--cc=gsoc-support@google.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