The big news today (at least in my circles) is the Fedora 23 release. Check out the release announcement and then head over to GetFedora.org to grab the bits.
You might also want to peruse the What’s New in Fedora 23 Workstation piece on Fedora Magazine to learn about some of the changes on the Fedora desktop.
There’s a slight bug with the Atomic Docker when using root bind mounts, but this should be addressed shortly with the two-week Atomic builds (expected to roll out mid-November).
Here’s something I spend a lot of time thinking about: What constitutes “real” open source? Not just the license, I think the OSI has done just fine in defining an open source license. (And the GNU/FSF folks have done just fine in defining a Free software license as well.)
I’m asking, what constitutes a real open source project? What are the specific things you need to say “yep, this is a genuine open source project that really deserves the title”?
Curious what other folks think. It probably comes as no surprise that I don’t consider a project “open” just because there’s a public repository with code that is under an OSI-approved license.
Also curious of any bodies like the OSI have working definition. So many projects and companies lay claim to open source, but I see very little of it in practice.
Here’s a pet peeve of mine, because I see it time and time again: Folks work on software or projects, put in a ton of effort, and then do nothing to promote the project or release. (And, for bonus points, complain that they don’t understand why the project isn’t getting more attention!)
This doesn’t mean developers have to do double-duty as marketeers and public relations folks. Well, not if they can pass the torch onto interested contributors who are happy to do it for them, anyway. It requires a little coordination and effort, but why put all the work into a project and then not get the attention of the users (and potential contributors) you’re trying to reach?
Additionally, it really helps to blog, tweet, and otherwise spread the word about projects while they’re in process. If you want people to collaborate, they really need to know that you’re doing something.
This isn’t necessarily intuitive for folks, I understand. But it is absolutely, vitally, necessary. Maybe, occasionally, a project is just so darn awesome that somebody happens to stumble on it via GitHub or whatever and word of mouth makes it a success – but typically, things get out into the world via consistent updates and communications to the right channels to get the word out.
One of the most exciting projects I’m getting to work with these days is Project Atomic. It touches on the full stack–from OS development to storage, to networking, containers, application development, and pretty much everything in between. Red Hat is working hard on the tools to develop, deploy, and manage containerized applications.
As part of that effort, I’m looking to find a lead for community efforts around Project Atomic and our container tools. (Job description on the Red Hat Jobs site.)
Ideally, we’ll find someone with some experience using Linux, Docker, Kubernetes, and so on. Also looking for someone with strong community background, able to work in the open and manage a number of open conversations across projects. Experience with the Fedora and CentOS projects a major plus.
There’s a ton of work to do, and things are moving really fast–so it’s definitely going to require someone well-organized and eager to stay on the leading edge of technology while the container ecosystem continues to move at a crazy pace. But, you’ll have the chance to work with a great team full of smart, friendly folks who are seriously passionate about open source.
Know somebody who’d be fantastic? Drop me a note. Username is jzb, and I work for Red Hat – shoot me an email with a resume! You can also find me on Twitter and occasionally on Freenode if you have any questions.
I love the “archive” button in Thunderbird (which was adopted from GMail, I think…) and (so far) am enjoying KMail. However, I was missing the “read it, don’t need to do anything further with this email – so put it in my 2015 folder.”
A quick trip to the googles brought up a helpful post on Superuser.com that walks through the steps quite handily to set up a filter that you can apply manually. Probably obvious to folks who’ve been using KMail for a long time, but there ya go.
Even though Fedora 23 isn’t quite out the door yet, officially, I have been poking at the alpha and beta because… that’s what you do. Well, it’s what I do, anyway. Call it a form of desktop wanderlust, I am always itching to see what’s next and what might be new and fun around the corner. (This also has the benefit of hitting bugs before folks who feel slightly less adventurous.)
I’ve put Fedora 23 onto a ThinkPad T430s and decided to go with KDE rather than GNOME this time around, and to experiment with different mail clients as well.
Right now, I’m tinkering with KMail – past attempts at KMail have resulted in dissatisfaction, but I’m giving it another go. Thunderbird has been disappointing lately, and I’m curious whether I can adopt the whole KDE PIM / KOrganizer suite. With any luck it’ll go smoothly and I can blog about that. Or it may fail spectacularly and I can try to find time to blog about that, we’ll see.
It’s been a while since I used KDE for any amount of time. If you have some KDE tips and tricks, please share!
Once again, time for the annual trek to Portland, Oregon for OSCON — perhaps for the last time!
Next year, OSCON is going to be in Austin, TX — which seems like a bit of a mistake to me. Portland and OSCON go together like milk and cookies.
If you’re going to be at OSCON, make sure to drop by Open Cloud Day on Tuesday, and come by the Red Hat booth to say hello!