On 03/30/10 12:56, David Greaves wrote:
Auke Kok wrote:
On 03/30/10 03:43, David Greaves wrote:
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."
Nonsense :)
heh :)
Could you clarify which bit is nonsense? Are you saying that NIH is acceptable?
Or is re-implementing internally a good idea when you know of external
equivalents?
Innovation comes from looking at an old good idea, and making a newer
and shinier implementation of it - not from shooting down good ideas
just because someone has already invented it...
True.
Those innovators get the best out of the community.
However I suggest that the very *best* innovators don't just take the ideas of
others and reimplement in the easiest way possible to their own advantage
leaving those upon who's shoulders they climbed in the dust. They go the extra
mile and reimplement in a way that reaches back down to enable the whole
community to benefit.
Those innovators give the most back to the community.
You're making much more out of this than is even worth it.
If you want to discuss bootchart on a technical level, I'm fine with that.
If you want to argue policy, please start a new thread or propose a
steering group meeting topic.
Auke
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
