public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ayush Singh" <ayushdevel1325@gmail.com>
To: devel@edk2.groups.io
Cc: Bret.Barkelew@microsoft.com, nathaniel.l.desimone@intel.com,
	 mhaeuser@posteo.de
Subject: Applying for GSoC 2022: Add Rust Support to EDK II
Date: Mon, 4 Apr 2022 22:48:08 +0530	[thread overview]
Message-ID: <CA+Yfj7s7cMbDDz0CMEb8hr4e5RFWw-RTVgcXqZrah=v3xQjKEg@mail.gmail.com> (raw)

Hello everyone, I am a 2nd-year University Student from India. I am
interested in applying for adding Rust support to EDK2. I have already
introduced myself to the mailing list earlier
(https://edk2.groups.io/g/devel/message/87637) and have even submitted
some patches for the edkii-rust branch in edk2-staging (which were not
merged since that branch seems to be abandoned now).
- https://edk2.groups.io/g/devel/message/87753
- https://edk2.groups.io/g/devel/message/87754
- https://edk2.groups.io/g/devel/message/87755
- https://edk2.groups.io/g/devel/message/87756

Anyway, since no mentor has been listed for this project, I was
wondering who should I discuss the proposal with? Normally, I think
one is supposed to discuss the proposal details with a mentor in form
of a google doc or something before submitting an application. So
should I directly start by submitting a proposal through the GSoC
application portal? Or is there someone I should contact first?

Ayush Singh

             reply	other threads:[~2022-04-04 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 17:18 Ayush Singh [this message]
2022-04-06 20:15 ` [edk2-devel] Applying for GSoC 2022: Add Rust Support to EDK II Pedro Falcato
2022-04-07 12:01   ` Ayush Singh
2022-04-07 21:03 ` Nate DeSimone
2022-04-08 12:41   ` Ayush Singh
2022-04-14  1:00     ` Nate DeSimone
2022-04-16 18:10       ` Ayush Singh

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-list 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='CA+Yfj7s7cMbDDz0CMEb8hr4e5RFWw-RTVgcXqZrah=v3xQjKEg@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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