From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Ayush Singh <ayushdevel1325@gmail.com>,
Erik Skultety <eskultet@redhat.com>,
marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Subject: Re: [GSoC 2023] Introducing Myself
Date: Thu, 02 Mar 2023 17:14:15 +0000 [thread overview]
Message-ID: <87r0u79ipi.fsf@linaro.org> (raw)
In-Reply-To: <20230302135302.GM7636@redhat.com>
"Richard W.M. Jones" <rjones@redhat.com> writes:
> On Thu, Mar 02, 2023 at 07:17:46PM +0530, Ayush Singh wrote:
>> Hello Everyone,
>>
>> I am Ayush Singh, a 3rd-year university student from the Indian Institute of
>> Technology (Indian School of Mines), Dhanbad, India. This email is just to
>>
>> I participated and successfully completed my GSoC 2022 Project under Tianocore
>> Organization in Rust, so I am pretty experienced in Rust Language. I am also
>> fairly proficient in reading and working with C, although not to the same
>> degree as Rust.
>>
>> I use Qemu often for testing and thus would like to contribute to Qemu as a
>> part of GSoC 2023. I have narrowed down the projects to:
>>
>> 1. Rust bindings for libnbd: https://wiki.qemu.org/Google_Summer_of_Code_2023#
>> Rust_bindings_for_libnbd
>> 2. RDP server: https://wiki.qemu.org/Google_Summer_of_Code_2023#RDP_server
>>
>> I would just like to confirm if both of the above projects are up for grabs in
>> the upcoming GSoC 2023, and if there are any specific requirements/tasks to
>> complete to apply for either of the projects.
>
> We do have another candidate. I'm not sure what happens in these
> situations .. Erik?
Project allocations happen through the GSoC process so everyone should
apply and then you interview the prospective candidates and choose the
best one.
> Rich.
>
>> Finally, what is the preferred way of discussions in Qemu community? I did see
>> an IRC channel as well as qemu-discuss mailing list.
For realtime questions (keeping in mind TZ's and working hours) IRC is
the best way. You can connect via matrix as described here:
https://www.qemu.org/support/
as not everyone has access to a persistent IRC bouncer. Otherwise deeper
technical questions are best handled on qemu-devel where the thread can
be followed by the whole community.
>>
>> Yours sincerely
>> Ayush Singh
>>
>> Github: https://github.com/Ayush1325
>> GSoC 2022 Project: https://summerofcode.withgoogle.com/archive/2022/projects/
>> PwQlcngc
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2023-03-02 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 13:47 [GSoC 2023] Introducing Myself Ayush Singh
2023-03-02 13:53 ` Richard W.M. Jones
2023-03-02 17:14 ` Alex Bennée [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=87r0u79ipi.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=ayushdevel1325@gmail.com \
--cc=eskultet@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).