On 22/07/2019, 20:21, "Andrew Cooper" <[email protected]> wrote:
a.k.a. (at least in this form) Andrew's "work which might be offloadable to
someone else" list.
Signed-off-by: Andrew Cooper <[email protected]>
---
CC: George Dunlap <[email protected]>
CC: Ian Jackson <[email protected]>
CC: Jan Beulich <[email protected]>
CC: Stefano Stabellini <[email protected]>
CC: Tim Deegan <[email protected]>
CC: Wei Liu <[email protected]>
CC: Julien Grall <[email protected]>
CC: Lars Kurth <[email protected]>
CC: Paul Durrant <[email protected]>
CC: Roger Pau Monné <[email protected]>
RFC for obvious reasons.
A rendered version of this can be found at:
https://andrewcoop-xen.readthedocs.io/en/docs-wishlist/misc/wishlist.html
During XenSummit in Chicago, it was expressed several times that having some
todo lists would be a benefit, to help coordinate work in related areas.
Here is an attempt to start one. For now, it covers one single
item (xenstored's use of non-stable APIs) to get some feedback about the
general approach. I have plenty to get stuck into in Xen itself if this way
of expressing them isn't deemed unacceptable.
As for the wishlist itself, I think it is important that it be restricted to
concrete actions (i.e. already partially groomed, if you speak agile), which
are identified problems, and suggested fixes.
In particular, I don't think it is appropriate to devolve into a bullet
point
list of new features, or tasks like "document $whotsit". It should be
restricted to things which are real problems, on existing systems, which
have
some forward plan of action. That way, any developer should be able to
cross-reference at least at a high level, and see if there are areas of
overlapping work, or whether a slightly tweaked approach might be suitable
for
multiple areas.
Anyway - thoughts from the peanut gallery?
Hi Andy, sorry I had missed this. I think this is a good idea and worth
experimenting with.
Regarding Rich's comment, I thought we already agreed that we can use a CC, but
we have not decided how to do this in practical terms as we may be hoovering up
content that in the past may have been published as GPL
Lars
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
