Re: [Gimp-developer] Enhancement request policy

2016-05-04 Thread C R
> > > Spotted the lurker having a bad day :) > > All of us play that part sometime. It's important to get over it and move on, and not to send out emails to the group while upset. Being part of the community means being social. Part of being social is not being a lurker. :) > You say that noone

Re: [Gimp-developer] Enhancement request policy

2016-05-03 Thread john smith
On 29 April 2016 at 13:52, C R wrote: >> My experience is that GIMP developers don't care what any user would >> like to have. > > > Clearly untrue. We have the Unified Transform Tool, hardware acceleration, > Mypaint brush engine, and (up to) 64bit colour depth, and linear

Re: [Gimp-developer] Enhancement request policy

2016-04-29 Thread C R
> > My experience is that GIMP developers don't care what any user would > like to have. > Clearly untrue. We have the Unified Transform Tool, hardware acceleration, Mypaint brush engine, and (up to) 64bit colour depth, and linear light blending modes to look forward to in the next release, the

Re: [Gimp-developer] Enhancement request policy

2016-04-29 Thread Alexandre Prokoudine
29 апр. 2016 г. 19:37 пользователь "john smith" написал: > > My experience is that GIMP developers don't care what any user would > like to have. What experience would that be exactly? Alex ___ gimp-developer-list mailing list List address:

Re: [Gimp-developer] Enhancement request policy

2016-04-29 Thread Paka
* john smith [04-29-16 12:38]: > My experience is that GIMP developers don't care what any user would > like to have. > The general response is "we have previously decided that we want to do > it like this and we aren't interested in how the end user might find > something

Re: [Gimp-developer] Enhancement request policy

2016-04-29 Thread john smith
My experience is that GIMP developers don't care what any user would like to have. The general response is "we have previously decided that we want to do it like this and we aren't interested in how the end user might find something useful". This is in stark contrast to most of the other open

Re: [Gimp-developer] Enhancement request policy

2016-04-23 Thread Bill Skaggs
The great advantage of the bug-tracker is that it allows requests to be handled in a structured way. It is easy to find specific types of enhancement requests in the bug-tracker and examine the priority they have been given and the discussion that followed them. Getting this information from a

Re: [Gimp-developer] Enhancement request policy

2016-04-23 Thread Tobias Ellinghaus
Am Samstag, 23. April 2016, 11:40:26 schrieb Euri Pinhollow: [...] > Bugtracker is for developers and they should pick doable tasks from > forum themselves. Most developers are too busy doing developing to read any forums. Communication is either actively pushed their way (i.e., via mail) or

Re: [Gimp-developer] Enhancement request policy

2016-04-23 Thread Euri Pinhollow
My point of view is: enchancements should be discussed on the forum, not in a bugtracker. Here is what DispCalGUI has: https://hub.displaycal.net/forums/ Mailing list is not exceptionally convenient for many people (myself included. I just mailed topic starter instead of mailing to the list

Re: [Gimp-developer] Enhancement request policy

2016-04-19 Thread Sven Claussner
Hi, no reply yet. I asked the devs to discuss it at the LGM, but so far I don't see anything in the (intermediate state of) the meeting minutes. Was it discussed and to which result? Greetings Sven ___ gimp-developer-list mailing list List

[Gimp-developer] Enhancement request policy

2016-04-13 Thread Sven Claussner
Hi, in the light of current events one problem comes up again: how do we deal with enhancement requests reported in Bugzilla? Currently we count 1'193 open GIMP bugs, of which 607 are enhancement requests. We're drowning in them. In 2015 Jim DeLaHunt pointed out a discrepancy between the