Thanks, I appreciate that. :)

I could definitely have chosen "flexible" or "nimble" or some other random adjective. It didn't quite just pop into my mind, though -- I'm definitely familiar with the agile programming movement and have seen it in action in very positive ways. (I'm sure it can go horribly wrong, just like anything.) So, the title isn't completely an accident. I do want to evoke some of the agile manifesto: focus on interactions and individuals, responsiveness in the face of change, and so on. In general, I think we need to make some room for "worse is better" underneath the Fedora umbrella (while still keeping the core to a "the right thing" model) -- that's not agile in specific but is part of the same vein from which it developed.

Question all you like. I don't mind. However, I'd really prefer questions to the trolling. *

Which, given all the posts, by tibit, I have to assume is the case. If I were to take it seriously, though, I would say that probably what's happened is that much of the concrete part of the proposal uses labels which are unlikely to be familiar to someone not active in Fedora development (Fedora Formulas, Software Collections) without explaining them. You might know OpenShift, but "OpenShift Gears, decoupled" just sounds like gibberish. Even the term "base design" sounds vague but actually relates to a specific ongoing effort (http://sched.co/11El9OZ).

I didn't really think about how this would read to an outside audience, because Fedora developers are the intended audience, and because this is a presentation, not an in-depth white paper.

(* I know, I know, am I new here or what?)

I have to say, I'm not entirely sure you've read this proposal. Or maybe there is something that could be more clear? The audience here is really Fedora developers, so it's likely that some things aren't immediately apparent if you're more removed from that. Overall, this is a proposal for significantly less baggage.

Well, Fedora isn't ever going to be that completely safe kind of boring. For that, we have our downstream distributions, which are awesomely boring in all the way you describe. Fedora isn't supposed to be that, and is supposed to be in place where we are generating excitement, whether that's at the OS core or further out. But in general, the idea here is to separate out that "no frills" core from the language stacks and other areas where "be up to date" and "make available the exact things we need" are the demands. Then, we can address these needs differently.

If you're just interested in the base, awesome: we will put that together for you in a well-defined way and let you do whatever you want on top of that.

Having the separate ring 1 lets us focus on making that a coherent base which can be enhanced in an cohesive way which doesn't break everything for users as we go from release to release.

Good, because those two things are exactly what this is all about.

As a general rule of thumb, if you need something lightweight, SQLite is the way to go. If you need something more powerful or sophisticated than that, PostgreSQL.

MySQL and spinoffs all occupy an uncomfortable middle ground. 99% of the small web sites which are built around MySQL don't need it.

Actually, this apparently comes from Dell's acquisition of Wyse. That is, these guys: http://upload.wikimedia.org/wikipedia/commons/thumb/7/72/WyseTerminal100.jpg/220px-WyseTerminal100.jpg -- the people who *did* do this decades ago. So, I guess, fair enough.

In Massachusetts, it's the law. http://www.mass.gov/courts/jury/compensa.htm#INFORMATION%20FOR%20EMPLOYERS:%20RIGHTS%20AND%20OBLIGATIONS:

I don't know if kids today remember, but Loki Games was one of the first commercial plays for big name games on Linux. Ended in tragic business troubles and financial doom.

It warms my heart to see that Sam Lantinga is still working on SDL.

That is all.

"If available" is the catch here. Comcast has a near-monopoly on broadband service in many parts of the country. Some places have the luxury of a second cable provider like RSN, but mostly, the other choice is more expensive and much slower DSL. Some places have Verizon FiOS, but apparently they're pulling back on that as well.

Title says implies that the judge made the statement about the code being trivial. The judge makes no such claim -- instead, he says that a previous Google witness made that claim. This is a world of difference!

And there's even King's Lynn on the real-world map roughly where King's Landing would be.

Oh, sheesh; yeah. The Lannisters come from Lancaster. (I mean, on the map; not just in similar names.)

Westeros is transparently (if not particularly faithfully) based on a fantastic reinterpretation of Britain, right down to the the Wall and the . And all the knights and chivalery (and non-chivalery) and so on are clearly Arthurian legend, which is unquestionably British even if it owes a big debt to France — which, speaking of, is of course right across the "narrow sea". Middle Earth is less literal with the geography, but Tolkien has said (were it not already obvious!) that the Shire is rural Britain in spirit, so of course the hobbits speak with the appropriate accent.

Spoiler alert! Sheesh!

This is some guy with a website, with a dull and poorly produced video telling you to buy stuff. I stopped when I got to the part where it says that most people buy smaller TVs than they "need". N-E-E-D.

Now, if he said "people buy smaller TVs than would be AWESOME", okay, fine. But this is basically crass consumerism pumped up by guy who isn't an "industry expert" but rather someone who worked for a crappy rah-rah-buy-stuff computer magazine for 20 years and is trying to trade on that to get some money. That's not wrong in itself, but it sure does translate to being a slashvertisement here.

Two thumbs down.