From: Thomas Huth <thuth@redhat.com>
To: Rohit Shinde <rohit.shinde12194@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Contributor wanting to get started with simple contributions
Date: Thu, 27 Aug 2020 06:37:52 +0200 [thread overview]
Message-ID: <15d81509-81d4-d583-16c6-3407efd26f12@redhat.com> (raw)
In-Reply-To: <CA+Ai=tCk-XX7yogRu=zoKxDv7okRHXibbnT9OoMs8XpHs9yDkA@mail.gmail.com>
On 26/08/2020 17.00, Rohit Shinde wrote:
> Hey Thomas,
>
> I didn't really have any specific questions. I wanted to know if there
> was any part of qemu that I could contribute to. Qemu is overwhelmingly
> vast and without some pointers, I felt very lost.
Ok, that's true - QEMU is really a huge project. I'd really recommend to
pick some topics from https://wiki.qemu.org/Contribute/BiteSizedTasks
first to get a feeling for contributing patches to QEMU. Since you're
interested in emulation, maybe the topics from the "Device models"
section would also be a good fit?
> > I plan to stay and become a long term contributor. Is there any CS
>
> What does "CS" stand for?
>
> Computer Science :)
Oh, well, thanks, ok, that was too easy. I guess there are just too many
abbreviations around ;-)
>
> > theory that I would need to know other than what I mentioned
> above?
I'd recommend to browse the various KVM forum presentations on
http://www.linux-kvm.org/page/Category:Conferences to see if there is
something that catches your eye. You can find the recordings of most
presentations on
https://www.youtube.com/channel/UCRCSQmAOh7yzgheq-emy1xA , too.
> > Is it possible to "learn on the go"?
>
> You certainly have to "learn on the go", since it is likely quite
> impossible to grasp a huge project like QEMU at once.
>
> I am interested in contributing to something like device emulation.
> There might be lots of devices which Qemu might want to emulate but
> which haven't yet been emulated.
Sure, but I think you first need a target you're interested in first.
E.g. do you want to focus on x86, ARM, PPC, m68k, ... ? Depending on
that, you can start looking around in the hw/ directory for "missing" or
"TODO" items.
Thomas
next prev parent reply other threads:[~2020-08-27 4:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 11:18 Contributor wanting to get started with simple contributions Rohit Shinde
2020-08-25 2:26 ` Rohit Shinde
2020-08-25 5:50 ` Thomas Huth
2020-08-26 15:00 ` Rohit Shinde
2020-08-26 15:51 ` John Snow
2020-08-26 17:55 ` Rohit Shinde
2020-08-29 5:14 ` Rohit Shinde
2020-09-02 16:38 ` Rohit Shinde
2020-09-30 4:38 ` John Snow
2020-10-13 18:46 ` Rohit Shinde
2020-10-14 17:59 ` John Snow
2020-08-27 4:37 ` Thomas Huth [this message]
2020-08-28 0:49 ` Rohit Shinde
2020-08-28 4:14 ` Thomas Huth
2020-08-26 15:40 ` John Snow
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=15d81509-81d4-d583-16c6-3407efd26f12@redhat.com \
--to=thuth@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rohit.shinde12194@gmail.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).