Ayatana is the right place for discussion, the topic of this list is clear
to all of us.
As long as the discussion you want to kick off is not OT, i for one am
interested in hearing your thoughts..
On Wed, May 5, 2010 at 05:50, Ralph Green wrote:
> On 4/27/10, Martin Owens wrote:
> > A few of m
On 4/27/10, Martin Owens wrote:
> A few of my community circles react to Design Team news with a *sigh*
> and "Oh god what have they done now". The teams reputation is low and
> it's over shadowing the really great work that's going on. How can I
Howdy,
The team has done a lot of good work, yet
2010/4/30 Diego Moya
> 2010/4/30 Martín Soto :
> > The fact that human brains posses such a high plasticity, however, is no
> > excuse for us not getting our act together. Whenever you change a UI, you
> > will break someone's habituation to that UI.
>
> Not if you support both interactions, the
On Fri, Apr 30, 2010 at 09:04, Vishnoo wrote:
> .. folks think some decisions are being
> truly dictatorial.
>
like most people here realize:
good PR will do the trick.
tell the people timely, inform them about the radiant enlightenment that
awaits them, and they will embrace the changes thankfu
Thank you, Diego, for your very well-articulated thoughts.
Your thoughts echo my own concerns (and I'm sure the concerns of many
others) regarding the challenges faced when design/experience changes aren't
qualified, aren't scoped adequately, or aren't communicated effectively.
2010/4/30 Diego M
2010/4/30 Martín Soto :
> The fact that human brains posses such a high plasticity, however, is no
> excuse for us not getting our act together. Whenever you change a UI, you
> will break someone's habituation to that UI.
Not if you support both interactions, the old and the new. In many
cases thi
On Wed, Apr 28, 2010 at 6:55 AM, Diego Moya wrote:
...
I'm the first one to defend a simplified design for entry-level to
> average users even if it doesn't support expert features. But this
> kind of design should be only for new features and never, ever be put
> in place of a previous design al
On Thu, 2010-04-29 at 19:40 -0400, Martin Owens wrote:
> On Thu, 2010-04-29 at 11:19 +0100, Mark Shuttleworth wrote:
> > and yet everyone will have their
> > idea of what piece is the most valuable to the most people. The
> > specification describes the things that we believe are the most
> > impor
On Thu, 2010-04-29 at 11:19 +0100, Mark Shuttleworth wrote:
> and yet everyone will have their
> idea of what piece is the most valuable to the most people. The
> specification describes the things that we believe are the most
> important for the most people. Those pieces are not revealed as
> tool
On Wed, Apr 28, 2010 at 10:18 PM, Mario Vukelic
wrote:
> But as I mentioned, the facilities are in place to display information
> *right at install* of a change. They just usually are not used. And I'm
> not talking about complete release notes (which are published on the
> website for each milest
On Thu, 2010-04-29 at 11:35 +0200, Paolo Sammicheli wrote:
> I'm so sorry to disagree with you in this. The entire process, from my
> perspective,
> worked regardless the schedule. Theme was applied the day before the UI
> freeze without
> any previous discussion or even information. Then butto
Hello Martin (and everyone):
Just a few comments on your post:
First of all, I also believe that better communication with the (technical)
community would be very valuable. Obviously, Canonical and the UI team have
failed so far in selling their work to large fractions of the Ubuntu
community and
On 29/04/10 10:35, Paolo Sammicheli wrote:
> And LoCos still don't have the font for updating their sites.
>
The font is still being designed, it is not complete, you will have it
when we have it.
Mark
signature.asc
Description: OpenPGP digital signature
>> On point 1: Looking at the tooltip bug in particular. The argument was
>> made that "menus don't have tooltips". But the *main* ubuntu menus,
>> for Applications, Places, and System, *all* have tooltips. As far as I
>> know, this was never addressed.
>
> That's easily addressed, thanks for the r
On 29/04/10 06:35, Jeremy Nickurak wrote:
> On point 2: People lost the ability to manage fine-grained
> information, or in some cases, information at all. "Time to charge
> battery" is still missing, as are many of the other things people
> brought up in that bug.
Is it not available if you dig i
Disclaimer:
---
Not being English native speaker I tend to sound more rude than I would, my
apologize in
advance. My real intention is to provide a positive contribution to the
discussion.
Alle 23:22 del 27/4/2010, Martin Owens ha scritto:
> A few of my community circles react to Desi
Let's look at the "tooltip" dialog as an example of a place where people are
still "resisting change".
https://bugs.launchpad.net/indicator-application/+bug/527458?comments=all
I'd argue that what people are really concerned about is two things:
1. A lack of consistency in the decision proces
On Thu, 2010-04-29 at 00:32 +0200, Jan Claeys wrote:
> I agree providing end-user upgrade notes might be a good thing, but of
> course those won't be ready until near the release, as not all
> proposed changes will end up in the release...
But as I mentioned, the facilities are in place to displa
On Wed, Apr 28, 2010 at 2:40 AM, Mario Vukelic
wrote:
> The experience is that as an interested
> user you are running the development version for months during the
> alphas with great expectations but nothing much to see UI-wise, and
> suddenly sweeping and often problematic changes land late in
Op woensdag 28-04-2010 om 08:40 uur [tijdzone +0200], schreef Mario
Vukelic:
> Maybe it would help to provide explanations, links to feedback options,
> etc. along with the changes. Currently users need to seek out the
> information on their own - and often the first thing they read is an
> inaccur
On Tue, 2010-04-27 at 23:55 -0500, Diego Moya wrote:
> Are you willing to compromise
> the design decisions and adapt to those multiple considerations, or
> are you going to push one "pure" solution for its expected benefit in
> some specific cases? It's hard to balance both ways
Yes it is hard a
On Tue, 2010-04-27 at 23:55 -0500, Diego Moya wrote:
> In the cases I've witnessed, the hyperbole works more like "we've
> broken the current workflow for some real existing users in benefit of
> some hypothetical newcomers that could or could not use the new
> feature. And we don't provide a way
On Tue, 2010-04-27 at 17:22 -0400, Martin Owens wrote:
>
> A few of my community circles react to Design Team news with a *sigh*
> and "Oh god what have they done now". The teams reputation is low and
> it's over shadowing the really great work that's going on. How can I
> convince people to trust
On 27 April 2010 16:22, Martin Owens wrote:
> Some of that good dialectic goes on here in this mailing list, but
> that's not communicated much outside where it would do good to calm
> people. I believe some of the problems stem from language of outside
> publishings, e.g: "We've made this choice b
+1 Martin, well said.
Benjamin
(Sent from my Android, please ignore any typos!)
On 28/04/2010 9:23 AM, "Martin Owens" wrote:
Hello,
This is an invitation to all designers who will be at UDS-M soon to talk
about reducing the resistance in the community to Ayatana developments
and directions. So
Hello,
This is an invitation to all designers who will be at UDS-M soon to talk
about reducing the resistance in the community to Ayatana developments
and directions. So I want to kick off a discussion here and then carry
it on at UDS:
We've seen in the wider community resistance for a number of
26 matches
Mail list logo
