Fedora blogs retirement and how to migrate to WordPress.com

Fedora has offered a hosted blogs system using WordPress MU for the past couple of years of so. Nirik recently announced that the Fedora blogs system is going to be retired on July 1, 2011. Note: just the blogs.fedoraproject.org hosted blog system is being retired. Planet Fedora is of course alive and well and will be sticking around! 🙂 Nooooo!! Why??? (Queue Darth Vader noooooo? 🙂 ) There’s been a number of factors that lead the Fedora infrastructure team to decide to retire the service. Fedora infrastructure team hackfest in the FUDcon Tempe hotel lobby At FUDcon Tempe this past January, the Fedora infrastructure team had a face-to-face meeting/hackfest to discuss future direction for the team. While the Fedora community continues to come up with great new ideas for Fedora that involve an infrastructure component, including many of the ideas in ‘The Next Big Fedora Engineering Project’ session lead by Spot, there’s a lot of pre-existing infrastructure – some not actively used – that is currently being maintained by Fedora infrastructure team members. The more infrastructure on the team’s maintenance plate, the less cool new projects involving infrastructure that we can easily do as a community. Fedora infrastructure team hackfest …

Version-controlled, automagical backup and file sharing system with Sparkleshare and Fedora

The Burden of files

Okay, there’s a lot of problems:

  • Backing up your files is a pain in the butt.
  • Every time you upgrade your system, either in-place or a fresh install, it is a royal hassle to restore your files.
  • That file looks great on your laptop, but how do you show it to a colleague not sitting next to you easily? Ughh.
  • You upload files to a random directory on some web server you have some space on, quickly to show an idea to someone. Fast-forward some time, and you’ve got disorganized, poorly-named files scattered across multiple shell / other accounts all over the web, and you’re not sure what you have a copy of where, or which ones are being referred to from other places, so you’re terrified to delete any of them.
  • Well, crap. You’ve made a mistake. You can’t go back, can you? No version control…

I think we all know these problems pretty well. I’ve built a solution using Fedora and Sparkleshare – completely free and open source software – that over the past week has addressed all of these issues and has substantially improved the quality of my computing life. It backs my work files up to an internal corporate server and it backs my Fedora files up to a Fedora-maintained public server. I’m planning to configure it to back up some personal files to my Dreamhost account and some to my NAS at home.

Design team imageboard test server and WE NEED Fedora 16 theme artists!

Fedora Imageboard Test Server Yesterday with some help from smooge and nb, I set up a Danbooru-style image board to test out, and I am hoping that Fedora artists and designers might play with it and see if it’d be a useful resource. It’s an application called Shimmie. What is an imageboard? It’s a bulletin board or forum type of website that focuses much more heavily on images rather than text. You can read more about them in Wikipedia’s article. Traditionally they are used for ‘found’ images, and I don’t know if they are used much by folks who are generating original artwork, but it seems as if they would be a useful tool for collaborative image production, as they would keep discussion focused on visuals. Anyway, if you are so artistically inclined, please feel free to try it out. It is a test server and it is not backed up, so make sure you keep local copies of your drawings or also copy them to your fedorapeople.org account. http://publictest04.fedoraproject.org/artboard/ Fedora 16: Verne I think maybe this imageboard it might be a cool opportunity to start sketching, sharing, and collaborating some Jules Verne and/or steampunk artwork ideas for Fedora 16 …

Ideas for a cgroups UI

On and off over the past year I’ve been working with Jason Baron on a design for a UI for system administrators to control processes’ and users’ usage of system resources on their systems via the relatively recently-developed (~2007) cgroups feature of the Linux kernel. After the excitement and the fun that is the Red Hat Summit, I had some time this week to work with Jason on updating the design. Before I dive into the design process and the mockups, I think it’d be best to do a review of how cgroups work (or at least how I understand them to) so that the rest makes more sense. (And maybe I’ve got some totally incorrect assumptions about cgroups that have resulted in a flawed design, so hopefully my calling out the current understanding might make it easier for you to correct me 🙂 ). A designer’s understanding of cgroups via diagram So cgroups, which are sometimes referred to as containers (I think because a similar Solaris feature, zones, is sometimes called containers) can be used to slice an entire operating system into buckets, similarly to how virtual machines slice up their host system into buckets, but without having to …