All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karsten Wade <kwade@redhat.com>
To: Lars Kurth <lars.kurth@citrix.com>,
	"dunlapg@umich.edu" <dunlapg@umich.edu>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: GSoC ideas for Xen?
Date: Thu, 19 Feb 2015 14:31:01 -0800	[thread overview]
Message-ID: <54E66425.60106@redhat.com> (raw)
In-Reply-To: <B5EC053C78C5D746BD8AC3386F2303C9254E7217@AMSPEX01CL01.citrite.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/19/2015 01:58 PM, Lars Kurth wrote:
> Adding the xen-devel list. Note that we are a long time
> participant of GSoC and OPW. Our project list is on 
> wiki.xenproject.org/wiki/GSoC_2015

Do you have anything that you would want to do in joint or through
CentOS GSoC efforts?

> We are both at CollabSummit, which is why we have not responded to 
> KB's mail

Gotcha, thanks. Yeah, I had to choose SCALE this year since they
conflicted.

- - Karsten

> Lars ________________________________________ From: Karsten Wade 
> [kwade@redhat.com] Sent: 19 February 2015 21:46 To: Lars Kurth; 
> dunlapg@umich.edu Subject: GSoC ideas for Xen?
> 
> George, Lars:
> 
> We're collecting ideas (over the next 24 hours) for work that
> Google Summer of Code students can do via the CentOS Project. In
> the past I've had good success with doing work with GSoC students
> via the Fedora Project where the work happens primarily in the
> upstream project, as long as it lands back with the distro. We
> think the same can work for CentOS SIGs.
> 
> For the Xen Project we're looking for items that might be directly 
> or indirectl related to work needed in your SIG. It could be 
> integration, packaging, or any other code-related task.
> 
> Each idea needs to be associated with a mentor, but we can be 
> flexible about the final mentor assignment once we (hopefully) get 
> accepted to this year's GSoC.
> 
> You can see the template of what we need to fill out for each
> idea.
> 
> http://wiki.centos.org/GSoC/2015/Ideas
> 
> Remember that these are tasks for e.g. computer science students,
> and a part of the work for the mentor is simply getting the student
> able to effectively contribute and collaborate in an open
> community. This means you can take an idea you might do over two
> months and split it in to 4 parts for 4 different students, etc.
> 
> Thanks,
> 
> - Karsten
> 

- -- 
Karsten 'quaid' Wade        .^\          CentOS Doer of Stuff
http://TheOpenSourceWay.org    \  http://community.redhat.com
@quaid (identi.ca/twitter/IRC)  \v'             gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlTmZCUACgkQ2ZIOBq0ODEFGlgCgtklWsumLDnw9RpRX4JUGWnZW
dqEAn3aVurYr3ZABSaN/DsnlljuRLOgR
=g66Z
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-02-19 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54E659AC.10303@redhat.com>
2015-02-19 21:58 ` GSoC ideas for Xen? Lars Kurth
2015-02-19 22:31   ` Karsten Wade [this message]
2015-02-19 23:54     ` Lars Kurth
2015-02-23  6:04       ` Karsten Wade
2015-02-24 14:34         ` Lars Kurth
2015-02-24 18:54           ` Karsten Wade

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=54E66425.60106@redhat.com \
    --to=kwade@redhat.com \
    --cc=dunlapg@umich.edu \
    --cc=lars.kurth@citrix.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.