Re: Feature proposal: combined system status menu

2013-04-24 Thread Luc Pionchon
On 24 April 2013 04:54, Mathieu Bridon boche...@fedoraproject.org wrote: On Wed, 2013-04-24 at 04:00 +0300, Luc Pionchon wrote: On 24 April 2013 02:14, Florian Müllner fmuell...@gnome.org wrote: On Tue, Apr 23, 2013 at 11:09 PM, Marco Scannadinari ma...@scannadinari.co.uk wrote: I

Re: Feature proposal: combined system status menu

2013-04-24 Thread drago01
On Wed, Apr 24, 2013 at 1:14 AM, Florian Müllner fmuell...@gnome.org wrote: On Tue, Apr 23, 2013 at 11:09 PM, Marco Scannadinari ma...@scannadinari.co.uk wrote: In fact, I think that these sorts of subtle design-based decisions should be held in something like loomio (see recent loomio post

Re: Feature proposal: combined system status menu

2013-04-24 Thread Florian Müllner
On Wed, Apr 24, 2013 at 9:53 AM, Luc Pionchon pionchon@gmail.com wrote: The main point is that so-called controversial features does not have to be either a hard default, either rotting in a branch. They can be shipped as default, but with a way to revert them in the case they block the

Re: Feature proposal: combined system status menu

2013-04-24 Thread Luc Pionchon
On 24 April 2013 11:57, Florian Müllner fmuell...@gnome.org wrote: On Wed, Apr 24, 2013 at 9:53 AM, Luc Pionchon pionchon@gmail.com wrote: The main point is that so-called controversial features does not have to be either a hard default, either rotting in a branch. They can be shipped

Re: Feature proposal: combined system status menu

2013-04-24 Thread Gil Forcada Codinachs
Planning an ostree hackfest would be more useful I would say, instead of arguing over (another) new way of shipping code to users/developers/testers... Once ostree is usable all this will be moot: let developers code the thing and once finished let everyone know that feature X can be tested with

Re: Feature proposal: combined system status menu

2013-04-24 Thread Florian Müllner
On Wed, Apr 24, 2013 at 3:51 AM, Sriram Ramkrishna s...@ramkrishna.me wrote: At least until we get a better testing infrastructure in place, the only way to get at least *some* user testing is [...] to get some minimal exposure to adventurous users of unstable/experimental distributions Again

Re: Feature proposal: combined system status menu

2013-04-24 Thread Colin Walters
On Wed, 2013-04-24 at 12:22 +0200, Florian Müllner wrote: First: If we are actually ready to roll out ostree images, that's awesome news! Depends who the audience is...no security updates and you need to build applications from source. But if you want to see GNOME as it is a few minutes or

Re: loomio

2013-04-24 Thread אנטולי קרסנר
Hi, is there any progress with this? I there a Gnome team willing to be the pioneer and try loomio, and report about the experience? I don't belong to any team so I can't take responsibility personally (but I'll help you, if you decide to give loomio a try). Anatoly On א', 2013-04-14 at 11:36

Re: Touchscreen Compatibility [was: Feature proposal: combined system status menu]

2013-04-24 Thread Allan Day
Alberto Ruiz ar...@gnome.org wrote: ... we have to question ourselves if this is another trend like the netbook one that is somewhat transient and misleading. ... I'd make a distinction here between transformers (Docable tablet that turns into a laptop+trackpad) that switches between touch

Re: Touchscreen Compatibility [was: Feature proposal: combined system status menu]

2013-04-24 Thread Tomas Frydrych
Hi Allan, On 22/04/13 16:26, Allan Day wrote: Alberto Ruiz ar...@gnome.org wrote: I am not sure what the criteria is with this regard and I might have miss a public discussion about it. What are we trying to accomplish with this whole trend towards touch? I haven't seen any successful single

Re: loomio

2013-04-24 Thread Marco Scannadinari
Hi, is there any progress with this? I there a Gnome team willing to be the pioneer and try loomio, and report about the experience? I don't belong to any team so I can't take responsibility personally (but I'll help you, if you decide to give

Re: loomio

2013-04-24 Thread Sriram Ramkrishna
Well the non-coding parts might accept it. The problem with voting is that it is an emotional choice when it comes to people who are voting and are not part of development. Which can lead to all kinds of conflicts in trying to decide how things develop. If we had voting, we would have had to

Re: Touchscreen Compatibility [was: Feature proposal: combined system status menu]

2013-04-24 Thread Allan Day
Tomas Frydrych tf+lists.gn...@r-finger.com wrote: ... As a basic, but I think pertinent, example -- if one of the reasons for the current design being touch unfriendly is that certain UI elements are too small (which is the most rudimentary problem any UI moving from pointer to touch faces),