From: John Snow <jsnow@redhat.com>
To: Rohit Shinde <rohit.shinde12194@gmail.com>, qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, crosa@redhat.com
Subject: Re: Contributor wanting to get started with simple contributions
Date: Wed, 26 Aug 2020 11:40:41 -0400 [thread overview]
Message-ID: <2a80090b-295b-4f57-df3e-5923506cce80@redhat.com> (raw)
In-Reply-To: <CA+Ai=tBJqLB7yDbd-kqzDhr+d+65K9r3DQsZrB2kGi9wF8BaiA@mail.gmail.com>
On 8/24/20 10:26 PM, Rohit Shinde wrote:
> Hey John,
>
Hi Rohit!
> I sent this email a couple of weeks ago to the qemu mailing list since I
> didn't really know who to approach.
>
Sorry, I didn't see a mail. The volume is quite high and I missed it.
For Python issues, the usual suspects are:
Me (Lately),
Markus Armbruster (Primarily around the QAPI parser),
Cleber Rosa (Primarily around VM tests),
Eduardo Habkost (In general).
> I am interested in contributing to the python-qemu package. I have quite
> a bit of experience in Python, but no experience in packaging libraries.
I must admit I am also quite new to packaging python, but I'm learning
as I go. For now, we do not have any published package so we do not need
to maintain any kind of stable API, but there are many places in the
QEMU source tree that rely on the python packages and must keep working.
> Whatever you mentioned in the reply to my comment on the bug, was pretty
> interesting. I would like to get started with at least ensuring that all
> python code is flake8/pylint compliant.
>
OK! I have some patches in progress, let me clean them up for post-5.1
and I will CC you when I send them. I have been on PTO for a little
while and was focused on another project, so they have to be resurrected
a little bit.
I will likely continue to be distracted by other projects, so if you are
able to help with some of the Python refactoring/redevelopment that will
be a good help.
> Do let me know what you think of this.
>
Sure, stay tuned.
> Thanks,
> Rohit.
>
> On Thu, Aug 13, 2020 at 7:18 AM Rohit Shinde
> <rohit.shinde12194@gmail.com <mailto:rohit.shinde12194@gmail.com>> wrote:
>
> Hello everyone,
>
> I am a hobby programmer (working as an SDE in the industry) and I
> have been observing qemu for quite a while. I have always wanted to
> contribute but I couldn't manage my time. I am good at Java and
> Python but quite a bit rusty with C++ and C (although working with
> it will not be a problem, I might have to google more than usual).
> On the theory side, I have a good grasp of data structures and
> algorithms and a decent understanding of OS and Compilers.
>
> I have built qemu from source and I have my machine setup for
> git-publish via email.
>
> I would like to start contributing with one of the bite sized tasks
> mentioned in the wiki page. The one that interests me and which I
> think is the easiest are the sections on "Compiler Driven Cleanup"
> and "Dead Code Removal". I think this is a good way to get
> introduced to the codebase.
>
> I plan to stay and become a long term contributor. Is there any CS
> theory that I would need to know other than what I mentioned above?
> Is it possible to "learn on the go"?
>
> I realize this is quite a long email and I would like to thank
> everyone in advance for reading this!
>
> Regards,
> Rohit.
>
prev parent reply other threads:[~2020-08-26 15:41 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
2020-08-28 0:49 ` Rohit Shinde
2020-08-28 4:14 ` Thomas Huth
2020-08-26 15:40 ` John Snow [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=2a80090b-295b-4f57-df3e-5923506cce80@redhat.com \
--to=jsnow@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@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).