Re: [Gimp-developer] hesitant about compiling a list...

[Øyvind Kolås <pippin gimp org>]

On Thu, May 17, 2012 at 4:19 PM, peter sikking <peter mmiworks net> wrote:
> within a minute we were talking about whether GIMP has a list
> of known UI design issues. as far as I know we do not have one,
> it is certainly not part of gui.gimp.org.
> - just thinking of what I can contribute to this list, I know
> that this list is _not_ going to be short. also because all the
> issues that I can put on it are ‘medium level to big-picture,’
> none of them are going to be trivial to solve. thus my hesitation
> is what this is going to make GIMP look like, and if the definitions
> of open worked where meant to stretch this far.
>
> - all of the issues that will end up on the list have been
> created by contributors to GIMP. some of these issues have been
> created 10 years ago, some of them last month. I wonder what it
> will feel like to GIMP contributors when something they just made,
> almost ‘immediately and automatically,’ (at least, feels like that
> to them) ends up on the UI issue list.

This is what doing work in the open is about, be open about what one
is doing; known shortcomings as well as calling out for help.
Maintaining such a list also can improve the perception users have; in
that in reading such a list they get a feeling for what direction GIMP
as a project wants to move in; working on such a list in the open is
also something that can make developers feel larger ownership of the
projects direction. You might even be surprised about what existing
GIMP developers might volunteer as problems with things they
themselves have made ;)

/Ø
-- 
«The future is already here. It's just not very evenly distributed»
                                                 -- William Gibson
http://pippin.gimp.org/ ;                           http://ffii.org/