Met some really interesting people today at MIT. Hopefully they'll find me interesting when I talk to them in eight hours.
Met some really interesting people today at MIT. Hopefully they'll find me interesting when I talk to them in eight hours.
Brutal but fairly productive 10 hour meeting today. Oy.
Spent a tiny portion of the weekend playing with xchat-gnome. Something lots of people have talked about, someone finally went ahead and did. Very cool.
<DV> someone blogs please, my Internet TV has been showing the same program for the last 10 hours or so ...
Just saw a brilliant performance of Tom Stoppard's Rosencrantz and Guildenstern Are Dead, on a set inspired by Escher, with a smart 'icing' of The Clash as everyone left the theater. Everyone in Boston should go see it. And if you're a Lessig fan, ponder the cultural sampling going on all over the place only between acts, for your own sanity.
I want to clarify I don't have any inside information regarding Red Hat or Sun's plans, and Novell's are still up in the air. But given Glynn's recent comments, FC2's use of 2.6, and Novell's obvious desire to ship a product to compete with JDS and RHEL WS at some point, I can see the possibility of the stars aligning in such a way that all the large corporate players decide the risks of 2.8 are too great, and settling for doing their own branches of 2.6, instead of actually trying to resolve the risks in 2.8. Seems like that would be a very odd, sort of wasteful outcome (to me.)
On a completely unrelated note, I've spent a lot of time and typing over the past couple of years complaining about bugzilla code quality and sql table design. Bugzilla 2.16 is like night and day. I just made some of our duplicate reports go from the slowest things in the world to rocking fast, allowing me to nuke some static html generation in the meantime. And it took me all of a few minutes, and the SQL queries got less complicated. Thanks to everyone who has contributed to bugzilla over the years- without it there truly could not be a modern, active QA movement within free software.
deekayen says:
I submit to you that people hacking on Gnome off in their own corners is what brings the coolest, new things to Gnome. The way I see it, the atmosphere behind thinking to create a "functional, stable release" is more focused on current features. Gnome needs both free spirits and "stabilizer" people...
Just to clarify, I don't think that people hacking off in their own corner on cool new features and such is a bad thing- this is often how innovation happens, and we need more of that, not less.
What I was worrying about (sorry I wasn't clear) was when an entire company goes off and stabilizes/bugfixes/backports on their own fork of a stable/deadish branch. [Something that Ximian has been quite guilty of in the past.] Most of those fixes end up being lost to the trunk, and the companies end up wasting a lot of time backporting that could have been more productively spent stabilizing the trunk. And the companies throw away the QA benefits of sticking closer to the trunk as well. The community could benefit a lot from that effort going into trunk, I think, and so could the companies, if it was structured right- they'd get more functionality, faster, with better/broader QA and less waste.
the blog tool needs a 'do what I mean, stupid' option.
Just read Havoc's post, and I do think he has it mostly right- GNOME does do it better than most. That said, some comments on his, Benjamin's, and Jeff's posts:
Anyway, that's one morning's ravings. NB: I dreamed about a Novell employee who snapped and shot all her co-workers in the non-existent Minneapolis office last night. It was scary as hell, and may have affected my mindset this morning :)
[Later] One other thing about Havoc's post- I don't think the thrust of my usability post was about communication, but rather about investment- it's not sufficient in my mind for the usability community (regardless of who employs them) to say 'here is what we're doing'; it must also educate about how it is being done so that others in the community can learn and add on. I've tried to do this with bugsquad; the evo team failed to do this for a long time but is now more actively trying to promote this kind of thinking, which is awesome.
I'd like this entry to be blank, but advo's rss generator appears to bork if you have a blank diary entry. And no one actually reads this via advo anyway. ;)
Had a decently productive day today- triumphed over bug 139195 (which I frankly didn't expect to do- thanks to the people who helped reproduce it) and otherwise did some minor cleanups.
Misirlou cooked up a nice, but scary, query for bugs with patches. There are over 1300 of them. 1300. Yeek. I'm hoping to do some cleanup on this list, and produce some useful queries maintainers can use to help clean up their own mess, later tonight.
It's nearly spring- had a very nice sandwich for lunch, while sitting on a bench outside. Look forward to doing more of that at some point soon.
[Later] Whipped this up for maintainers to check on patch statuses, but it still sucks- if you mark a bug needs-work, it'll still show up in that query. Bugzilla code still scares me sometimes :) Still, though, it can give you a rough idea of the number of patches in the system for you- probably some scary large numbers in there for some maintainers.
You know you're too obsessed in IP when you go to a perfectly wonderful Vienna Teng concert and spend half of it thinking about street performer protocol and the RIAA. Oh, and The Animators rocked too.
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!