From: Lars Kurth <lars.kurth-LM2mM/qkH7s@public.gmane.org>
To: xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org
Subject: Preparing for Google Summer of Code 2011
Date: Thu, 03 Feb 2011 11:14:00 +0000 [thread overview]
Message-ID: <4D4A8DF8.2030608@xen.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1419 bytes --]
Hi everybody,
Xen.org intends to apply for Google Summer of Code 2011 sponsored by
Google. Last year we got 3 projects approved and with luck and a little
effort we will be able to grow to more. GSoC is a great opportunity for
Xen.org to promote our technology, to get new features for our code and
to grow the community of people working on the code.
For the application to be successful, we need a list of proposed project
ideas. For last year's submission, we had a very long list of project
ideas. I have copied the ideas to
http://wiki.xensource.com/xenwiki/GSoC_2011_ideas and removed the ones I
know were implemented.
What I am asking YOU to do is the following:
* Have a look at the list
* If you are a named contact on the ideas list, let me know whether
your idea is still valid (by e-mail, by replying to this thread or
by marking the idea with a YES or NO in the 2011 column)
* If the named contact should change, please let me know who the new
contact should be
* If you have a new idea, please drop me a line or add it with a
description to the wiki page, following the existing examples
In about two weeks, I will review the list and start preparing the GSoC
submission and work with the various XEN projects and maintainers.
Best Regards
Lars
Xen.org Community Manager
lars.kurth-LM2mM/qkH7s@public.gmane.org | http://blog.xen.org | @xen_com_mgr
[-- Attachment #1.2: Type: text/html, Size: 2332 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2011-02-03 11:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D4A8DF8.2030608@xen.org \
--to=lars.kurth-lm2mm/qkh7s@public.gmane.org \
--cc=xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
--cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.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.