public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marvin Häuser" <mhaeuser@posteo.de>
To: devel@edk2.groups.io, ayushdevel1325@gmail.com
Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>,
	nathaniel.l.desimone@intel.com, jiewen.yao@intel.com
Subject: Re: [edk2-devel] [GSoC 2022] Introducing Myself
Date: Thu, 17 Mar 2022 19:27:43 +0000	[thread overview]
Message-ID: <B923342C-7F94-4EAE-9EEF-0E403482E81F@posteo.de> (raw)
In-Reply-To: <xMkx.1647454008754449392.c7Tu@groups.io>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

Hey Ayush,

I heard Bret likes Rust. :) The Rust staging branch is owned by Jiewen. Nate handles GSoC. All CC’d (better get used to it fast :) ).

Best regards,
Marvin

> On 16. Mar 2022, at 23:16, ayushdevel1325@gmail.com wrote:
> Hello everyone,
> 
> I am Ayush Singh, a 2nd-year student from India. I am interested in the proposal: Add Rust support to EDK II.
> 
> I am experienced in Rust, C, and Python. However, I have very little experience with Assembly. I am currently participating in Season of KDE to write Rust Bindings for KConfig. I am also a collaborator in qmetaobject project which allows creating Qt applications with Rust.
> 
> While I have not done anything much that is so low-level, I am interested in learning more about bare-metal programming. I have also used Rust without std although it was when I was following along with the OS Philip Blog, so it was not all that special.
> 
> Are there any tasks for this project that I can complete? Due to COVID, my semester times are a bit off, so I don't have too much time to complete tasks right now, but I will try my best.
> 

[-- Attachment #2: Type: text/html, Size: 1947 bytes --]

      reply	other threads:[~2022-03-17 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 18:06 [GSoC 2022] Introducing Myself ayushdevel1325
2022-03-17 19:27 ` Marvin Häuser [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-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=B923342C-7F94-4EAE-9EEF-0E403482E81F@posteo.de \
    --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