On Fri, May 4, 2012 at 12:19 AM, Federico Mena Quintero
feder...@gnome.org wrote:
...
As a way to solve these issues, I'd like to follow up on an idea which I
sketched during last year's Desktop Summit - namely, about constructing
a pattern language for Gnome's design based on the good things
On Sat, May 5, 2012 at 4:09 AM, Federico Mena Quintero
feder...@gnome.orgwrote:
On Fri, 2012-05-04 at 00:03 -0500, Diego Escalante Urrelo wrote:
A common language of patterns is an awesome idea. I'd encourage
Federico to expand on the subject.
Calum, Allan, and generally the people around
As someone who is just starting to become involved in design development
after many years of using open source free software, I find these
discussions fascinating on multiple levels. For whatever reason I have
always found communities in free/open source software to be rather
intimidating, which
Il giorno 30/apr/2012 17:36, Bastien Nocera had...@hadess.net ha scritto:
* will be developed inside totem source tree (replacing?)
Yes. I think both the feature page and the mail to this list made it
pretty clear, even if glibly.
To be honest not so clear, at least to me. And to be
On Fri, 2012-05-04 at 00:03 -0500, Diego Escalante Urrelo wrote:
A common language of patterns is an awesome idea. I'd encourage
Federico to expand on the subject.
Calum, Allan, and generally the people around the London UX Hackfest
have already done a ton of work in this area:
I'm completely and utterly against this idea, you might push away the
noise, but you are pushing away all new contributors as well... how are you
supposed to become a design contributor if you're not a programmer and you
cannot contribute designs because you cannot join the mailing list since
you
On Wed, 2012-04-25 at 14:27 +0100, Allan Day wrote:
But there are challenges and things we can do better. Among those
obstacles, I see:
* lack of design resources - we are always trailing behind where we
want to be, and there are important tasks which we are unable to
complete (a new HIG
On Thu, May 3, 2012 at 5:19 PM, Federico Mena Quintero
feder...@gnome.org wrote:
As a way to solve these issues, I'd like to follow up on an idea which I
sketched during last year's Desktop Summit - namely, about constructing
a pattern language for Gnome's design based on the good things that
On Apr 25, 2012 8:43 AM, Allan Day allanp...@gmail.com wrote:
On Wed, Apr 25, 2012 at 9:55 AM, John Stowers
john.stowers.li...@gmail.com wrote:
So there are lots of ways that we can do design better as a community,
and contributors on this list can all play a part in helping to make
teams, more time you spend writing it, less time you'll spend explaing
here on desktop devel list :)
...
For me, design in the open is about developers and designers working
together as partners, not hyper-specified design documents.
Wait. I never said to keep apart designers and developers
document is a written contract[4] between designers and other
teams, more time you spend writing it, less time you'll spend explaing
here on desktop devel list :)
...
For me, design in the open is about developers and designers working
together as partners, not hyper-specified design
On Mon, 2012-04-30 at 16:36 +0100, Bastien Nocera wrote:
On Mon, 2012-04-30 at 16:52 +0200, Luca Ferretti wrote:
I don't want and I don't have time and resources to help you with
design or code writing. But I'm involved in this change and I feel I
need more info[1]. And developers will need
called design in the open though...
Cheers
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
designers and other
teams, more time you spend writing it, less time you'll spend explaing
here on desktop devel list :)
...
For me, design in the open is about developers and designers working
together as partners, not hyper-specified design documents. That might
not give observers as much
On Sat, Apr 28, 2012 at 2:02 PM, Rodrigo Moya rodr...@gnome-db.org wrote:
then, why not do the proposals for new designs here in d-d-l? That way
you might get initial feedback before starting on the design, and people
that feel ignored get info on what's going on. Then, you can just keep
time you'll spend explaing
here on desktop devel list :)
...
For me, design in the open is about developers and designers working
together as partners, not hyper-specified design documents. That might
not give observers as much to see, but it provides contributors with a
real opportunity to shape
Hi Allan
On Wed, 2012-04-25 at 14:27 +0100, Allan Day wrote:
Hi all,
Apologies in advance for the long mail - there was no other way.
There have been a few design-related threads on the list recently. I’m
going to try and reboot those discussions in a slightly different and,
I hope,
2012/4/25 Allan Day allanp...@gmail.com:
But there are challenges and things we can do better. Among those
obstacles, I see:
snip
* giving people a stake in the project - the danger of design-led
development is that people feel that the project is no longer theirs.
They want to feel they
Hi all,
Sorry in advance for the long e-mail and any eventual harsher remark :)
For some time now it seems that the way to create, lets say a new core
GNOME application has been to get someone from the design team to publish
rude mockups for a couple of screens in that App and then passing it on
On Thu, Apr 26, 2012 at 12:16 PM, Luca Ferretti lferr...@gnome.org wrote:
2012/4/25 Allan Day allanp...@gmail.com:
From my point of view the main issue (at least perceived as issue) in
current design-develop workflow is explanation.
While our design/ux team is able to produce great ideas,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/04/12 18:16, Luca Ferretti wrote:
While our design/ux team is able to produce great ideas,
frequently the only visible product of design work is a wiki page
with poor info. Or, at least, poor compared with documents and info
provided by
Hi all,
Apologies in advance for the long mail - there was no other way.
There have been a few design-related threads on the list recently. I’m
going to try and reboot those discussions in a slightly different and,
I hope, more constructive mode.
Let’s start with the big picture - design is
So there are lots of ways that we can do design better as a community,
and contributors on this list can all play a part in helping to make
us to be even more successful in this regard. It will take actions as
well as words to move forward, of course - if you want to help, or
have your own
Allan:
I think it is pretty clear that the GNOME UX team is pretty amazing.
As you say, though, I think we recognize that we need to improve in
areas like engagement.
With GUADEC around the corner, I think now is an important time to
make progress on getting better engagement between the
On Wed, Apr 25, 2012 at 9:55 AM, John Stowers
john.stowers.li...@gmail.com wrote:
So there are lots of ways that we can do design better as a community,
and contributors on this list can all play a part in helping to make
us to be even more successful in this regard. It will take actions as
On Wed, April 25, 2012 9:27 am, Allan Day wrote:
Echoing what Brian said, I like these suggestions for improvement! Are
there any that we can turn into concrete initiatives that we can organize
soon and perhaps fundraise for? Or build some initiatives for GUADEC? I
include a few more detailed
I am happy Allan drafted the problem thoroughly and and also provided
initial steps that could solve it.
Well done.
On Wed, Apr 25, 2012 at 7:45 PM, Karen Sandler ka...@gnome.org wrote:
On Wed, April 25, 2012 9:27 am, Allan Day wrote:
Echoing what Brian said, I like these suggestions for
On Wed, Apr 25, 2012 at 6:45 PM, Karen Sandler ka...@gnome.org wrote:
On Wed, April 25, 2012 9:27 am, Allan Day wrote:
Echoing what Brian said, I like these suggestions for improvement! Are
there any that we can turn into concrete initiatives that we can organize
soon and perhaps fundraise
On Wed, Apr 25, 2012 at 10:21 PM, Allan Day allanp...@gmail.com wrote:
...
* better testing facilities so people can test and give feedback on UX
changes before release time
What would this entail? This sounds like it could be incredibly helpful if
we could find the resources for it.
There
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/04/12 15:27, Allan Day wrote:
* lack of design resources - we are always trailing behind where
we want to be, and there are important tasks which we are unable
to complete (a new HIG springs to mind)
Caused by this, the design process in
30 matches
Mail list logo
