is a joyous,
is the realization
that I had forgotten.
Don't say I never gave you nothing.
I've had time to review more of the FUDCon 11 videos, specifically the KVM, Moksha, and Desktop videos. The KVM and Moksha videos pretty much only had me saying "neat", not that I thought they were boring, just that I saw nothing to comment further on; I think both are great ideas and I'm sure that both are only at the very beginning of their potential. This then leaves the Desktop video. But I'd like to digress before I give my thoughts about it.
I first heard of Linux through a classmate, via RHL 5.1. I dabbled with it through 7.2, then drifted away. I'm not sure what caused the drift. I think it was games. Anyway, I used Windows up until Windows 2000, when I decided to take a look at this new-fangled thing called "Fedora". I set up my system as dual-boot between Windows 2000 and Fedora Core 2. I didn't boot it into FC2 very much, simply because I already had Windows 2000 set up how I liked it, and to be completely honest, Windows 2000 wasn't terribly bad. In fact, I found that it suited my needs as a desktop well. The only thing I missed was multiple workspaces.
But blah blah blah, enough of that. How does that relate to the Desktop video? Long story short, I saw the GNOME 3.0 demo, and I don't get it. How does any of that help me get things done? Why should I worry about managing the number of workspaces I have? I'm not going to say anything about the launcher application selection since I'm sure it will go through one or more revisions before they come up with a sane scheme.
"Okay big talker, how do you think it should be done?" Well, we'll get to that in a second. First I want to show you an experiment that I'm undertaking, working within the confines of the existing technology:
As you can see, it's very similar to the GNOME default with a few significant changes:
This mostly works, except for a few issues with (auto)mounting, and with the clock applet not playing nice with the right panel.
What I envision though, goes even further:
A number of changes are in place here. The visible ones:
Of course, there are also a number of invisible differences as well:
So there you have it. I'm sure there's a few things I missed in there. As always, comments and criticism are welcome.
I just finished watching the XO/RPM FUDCon video, and here are my thoughts, in no particular order:
Comments and criticism welcome.
Every second is a new year; a chance for new opportunities and new successes.
And just so that this post doesn't become completely touchy-feely, here you go.
Whew! I finally got Python 2.6 into Rawhide. I'd like to thank the following people for their invaluable help:
And of course, every Fedora Contributor that maintains or uses a package in Fedora that uses Python in one fashion or another, since your kind assistance will be needed in order to complete the integration of this new version.
blah blah normal Fedora 10 on the XO on a USB drive. Here's how:
You may be able to skip the kernel-swapping step by passing i586 at the install boot prompt. I did not try this.
Preparations are now underway to get Python 2.6 into Fedora. Watch the skies in the next few days.
I had originally agreed to give a presentation about packaging a part of the Fedora Classroom series. As time passed I realized 2 things:
So instead of talking about packaging, I'm going to be talking about packages. How to identify them, how to use them, and so on. The talk will be a little more disjoint due to the running around that needs to be done, but it's better than me just typing the article out in IRC.
So you'll still have to read the Building Packages Guide if you want to learn about packaging (and I urge you to read it), but I'll be more than happy to answer any questions you have about it during or after the session, with the exceptions of "why is it still a draft" and "when will you finish it" (because, and whenever :P ).
Actually, applications. Lots of them. Use as many varied core Windows technologies as you can. COM, ActiveX, DirectX, you name it.
Get people to like and use your applications. Lots of people. People with money. People with power.
And then promptly ignore them. .NET? Who cares. WPF? Passing fad. Force Microsoft to spend billions of dollars to keep your apps and their 20-year old API calls working. The building pile of legacy in their codebase will compound and eventually overwhelm them.