From: Wei Liu <wei.liu2@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>
Cc: nimisha agarwal <nimishaag2212@gmail.com>,
xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [Outreachy]Code Standards Checking using clang-format
Date: Tue, 27 Sep 2016 16:15:02 +0100 [thread overview]
Message-ID: <20160927151502.GJ16004@citrix.com> (raw)
In-Reply-To: <0f77d7fe-4225-3d4c-946d-efced21ce6d1@cardoe.com>
On Tue, Sep 27, 2016 at 09:22:37AM -0500, Doug Goldstein wrote:
> On 9/26/16 3:53 PM, nimisha agarwal wrote:
> > Hello,
> > I wish to take part in the Outreach Program this time. The
> > second project that interest me is *Code Standards Checking using
> > clang-format. *I am currently looking through clang-format so I could
> > get to know how to use it.
> > To get started, if you could suggest couple of small bitesize work-items
> > so I could start contributing and get familiar with the codebase.
> >
> >
> > Regards,
> > Nimisha
>
> Hi Nimisha,
>
> Sounds great. At this time I'm personally not very familiar with some
> bite sized items to get started with contributing but I've CC'd Wei and
> I'm hoping he's got some ideas.
I don't have anything in mind at the moment.
However, I think it would be more useful to design a small task to test
applicants' proficiency in the skills we care about than ask them to
make simple modifications to the code base.
See <d9b5890f-8620-49f3-1d6a-0e414d551c4a@citrix.com> for an example.
Wei.
>
> --
> Doug Goldstein
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-27 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 20:53 [Outreachy]Code Standards Checking using clang-format nimisha agarwal
2016-09-27 14:22 ` Doug Goldstein
2016-09-27 15:15 ` Wei Liu [this message]
2016-09-28 18:24 ` nimisha agarwal
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=20160927151502.GJ16004@citrix.com \
--to=wei.liu2@citrix.com \
--cc=cardoe@cardoe.com \
--cc=nimishaag2212@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.