Submit your wallpapers for Fedora 19! (Deadline extension, too!)

You may have seen Gnokii’s call for Fedora 19 wallpaper submissions a few weeks ago. We are still accepting supplemental wallpapers, and have extended the deadline from March 31 to April 10th! There’s a few guidelines you must follow in making your submissions – they have to be under a free license, they have to be at least a certain minimum resolution, and in a certain format, among other things. Gnokii’s blog post on submitting supplemental wallpapers covers these in detail. To submit, you simply upload your submission to the Fedora 19 Supplemental Wallpapers page on Fedora’s wiki. It’s that simple! We’re really looking forward to see your submissions. 🙂 Submit your wallpaper now!

Improving the Fedora boot experience

If you’re subscribed to Fedora’s devel list, then you probably noticed this thread about improving Fedora’s boot experience explode over the past two days. So I have this thing on my desk at Red Hat that basically defines a simple design process. (Yes, it also uses the word ‘ideate’ and yes, it sounds funny but it is a real word apparently!) While the mailing list thread on the topic at this point is high-volume and a bit chaotic, there is a lot of useful information and suggestions in there that I think could be pulled into a design process and sorted out. So I took 3 hours (yes, 3 hours) this morning to wade through the thread and attempt to do this. 1. Define the problem What problem(s) are we actually trying to solve in the boot process? You have to know what you’re trying to solve – then you’ll know whether or not a given solution will fix the problem, and you’ll also know later on how to evaluate (after the work is done) whether or not you actually fixed the problem. So what exactly is the problem with Fedora’s boot experience? Here is the high-level problem: Fedora 18’s …

RAID Re-do for Anaconda

Remix of Cartoon Rattlesnake by Sirrob01, Spray Paint in Action by Guillaume W., and Tango Drive Hard Disk by Warszawianka on OpenClipArt. Yes, that is a snake spraying RAID onto a pile of disks. So I think out of all of the feedback we got about the Anaconda UI redesign, the one piece of the UI that’s received the most negative feedback is the RAID configuration piece of the custom partitioning UI. The designs for how this UI ended up getting implemented in Fedora 18 was posted to this blog in December 2011. I really wish we’d received the level of feedback we received post F18-Beta and post F18-GA at that point, so the design could have been modified before it was implemented! That being said – I’m not placing blame with anybody but myself – I got this design wrong, and for that I am sincerely sorry. The initial design The idea behind the initial design was to not have a simple dropdown with a list of RAID numbers, because we found in our research even trained sysadmins don’t tend to remember what every single RAID level means or which one is best for which situations. When you don’t …

Refreshing storage in Anaconda

Remixed version of bottles by Tomas Arad on OpenClipArt. You must be thinking: “What do you mean by refreshing storage? I didn’t think you could drink storage?” No, sad to say, this blog post isn’t about the type of refreshment you get from a crisp cold glass of Anaconda Cola (yum!) It’s about the action of manually refreshing anaconda’s view on the storage configuration it’s working with. Why would you want to do that? Let’s step back a second first. The custom partitioning tool in Anaconda (Fedora’s installer) still has a lot of rough edges to the design in Fedora 18 GA. The Anaconda team has been putting a lot of work into improving it in their Fedora 19 branch. We’ve got a ton of bugs, thoughtful (and some not so thoughtful 🙂 ) comments from forums and blogposts, and some preliminary anaconda usability test data! (You’ll be hearing a lot more about that last bit soon, don’t worry! 🙂 ) The team has pored over all of this information and has had a number of brainstorming sessions and discussions on how to address the identified issues, both over IRC, the mailing list, in bugs directly, and in person. The …