From: Attilio Rao <attilio.rao@citrix.com>
To: xen-devel@lists.xen.org, Lars Kurth <lars.kurth@xen.org>
Subject: Re: Xen Development Projects page
Date: Mon, 30 Jul 2012 18:27:50 +0100 [thread overview]
Message-ID: <5016C416.3010000@citrix.com> (raw)
In-Reply-To: <5016BDC5.4010103@xen.org>
[-- Attachment #1.1: Type: text/plain, Size: 1214 bytes --]
On 30/07/12 18:00, Lars Kurth wrote:
> Attilio,
>
> this is a very good idea. I am not 100% convinced that the Dev Home
> page should contain TODO items only. It should point to
> a) Conventions (asking questions, building, testing, ...)
> b) Design docs (assuming there are any)
> c) TODO list
More specifically I was referred to make c) and in particular by
modifying http://wiki.xen.org/wiki/Xen_Development_Projects for this
purpose.
>
> So maybe you need
>
> * A new page better organized home page (with a good title) and
> when done delete the old one
> * A Xen separate project TODO list
>
Yes, I'm going with the TODO first, then I can think about organizing
the DevHome and link to it.
> *
>
>
> > I wanted to organize the page like that:
> > - Have upfront a list of tasks, divided by subsystem (es. toolstack,
> hypervisor, domain support, etc.)
> I think entries in the list also need to contain the date when created
> such that we can identify and throw out stale ideas
> If you want me to, I can create a template to make encoding this easier.
I'm already working on this, what is the quickest way to submit a draft
to you for review by wiki modifies?
Thanks,
Attilio
[-- Attachment #1.2: Type: text/html, Size: 2076 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-07-30 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 15:57 Xen Development Projects page Attilio Rao
2012-07-30 17:00 ` Lars Kurth
2012-07-30 17:27 ` Attilio Rao [this message]
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=5016C416.3010000@citrix.com \
--to=attilio.rao@citrix.com \
--cc=lars.kurth@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.