Michael Meeks wrote: > My views on this sort of Intel internal re-writing are well known. > There is a good way to do this: work with the existing guys on the > various bootchart projects out there, and try to draw them together. > That is the approach I took with bootchart2. It is also far, far less > wasteful of the scarce resources that we (collectively) have today to > work on tooling. +1
> There is a good way to do software development in community; and IMNSHO > it doesn't look like this. We don't need yet-another bootchart > project[2] there are currently a handful (now +1). +1 Auke - I would suggest that you lead by example and make a conscious effort to say "NIH is not acceptable. We now know of external tools that are functionally equivalent to internal tools. We will drop the internal tool and work with the wider community." David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
