Petrus Lundqvist wrote:
>
> > "Criticizing an Open Source project for their level of progress is akin to
> > criticizing someone else for not giving enough to charity, while giving none
> > yourself."
>
> Quotation marks? So who said it? Personally, I think that's completely
> irrelevant. If the release date slips it slips and it's a bad thing. It
> doesn't matter if you have a great "quote" to explain it with - the fact
> is still that the release date has slipped huge amounts and it is causing
> the project to lose credibility.
Well, the project I am working on has slipped more than a year and
recent problems, out of the control of anyone on the project, will
induce months more slip. I have been criticized for not removing the
1998 copyright from many of my source and other files pertaining to the
project. However, I cannot change the history of the project with a text
editor.
> That said, I think the "quote" sucks. There's faulty logic in assuming you
> can't give critics about something even though you're not doing it better
> yourself. I can say that a golf player sucks and I can point out his
> weaknesses even though I can't play golf myself.
>
> Peppe
But is the criticism valuable when it is nonspecific? Does it change the
position of the sun to criticize a clock for being an hour off? In what
way does your critical comment in any way help the project? In no way.
It is worthless because it can change nothing and offers no value to the
project.
Critical comment such as yours is meaningless. It brings to light no
error that can be corrected. This is why the quote in a previous post is
more to the point. If you are critical of a golfer, should the golfer
listen to you? Since you do not play, the answer is a resounding no.
Chuck
--
... The times have been,
That, when the brains were out,
the man would die. ... Macbeth
Chuck Simmons [EMAIL PROTECTED]
