Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-02-21 Thread Adam Williamson
On Thu, 2014-02-13 at 09:36 -0500, Kamil Paral wrote: On Tue, 11 Feb 2014 12:38:44 -0800 Adam Williamson awill...@redhat.com wrote: On Tue, 2014-01-14 at 09:47 -0800, Adam Williamson wrote: On Tue, 2014-01-14 at 10:44 -0700, Mike Ruckman wrote: I'm +1 in general and +1 for

Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-02-13 Thread Kamil Paral
On Tue, 11 Feb 2014 12:38:44 -0800 Adam Williamson awill...@redhat.com wrote: On Tue, 2014-01-14 at 09:47 -0800, Adam Williamson wrote: On Tue, 2014-01-14 at 10:44 -0700, Mike Ruckman wrote: I'm +1 in general and +1 for the Kamil edit. Because anaconda allows that config, it

Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-02-13 Thread Matthew Miller
On Tue, Jan 14, 2014 at 08:03:02AM -0800, Adam Williamson wrote: I'm working on the assumption that there'll still be a base product for us to validate whatever else happens, and it's better to keep working on our processes for that than to just sit around on our hands. As I understand it, the

Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-02-12 Thread Mike Ruckman
On Tue, 11 Feb 2014 12:38:44 -0800 Adam Williamson awill...@redhat.com wrote: On Tue, 2014-01-14 at 09:47 -0800, Adam Williamson wrote: On Tue, 2014-01-14 at 10:44 -0700, Mike Ruckman wrote: I'm +1 in general and +1 for the Kamil edit. Because anaconda allows that config, it should

Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-02-11 Thread Adam Williamson
On Tue, 2014-01-14 at 09:47 -0800, Adam Williamson wrote: On Tue, 2014-01-14 at 10:44 -0700, Mike Ruckman wrote: I'm +1 in general and +1 for the Kamil edit. Because anaconda allows that config, it should work. anaconda allows you to use any configured layout during anaconda itself, but

Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-01-14 Thread Kamil Paral
So, I'm proposing we add a section to https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#Post-install_requirements which states that at decryption and login stages, the systemwide keyboard layout must be used, and post-login, the systemwide layout must be used if no per-user

Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-01-14 Thread Adam Williamson
On Tue, 2014-01-14 at 09:31 +, Jóhann B. Guðmundsson wrote: On 01/14/2014 09:24 AM, Kamil Paral wrote: ACK in general. Nack We will need to refactor the entire criteria around the output from WG's if the board will sanction the injustice that's going on. Technically there is

Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-01-14 Thread Adam Williamson
On Tue, 2014-01-14 at 09:22 -0500, John Dulaney wrote: I'm also +1 in general; Kamil does raise a good point about the systemwide layout being available, but not required to log in. Yeah, it's a reasonable point and I've seen the feature suggested, but I'm not aware of any DM that implements

Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-01-14 Thread Jóhann B. Guðmundsson
On 01/14/2014 04:03 PM, Adam Williamson wrote: I'm working on the assumption that there'll still be a base product for us to validate whatever else happens, and it's better to keep working on our processes for that than to just sit around on our hands. -- On that note just add it we can

Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-01-14 Thread Mike Ruckman
On Tue, 14 Jan 2014 04:24:15 -0500 (EST) Kamil Paral kpa...@redhat.com wrote: So, I'm proposing we add a section to https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#Post-install_requirements which states that at decryption and login stages, the systemwide keyboard layout

Release criteria proposal: explicit requirements for keyboard layouts

2014-01-13 Thread Adam Williamson
Hey, folks. So I'm currently looking through f20 blocker review logs to try and catch cases where the criteria clearly weren't as clear as they could be. One that showed up quickly is something of a greatest hit: keyboard layout problems. It's quite often the case that keyboard layout selection

Re: Release criteria proposal: explicit requirements for keyboard layouts

2014-01-13 Thread drago01
On Tue, Jan 14, 2014 at 1:49 AM, Adam Williamson awill...@redhat.com wrote: Hey, folks. So I'm currently looking through f20 blocker review logs to try and catch cases where the criteria clearly weren't as clear as they could be. One that showed up quickly is something of a greatest hit: