All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karsten Wade <kwade@redhat.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>
Cc: Lars Kurth <lars.kurth@citrix.com>,
	"dunlapg@umich.edu" <dunlapg@umich.edu>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: GSoC ideas for Xen?
Date: Tue, 24 Feb 2015 10:54:10 -0800	[thread overview]
Message-ID: <54ECC8D2.50206@redhat.com> (raw)
In-Reply-To: <BEBE0650-C28A-4050-B434-B16D91A31479@gmail.com>

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

On 02/24/2015 06:34 AM, Lars Kurth wrote:
> You seem to have a good list together by now. Should be good enough
> for the application.

Thanks, yeah, I really like the ideas, and a nice list of mentors.
We've got some good stuff in there that should help the wider
ecosystem, which I always prefer over things that just help the
project itself.

- - Karsten

> Regards Lars
> 
> 
>> On 23 Feb 2015, at 06:04, Karsten Wade <kwade@redhat.com> wrote:
>> 
> On 02/19/2015 03:54 PM, Lars Kurth wrote:
>>>>> Do you have anything that you would want to do in joint or 
>>>>> through CentOS GSoC efforts?
>>>> We probably do, but don't have time to put this together in
>>>> there next 24 hours. A bit of thought and word smithing is
>>>> needed. There is nothing on our existing list that can be
>>>> moved over.
> 
> No problem, I realized near the end that I hadn't directly reached
> out to SIG leadership to see what they were thinking about, hence
> my last-hour appeal. :)
> 
>>>> Is there any infrastructure stuff you could add: the issue I
>>>> see is that you have an empty project list, which means as a
>>>> mentoring org you have 0 chance of getting into GSoC. From my
>>>> experience it is necessary to start the process for GSoC in
>>>> December.
> 
> Agreed, and just like last year I forgot my experience here --
> i.e., once you see the notice that GSoC 20** is "on", start working
> on it. So the opening week snuck up on me. :)
> 
> Cheers,
> 
> - Karsten
> 
>>>> Regards Lars
>>>> 
>>>> On 19/02/2015 14:31, "Karsten Wade" <kwade@redhat.com>
>>>> wrote:
>>>> 
>>>> 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
>>>>>>> 
>>>> 
>>>>> 
>>>> 
> 
>> 
>> _______________________________________________ Xen-devel mailing
>> list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
> 

- -- 
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

iEYEARECAAYFAlTsyNIACgkQ2ZIOBq0ODEF4OgCgkcFZk/rrZN+L98JY29xg0gbF
BVEAn0TnAx588qTiy6bg1Nrco1TP/bSa
=p1xU
-----END PGP SIGNATURE-----

      reply	other threads:[~2015-02-24 18:54 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
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 [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=54ECC8D2.50206@redhat.com \
    --to=kwade@redhat.com \
    --cc=dunlapg@umich.edu \
    --cc=lars.kurth.xen@gmail.com \
    --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.