From: Attilio Rao <attilio.rao@citrix.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: Xen Development Projects page
Date: Mon, 30 Jul 2012 16:57:53 +0100 [thread overview]
Message-ID: <5016AF01.7010504@citrix.com> (raw)
Hi,
I think it is time we start preparing and managing correctly a Xen
Development wiki page. We already have one but it is a bit un-organized,
with stale and poor content.
I wanted to organize the page like that:
- Have upfront a list of tasks, divided by subsystem (es. toolstack,
hypervisor, domain support, etc.)
- Have the corresponding entries organized like that:
o Technical contact (this may be optional if we think the idea is
worthwhile but there is not really someone which can tackle this right
now). There may be more than one.
o Description of the issue: the description must be technical and
give an hint to the contributor, however might not reveal all the
technical trickery about it. This is to force the novel contributor to
contact the "technical contact" and work on the issue to get a grasp.
o Difficulty level. I'm not sure if you like this, but very much I
think this would be an hint for people that are very new to xen
development and wants to start from simple projects.
In the end, we can squeeze out Summer of Projects entries from this list
if we keep it updated well enough and really useful.
What I'm asking you is:
- Do you like the idea to organize the development projects page like that?
- Do you *all* want to contribute with a couple of ideas outlining the
informations reported above? I don't it is a huge effort if everyone
contributes at least 1 entry or 2.
Thanks,
Attilio
next reply other threads:[~2012-07-30 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 15:57 Attilio Rao [this message]
2012-07-30 17:00 ` Xen Development Projects page Lars Kurth
2012-07-30 17:27 ` Attilio Rao
2012-07-30 17:40 ` Lars Kurth
2012-07-30 17:42 ` 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=5016AF01.7010504@citrix.com \
--to=attilio.rao@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).