From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Lars Kurth <lars.kurth@citrix.com>
Cc: Lasya Venneti <comethalley61@gmail.com>,
Stefano Stabellini <Stefano.Stabellini@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Newbie - OutreachY round 11 (Dec 7 to March 7)
Date: Thu, 17 Sep 2015 16:14:14 -0400 [thread overview]
Message-ID: <20150917201414.GD12745@l.oracle.com> (raw)
In-Reply-To: <D22067AE.20FB0%lars.kurth@citrix.com>
On Thu, Sep 17, 2015 at 12:03:27PM +0000, Lars Kurth wrote:
> Hi all,
>
> we do have two OutreachY slots and I just received information related
> about the timeline for OutreachY yesterday. See below
>
> September 28 organizations' landing pages need to be ready with project
> ideas
> September 29 application process opens
> November 2 application deadline
> November 17 accepted applicants announced
> December 7 - March 7 internship dates
>
>
> For now, we can use the information on
> http://wiki.xenproject.org/wiki/Outreachy/Round10 and then update the
> project lists (under "Community Reviewed Project List")
>
> @Lasya, is your interest in Hypervisor work? Or higher level work such as
> Mirage OS?
> For the former starting information can be found at
> http://wiki.xenproject.org/wiki/Category:Developers - but we should also
> possibly haver some projects in areas such as Xen - OpenStack integration,
> Xen - Libvirt integration, Raisin
> (https://blog.xenproject.org/2015/06/28/project-raisin-raise-xen/), and
> many other areas that are not reflected in the project list
>
> Depending on your interest, the existing project list or some areas you
> may be interested in, we can start updating "Community Reviewed Project
> List"
>
> @Wei, @Stefano, @Konrad and everyone else: do we have any smaller work
> items / bug fixes / etc. that need doing and would be suitable for Lasya?
> Remember, the purpose of these items, is to get familiar with set-up and
> the community processes. Maybe some stuff coverity has thrown up to start
> with and then maybe something more complex a little later. We then also
> need to find mentors and update projects.
I've a bunch of work on http://wiki.xen.org/wiki/XSplice - from which
the non-hypervisor parts could be spun off. I can certainly stick
some of them in the proper sections.
>
> Best Regards
> Lars
>
> On 17/09/2015 12:49, "Wei Liu" <wei.liu2@citrix.com> wrote:
>
> >Cc Lars
> >
> >On Thu, Sep 17, 2015 at 02:33:43PM +0530, Lasya Venneti wrote:
> >> Hi everyone,
> >>
> >> I'm Lasya a student studying in IIIT-H, Hyderabad, India.
> >>
> >> I wish to participate in round 11 of Outreachy this time. I would be
> >> grateful if someone would direct me as to how I am supposed to start
> >> contributing to Xen Project for this Outreachy round.
> >>
> >> Sincerely,
> >> Lasya V
> >
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xen.org
> >> http://lists.xen.org/xen-devel
> >
>
next prev parent reply other threads:[~2015-09-17 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 12:03 Newbie - OutreachY round 11 (Dec 7 to March 7) Lars Kurth
2015-09-17 20:14 ` Konrad Rzeszutek Wilk [this message]
2015-09-18 8:48 ` Lasya Venneti
2015-09-18 9:02 ` Lars Kurth
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=20150917201414.GD12745@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=Stefano.Stabellini@citrix.com \
--cc=comethalley61@gmail.com \
--cc=lars.kurth@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).