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
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
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
> 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.
Also feel free to add it to the docs day TODO list. This is a community
document that is intended for the community and you shouldn''t wait for
me to add stuff.
Lars
On 30/07/2012 16:57, Attilio Rao wrote:> 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
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
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 listMore 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 30/07/2012 18:27, Attilio Rao wrote:> > > I wanted to organize the page like that: > I''m already working on this, what is the quickest way to submit a > draft to you for review by wiki modifies?I was just thinking us using a template such that changing the formatting is easier in future. I just copied one, which did not work. Five me 5 minutes and I''ll do a simple one
On 30/07/2012 18:27, Attilio Rao wrote:>> 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?Actually, just start with the content. I will make a template later and reformat. That is probably best. Lars