From: George Dunlap <george.dunlap@eu.citrix.com>
To: Abhinav Gupta <abhinavgupta440@gmail.com>,
xen-devel@lists.xenproject.org
Subject: Re: Interested in taking up a project
Date: Mon, 22 Jun 2015 10:45:16 +0100 [thread overview]
Message-ID: <5587D92C.4030903@eu.citrix.com> (raw)
In-Reply-To: <CALc02L70Aq6bWYp2bTJMyL-RorwMSH0UghPbhQG+-W6W2qUK1Q@mail.gmail.com>
On 06/21/2015 07:37 AM, Abhinav Gupta wrote:
> Hii,
> I'm still waiting for the confirmation. Have started looking into the
> code though.
Hey Abhinav,
Thanks for your interest! As others have said, it's a free world, so of
course you can work on and attempt to contribute whatever you want. :-)
There's nobody else working on this yet, and it's probably still a good
idea, so in that sense, the project is something that you should feel
free to start working on.
I don't have time at the moment to commit to the level of mentorship I
would if you were a GSoC intern; but as a community, we're generally
pretty good about helping people who try to get involved -- as you've
already found out. :-)
One heads-up: A thing we've started doing in our community, before
submitting a large new feature, is to post a design document describing
the purpose of the new feature, and a technical overview of the changes
that you want to make and why.
This is *not required*; you are free to just submit patches with your
changes, and many people do. However, it's not uncommon for maintainers
to request significant changes to the architecture or approach on major
features, which require a major re-write. This can be frustrating both
for you and for us. Done properly, a design document can make things
easier for all of us.
Looking forward to seeing your work!
-George
next prev parent reply other threads:[~2015-06-22 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 7:02 Interested in taking up a project Abhinav Gupta
2015-06-19 9:11 ` Wei Liu
[not found] ` <CALc02L7+MtwBOg4iFn2uri0MGKu_XSrdxA-LyzQ-59LuEsJ-RQ@mail.gmail.com>
2015-06-19 10:56 ` Wei Liu
2015-06-21 6:37 ` Abhinav Gupta
2015-06-22 8:37 ` Dario Faggioli
2015-06-22 9:45 ` George Dunlap [this message]
2015-06-24 9:56 ` Abhinav Gupta
2015-07-01 13:11 ` Dario Faggioli
2015-07-10 20:33 ` Abhinav Gupta
2015-07-13 9:45 ` Dario Faggioli
2015-07-25 12:34 ` Abhinav Gupta
2015-07-27 14:20 ` Dario Faggioli
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=5587D92C.4030903@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=abhinavgupta440@gmail.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.