From: John Snow <jsnow@redhat.com>
To: Aishwarya Kadlag <aishwaryakadlag@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Introduction
Date: Tue, 6 Mar 2018 14:37:47 -0500 [thread overview]
Message-ID: <d6966f63-ff07-fc86-bdcc-877b4a99dca3@redhat.com> (raw)
In-Reply-To: <CAFPFVbdG=Ccr+M+Zv32XTavYdOwifDCxAXObeeZaZfB+x6V9Uw@mail.gmail.com>
On 03/04/2018 12:17 AM, Aishwarya Kadlag wrote:
> Hi, I am aish2k joining this mailing list today
>
Hi, aish2k:
In general, you do not need to announce or introduce yourself when
joining technical mailing lists. You may subscribe and unsubscribe at
your leisure.
Most lists have certain rules and etiquettes that may be learned by
watching how the list conducts itself over time -- sometimes they're
written more explicitly, but not always.
A thing to keep in mind is that every message sent to the mailing list
will be received by everyone on it, so it's best to make sure that
messages are meaningful or interesting. If you have questions, try to
research your questions as best as you can and provide that information
so that people can assist you more quickly.
If you're joining our list to look for small projects or contributions
you could make as a stepping stone to something greater, check out these
pages on our wiki:
https://wiki.qemu.org/Contribute
https://wiki.qemu.org/Google_Summer_of_Code_2018
https://wiki.qemu.org/Outreachy_2018_MayAugust
Many pages eventually link to this one:
https://wiki.qemu.org/BiteSizedTasks
Which we use to put small project ideas that are useful for new
contributors to familiarize themselves with the codebase.
Hopefully this information is useful to you.
--js
prev parent reply other threads:[~2018-03-06 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 5:17 [Qemu-devel] Introduction Aishwarya Kadlag
2018-03-06 19:37 ` 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=d6966f63-ff07-fc86-bdcc-877b4a99dca3@redhat.com \
--to=jsnow@redhat.com \
--cc=aishwaryakadlag@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).