Suggestion for Konquerer developers and delivering "stripped" releases

[Randy Kramer]

On Friday 10 November 2006 11:41 am, Kimberly Lazarski wrote:
---<other good stuff snipped>---

> You haven't worked with a lot of developers then. The very best
> architects I know sketch GUIs and flowcharts on paper in meetings with
> UI designers and other developers, mocks up the GUI in VB or even Paint
> for review of the workflow, then start coding.  Of course that has been
> for enterprise apps and commercial products.

Thank you!

---<more good stuff snipped>---

> You ask for good feedback, you got it, and now you're telling the user
> to STFU? Who is the arrogant one here? This is EXACTLY the kind of thing
> that keeps open source out of corporate environments, and keeps open
> source out of the home market.  Why are you involved in the project if
> all you are going to do is tell the user to "shut the fuck up?"  Why
> don't you just ask for more detail in the defect report/feature
> request/feedback, or if you can't be bothered, just quit? I've seen
> developers with your attitude in the industry, and they tend to not last
> long because the rest of the development organization tends to hate
> them. They can't take suggestions, criticism, feedback, and invariably
> will do what they want to do regardless of logic or team consensus.
> There are times to buck the trends, but it should be done amicably, with
> respect and tact.

Thanks again!

> To the rest of the KDE team: THANK YOU for all of your hard work. IMHO,
> KDE is the best desktop environment around, even with whatever
> shortcomings it may have. Please keep up the good work, and _please_
> receive feedback from users with grace.

+1 (or more) 

Randy Kramer