Bruce wrote:
[I will snip here quite a bit to keep this post from ballooning]
> Hi guys, I'm the Bruce that Peter referred to in the first post in this
> thread.
>
> How open does it make sense to be?
>
> I think a good approach is to be open to the degree where it is constructive
> and feel
Hi guys, I'm the Bruce that Peter referred to in the first post in this
thread.
I thought I'd share some feedback about this, but in more of a brainstorm
sort of way where we can just share and discuss ideas for what such a list
might look.
That way we can put the idea of creating it aside for th
On 17 May 2012 16:19, peter sikking wrote:
> a couple of days ago Bruce appeared on irc and we had a chat.
> (Bruce is now subscribed to this list)
>
> 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
On Thu, May 17, 2012 at 4:19 PM, peter sikking 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
Hi Peter,
my opinion is 'the clearer the better'.
Such a list could IMHO improve GIMPs product quality.
Even if it will be a long list (and it will be growing, as user
requirements and wishes always become more) this will show the necessity
to priorize.
I'm not (or not yet) a GIMP developer, bu
How about you start your list with issues that are at least 18 months old?
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-developer-list
guys,
a couple of days ago Bruce appeared on irc and we had a chat.
(Bruce is now subscribed to this list)
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.
(I am not talking abo
