qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Kurape <jkurape@gmail.com>
To: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: Contributing to Qemu
Date: Sun, 8 Sep 2024 20:07:30 +0100	[thread overview]
Message-ID: <CALcAbx7soPaL30DbYVcLkGLxfzxzbXGVGO0dj2609C_tnKK8zg@mail.gmail.com> (raw)
In-Reply-To: <jhkm8.uh7rl3q19uua@linaro.org>

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

Thank you, Manos.

I'm not discouraged by the difficulty. I guess I just didn't know where to
start from. Thanks for the direction.


On Sun, 08 Sept 2024, 09:51 Manos Pitsidianakis, <
manos.pitsidianakis@linaro.org> wrote:

> On Sun, 08 Sep 2024 10:28, Joseph Kurape <jkurape@gmail.com> wrote:
> >Hello,
> >
> >I'm new to open-source, but I've learned C and Python.
> >
> >I've read the 'Getting Started' guide, but aside from signing up for the
> >mailing list and getting the source code, it doesn't provide much
> direction
> >for beginners.
> >
> >I'm looking for somewhere I can contribute. Could any maintainer suggest
> >any issue they need fixing or offer general directions on the best way to
> >get started?
>
> Hello Joseph!
>
> First, the bad news: QEMU is a sophisticated and complicated project,
> and I would not recommend it as the first foray of serious programming
> to most people. But the good news is, it is still possible to contribute
> without being an expert simply because QEMU is composed of many
> different things.
>
> The usual advice is to take a look at the issues labelled as
> "Bite-Sized" on our Issue tracker:
>
>
> https://gitlab.com/qemu-project/qemu/-/issues/?sort=created_date&state=opened&label_name%5B%5D=Bite+Sized&first_page_size=50
>
> Take your time looking at each of them and you can choose something that
> looks approachable to you.
>
> Note: I see that in many issues people say they want to contribute and
> ask for the issue to be assigned to them- no need to do that! Focus on
> writing down your solution and sending it to the list while following
> the "submitting a patch" docs:
> https://www.qemu.org/docs/master/devel/submitting-a-patch.html
>
> If you have any kind of technical question you should ask on IRC, if you
> happen on any developer being online at the same time as you, or on the
> list. Do not ask people in private because not only will less people see
> your question, but most QEMU maintainers only pay attention to the
> mailing list for QEMU related discussion.
>
> If you have any more questions feel free to ask!
>
>
>

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

      reply	other threads:[~2024-09-08 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-08  7:28 Contributing to Qemu Joseph Kurape
2024-09-08  8:44 ` Manos Pitsidianakis
2024-09-08 19:07   ` Joseph Kurape [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=CALcAbx7soPaL30DbYVcLkGLxfzxzbXGVGO0dj2609C_tnKK8zg@mail.gmail.com \
    --to=jkurape@gmail.com \
    --cc=manos.pitsidianakis@linaro.org \
    --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).