All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Lars Kurth <lars.kurth@xen.org>, konrad@kernel.org
Cc: xen-arm@lists.xen.org,
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Getting into shape for GSOC 2013
Date: Wed, 19 Dec 2012 16:44:14 -0500	[thread overview]
Message-ID: <20121219214414.GA25858@phenom.dumpdata.com> (raw)
In-Reply-To: <50A4F83D.4000205@xen.org>

On Thu, Nov 15, 2012 at 02:12:13PM +0000, Lars Kurth wrote:
> Hi everybody,
> 
> this is a gentle reminder to update
> http://wiki.xen.org/wiki/Xen_Development_Projects and to start

Let me put some extra items on the list.

> thinking about projects that are suitable for GSoC. The template to
> add items to the project page is below...
> 
> {{project
> |Project=Project description
> |Date=date of insert
> |Contact=Owner name
> |Desc=Description of
> |GSoC=Yes or No, or any other GSoC related comment
> }}
> 
> In 2012, we didn't make it into GSoC because we didn't have a good
> enough project list. We need to have a list of about 10 good project
> proposals for GSoC and present these nicely. It would be a real
> shame, if we didn't make it in 2013, in particular with some of the
> exciting work which is going on at the moment.
> 
> In 2011, when we made it our project list was at
> http://wiki.xen.org/wiki/Archived/GSoc_2011_Ideas ... Google has
> raised the bar, so we need to have
> a) Really good descriptions for our GSoC projects
> b) Pre-assign mentors to each project
> c) Ideally I would like to add biography and interest section for
> all our mentors. I can create a wiki template for mentors if it
> helps

Please do.
> 
> All this needs to be in place when we apply for GSoC as a mentoring
> organisation. The application deadline is likely in early February
> 2013, so starting on this now should leave us in good shape! If we

Aye. Feb.
> get a good list of projects together this year, we can tidy it up,
> iterate and improve in January!
> 
> Best Regards
> Lars
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

       reply	other threads:[~2012-12-19 21:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50A4F83D.4000205@xen.org>
2012-12-19 21:44 ` Konrad Rzeszutek Wilk [this message]
2012-12-19 23:31   ` Getting into shape for GSOC 2013 Dario Faggioli
2013-01-07 16:27     ` Konrad Rzeszutek Wilk
     [not found]     ` <20130107162734.GA6402@phenom.dumpdata.com>
2013-01-07 16:39       ` Wei Liu
2013-01-08 19:54         ` Konrad Rzeszutek Wilk
2013-01-09 15:44         ` [Xen-API] " Anil Madhavapeddy
     [not found]         ` <1F802A25-1C16-4BB8-9B7E-3FC80FD07B04@recoil.org>
2013-01-09 16:12           ` Wei Liu
     [not found]           ` <1357747958.9068.10.camel@iceland>
2013-01-09 16:19             ` Anil Madhavapeddy
2012-11-15 14:12 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=20121219214414.GA25858@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=konrad@kernel.org \
    --cc=lars.kurth@xen.org \
    --cc=xen-api@lists.xen.org \
    --cc=xen-arm@lists.xen.org \
    --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 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.