From: Thomas Huth <thuth@redhat.com>
To: Akshaya Sankar <akshayasankarr@gmail.com>, qemu-devel@nongnu.org
Subject: Re: Regarding the TODO list for contribution
Date: Mon, 14 Jul 2025 14:59:43 +0200 [thread overview]
Message-ID: <b356a6b0-28dc-4ca3-8531-b47b7f60d7d4@redhat.com> (raw)
In-Reply-To: <CA+A3OQ3jcS=r0n_gEMAxrtTDHkCjibL9SPWY37WDBq2tqC-1SQ@mail.gmail.com>
On 14/07/2025 13.30, Akshaya Sankar wrote:
> Hi all,
>
> we would like to contribute to this open source community as a fresher /
> less experience, and would like to know about the small contributions to be
> done as initially. We have hands on experience on embedded, c, python and c++.
>
> Kindly guide us if there is any TODO list.
Hi,
thanks for your interest in QEMU! There are some "bite sized" tasks in our
issue tracker, some of those likely can be done by new contributors, too:
https://gitlab.com/qemu-project/qemu/-/issues/?state=opened&label_name%5B%5D=Bite%20Sized
HTH,
Thomas
prev parent reply other threads:[~2025-07-14 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 11:30 Regarding the TODO list for contribution Akshaya Sankar
2025-07-14 12:59 ` Thomas Huth [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=b356a6b0-28dc-4ca3-8531-b47b7f60d7d4@redhat.com \
--to=thuth@redhat.com \
--cc=akshayasankarr@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).