The last set of videos from UDS have been posted! This includes my favorite part of UDS, the Lightning Talks. Remember we kick people off after five minutes so they’re kind of high stress. Apparently my crutch word is “ummm”. Aurelien did a Qt Creator demo, but also make sure you see Ryan Paul’s Qt demo, I talk about askubuntu.com with Robert Cartaino, Colin Watson does one on libpipeline. KDE daily builds, and what I call “The Rescue” by Dustin and the rest of the server team.
It can be a real bummer when contributions are ignored so I am glad we’re taking a more proactive stance on the problem and setting aside time for people to do it. You can find out more about the Sponsorship Process here.
Another important element to accepting gifts is Operation Cleansweep. Here’s the stats for the week:
Total bugs with patches: 2395 (+10)
Reviewed patches: 428 (+1)
Bugs with 'patch-needswork': 99 (-1)
Bugs with 'patch-forwarded-upstream': 192 (+5)
Bugs with 'patch-forwarded-debian': 63 (+1)
Bugs with 'indicator-application': 38 (0)
Bugs with 'patch-accepted-upstream': 60 (-1)
Bugs with 'patch-accepted-debian': 10 (0)
Bugs with 'patch-rejected-upstream': 19 (0)
Bugs with 'patch-rejected-debian': 3 (0)
Last updated: Sun, 21 Nov 2010 08:05:42 +0100
Plenty of work for many more people! If you want to dive in hit the Getting Involved page — Cleansweep is a good place to get started, you just need to know how to review code, you don’t have to worry about learning all the Ubuntu Developer-specific workflow to contribute!
Jono Lange has some ideas on how to make bugs easier to fix in Ubuntu.
Right now, when you run the script on your Ubuntu desktop, your cursor becomes a cross-hair. When you click on an application, start-hacking will tell you the source package that the application belongs to and where you can get the source (both Ubuntu source and latest upstream if available.)
There’s plenty of reviews out there on the new Boxee Box, here are my highlights:
The UI is too slow, the thumbnails take forever to refresh (it’s as if they’re not cached?)
It has played every thing I’ve thrown at it, it doesn’t break a sweat with 1080p at all (and all this over powerline ethernet!)
They updated the UI and kind of buried your local content behind the online content, which would be fine if most of the online content wasn’t a browser on your television that you might or might not be able to full screen.
Overall I think it’s great, it’s not quite awesome though. It’s a great value for $200 if you want to get your content to your TV.
Though the UI can be a bit frustrating I mostly care about presenting my media to me, and it does that very well even if it’s not as upfront to get my local media as I’d like. I have a Tivo, so I guess I am used to slow UX.
Hopefully the updates will fix the little details that are missing (little but annoting things like the subtitles always being on on every video and having to turn them off).
Given the quality of the online content I’ll probably throw XBMC on it when someone makes that possible and concentrate on that — the presentation of online content on this thing basically proves how little content providers care about their online presence, which is probably the most bummer part of the experience.
People have no idea (or care) where the problem comes from, they don’t care if it’s “upstream” or “distro”, they just want their software to work, and they don’t care who fixes it.
We’re not the only project to face this challenge.
This person thinks that we can bring pessulus/sabayon fixes to 7.04; a distro that is out of support, and even thought Scott Balneaves is now a contributing upstream; it doesn’t help this person who is stuck in some old version of Ubuntu, how do we help him?
So how do we fix this for plumbing? Those of us who have been around kind of know how this works. “I have a broadcom card, and it worked with foo distro, and then I upgraded, and it broke, so I moved to bar distro, and it worked; amazing, therefore bar distro is the win and foo is crap.”
My experience in this area was at Ohio Linux Fest. I hadn’t gone to a LUG meeting in a long time and I got into the elevator and ran into a guy from the LUG, after initial hellos he was like “Wow, what the /fuck/ happened with Lucid, worst release ever, I can’t even connect!”
I was in a serious state of anxiety. Here I was, pouring my heart into this damn thing. And not just coworkers at Canonical, but our immense community contributors, pouring our heart and souls into this release, and to be slapped in the face with failure, ouch! What was he upset about? Some stupid work around he applied 2 years ago to get his stupid Broadcom wireless card working. And on an upgrade it broke.
As it ends up we’ve reached a new level of what people expect.
My “linux geek correct” answer would have been “Hey bro, you have a broadcom card, it’s a saving throw; each distro release has different set of variables”. If you’re lucky you roll a natural 20 on a certain release of a distro — and if you’re lucky an upgrade is totally easy. I don’t even know what to say to the people to who own these realtek cards. People are still recommending “ndiswrapper” for these cards. That’s basically “Hey, I can’t fix your problem, so here’s a work around”. That’s not sustainable.
And as we know the people with broadcom cards don’t even get to roll the dice, they’re still waiting! It would be nice to reset the board and say “You’ve been hosed for years, but this time we’ll get it right.”
What a mess!
So in conclusion
I don’t think there’s something we can fix here. If someone rolls the ndis20 and gets a working wireless, then … yay? We can perhaps do a better job of explaining to users that they got lucky.
I don’t know much about about how Fedora does bug reports (or Ubuntu for that matter), but I am pretty sure if you have a Broadcom card that it will be a horrible piece of pain for you regardless of what distro you use. (Until the newer drivers are integrated, and even then there’s no guarantee that those will work with both your older distro AND your older hardware.)
Hey, I’ve heard this before.
Of course you have, Dan Williams has been preaching this for years. And, as it ends up, every distro has bugs. Every day I hear people “I am switching from foo to bar, they fix bugs!” … but in reality, we’re all in the same level of doom, as it stands today if you have a broadcom wireless card, you will be doomed; roll the dice. Depending on your video needs, ATI or NVIDIA? Roll the dice. Doomed.
If your hardware works with no workarounds, send the manufacturer a note. If it doesn’t work, then don’t buy it! If you want to make a difference, vote with your dollar!
UNIX is our generation’s fault; let’s not leave this burden with our children, let’s at least leave them a list of things they can fix.
Let’s spend more time rewarding hardware manufacturers who do the right thing than dogpiling manufactures that might not know how to support Linux.
Instead of flaming people who are frustrated that their computer doesn’t work maybe we should suck it up and deal with their bad attitude as long as it fixes the problem — it’s been proven over and over that people will do the right thing if they’re treated right.
As I mentioned in my last screencast; I prefer to have Banshee doing all my hard work for me. A great way to do this is via smart playlists. The problem is that they are very powerful and if you’re not overly clever off the top of your head you might feel stuck.
Luckily there are some handy smart playlists already included! In Banshee do Media -> New Smart Playlist
Go ahead and explore these, and come up with your own!
Here’s a bunch of summaries from the UDS Proceedings. Sorry they’re not more organized.
UPDATE: As many of you have pointed out, these are raw and in some cases don’t even make sense since they’re pasted in from people furiously typing into gobby documents. They’ll be polished as the week progresses.