This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new Linux.com!

Linux.com

Re(2): I agree. The GIMP team talks out of both sides of its mouth ...

Posted by: Anonymous [ip: 193.155.95.1] on November 09, 2007 09:55 AM
Well, let's concentrate on the message you pointed to.

How would you suggest such cases to be handled:


- "wow, nice proposal"... and then nothing happens

- "wow, nice proposal"... and then the developer spends a lot time investigating for this one feature, implements it in a time he could have done multiple others, better specificed ones (coming up with specs which remove the need for research by developers is what Sikking's team does, btw)

IMO it is better to be frank from the beginning - telling the user about problems with the proposal (just like Sven did), and telling them how it can be improved (by providing details or by finding a developer who is interested in implementing it).

Or something else? How would you have responded?

#

Return to When open source projects close the process, something's wrong