qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Rohit Shinde <rohit.shinde12194@gmail.com>,
	Thomas Huth <thuth@redhat.com>
Cc: crosa@redhat.com, qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: Contributor wanting to get started with simple contributions
Date: Wed, 26 Aug 2020 11:51:07 -0400	[thread overview]
Message-ID: <a50f47d2-f5c6-49c0-779f-dfcaf05df5f9@redhat.com> (raw)
In-Reply-To: <CA+Ai=tCk-XX7yogRu=zoKxDv7okRHXibbnT9OoMs8XpHs9yDkA@mail.gmail.com>

On 8/26/20 11:00 AM, 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.

Yeah, it can be hard to get started.

What are your interests in programming/development, any specific types 
of coding you like doing more than others? What draws you to the QEMU in 
particular? Is there something you'd like to see QEMU do that it doesn't 
today, or something you feel like you are particularly suited to doing?

If I can figure out what brought you here, maybe I can direct you to 
some projects that might benefit from your attention. [Apart from the 
Python stuff, which we are discussing elsewhere in another thread.]

Some topic areas:

- Emulation (TCG)
- Virtualization (KVM)
- Esoteric/Legacy architecture/device emulation
- Optimization (Network, Storage, CPU)
- Regression/Acceptance Testing
- Fuzzing
- Configuration
- Deployment
- Continuous Integration
- Accessibility, Ease-of-use
- Build systems & tooling
- Development process
- SDK/API development


If you have any specific knowledge in areas that aren't Linux on x86, 
there are likely areas of QEMU that could benefit from your knowledge. 
We are always looking for people to help maintain and develop code 
intended for other architectures on other platforms.

--js



  reply	other threads:[~2020-08-26 15:52 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 [this message]
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
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=a50f47d2-f5c6-49c0-779f-dfcaf05df5f9@redhat.com \
    --to=jsnow@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rohit.shinde12194@gmail.com \
    --cc=thuth@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).