preed's blah-blah-blahg

On Memorial Day, The ReedBot^TM and I went on a flight down to Oceano Airport for lunch.

Section 8.1.2.b, paragraphs 2, 3, 4, and 5 of the Airmen's Information Manual say, in part:

Either an upper respiratory infection, such as a cold or sore throat ... can produce enough congestion around the eustachian tube to make [pressure] equalization difficult. Consequently, the difference in pressure between the middle ear and aircraft cabin can build up to a level that will hold the eustachian tube closed, making equalization difficult if not impossible. The problem is commonly referred to as an "ear block." An ear block produces severe ear pain and loss of hearing that can last from several hours to several days. Rupture of the ear drum can occur in flight or after landing. Fluid can accumulate in the middle ear and become infected. An ear block is prevented by not flying with an upper respiratory infection or nasal allergic condition. ... If an ear block does not clear shortly after landing, a physician should be consulted.

Having just recovered from a nasty cold the Sunday morning before, that was (what some would call) the first mistake of the flight.

(Some might call spending two hours stuck in an airplane next to Reed the first mistake, but I assure you, he was a model passenger, and I'm proud to report I won't be invoking the "interference with a flight crew felony" clause—which applies to general aviation aircraft as well, thank god—the airlines always cite.)

Since I'm going on Day Five of not being able to hear out of my right ear, it may have turned out to be the worst mistake of the flight... but arguably, I didn't know it at the time.

I think I began to realize something was going to be wrong when we climbed through about 2,500 feet (ironically, over the Mozilla offices), and my ears didn't want to pop... and about 500 feet later, started to pop in the most excruciatingly painful way).

After about 5,000 feet, the popping was over, and I thought to myself "Well, alright. That was awful. Lesson learned. Let's get to Oceano." Enter an mostly uneventful (and beautiful) flight down there.

Until the descent. The the excruciating popping—in reverse—occurred. Oh my Jesus Lord... did I beg for forgiveness.

The lunch was good (clam chowder in a bread bowl!), but slightly rushed... and the refueling stop in San Luis Obispo-proper was uneventful.

The flight back was also uneventful and the sunset, beautiful.

On the descent into Palo Alto, though, my right ear refused to clear... and if you want to talk about horrible sinus pain... oh man.

But, a low approach at Moffett Airfield with the approach lights on almost made it all better.

Almost.

The full Flickr set—for those that want to nitpick about cloud clearance requirements— is here.

Overall, I had a really fun time. I hope the ReedBot did too.

And now, to play the waiting game with my hearing returning to my right ear (although, it did pop in a clearing-sort-of-way tonight, so that's encouraging...)

Posted by preed at 11:31 PM | Permalink | Comments (4)

You ever have one of those weeks where it feels like... like... you did a bunch of... stuff... but you didn't really get anything actually done?

Yeah, that was me this week.

I got assigned "light and airy" bugs like "Nightly updates broken - all apps, branches, platforms."

I also spent a lot of the week trying to turn:

Exhibit A

into...

Exhibit B

Now, if you don't know what those pictures mean, that's OK... because after having worked for most of a day fixing it, I really don't understand how it works, what I did to fix it, how I would fix it again... or what the pictures actually mean.

All I know is there's a bunch of red in the first picture... and there's a bunch of green in the second picture. And green is... good.

I think.

(Right?)

Anyway, in the end, that thing they say about it not being the destination, but the journey... just might be true.

Posted by preed at 7:35 PM | Permalink | Comments (1)

I know I have a bit of a... reputation for being up at weird hours. But lately, I've been falling into a work pattern that... has some good elements to it, but probably isn't sustainable.

The main cause of this has been cf.¹

Since he's working across the pond, he tends to be up and responding to email/IRC around 1 or 2 am and falling offline around noon to 1 pm PDT. (Astute readers will notice that this is an 11 hour day... which... now I feel really bad about some of the meetings we ask him to be at.)

He's been a really good sport about this and we got spoiled because he was here for a few weeks just a couple of weeks ago², so we typically just expect that he'll be able to be in meetings (because he was in them while he was here... and now he's "just a phone call away!")

I've always been a late(r) riser, so I've noticed that if I don't touch bases with Nick until I'm booted up, then he'd be parking his brain's drive heads for the day. I've found that to really be effective in helping him with things and doing reviews, I tend to need to stay up until 2 or 3 in the morning, when it's his morning, and try to be around earlier in the PDT day, to catch him at the end of his day.

On certain days (that tend to be coincident with the days I set up my coffeemaker's timer), this turns out to be workable; I'll go to bed around 4 and get up around 8 to the smell of fresh brewed coffee. It affords me the opportunity to catch up on IRC, email, and the fires that flared up overnight, and deal with them before coming into the office and trying to get something done.

But if I don't set up the coffeemaker, I find myself getting up at 10 or sometimes even 11, and not getting into the office until noon or sometimes even 1.

I don't like this for a number of reasons.³ The largest one is that it tends to fragment my work day too much, I think.

Anyway, this is relevant because the weekly build team meetings have traditionally been at 2 pm Pacific... and this turns out to be suboptimal, but workable for East Coast peeps. For Nick, it's positively hell.⁵

We've been trying to find a new time for it, but we've run into conflicts with other "random" meetings. ;-)

It looks like we've found a place that may work, but it's a 10 am meeting... and I've always hated any meetings before 11 am (what with getting up, getting into the office, and getting caffeinated, I tend to not be very useful before 11 am anyway).

The upshot is that I think I'm probably going to have to find a way to start shifting my days earlier on principle. I think this is going to be difficult for me because I've always been a night owl⁶, and going to bed at, say 10 or 11 pm, goes against at least fifteen years of going to bed at 2 am. Or later.

I think one of the hardest things, though, about going to bed before midnight is that it would make me feel like... too much of an adult. "Hey, I can still stay up until 3 am, and get up for a 7 am class, and be useful!!"

Except I can't.

Anyway, in the next couple of months, it'll be interesting to see how the meeting schedules shift... I'll also be curious to see if the rest of the build team begins to move "earlier" in the [Pacific Time] Day, since we've got Coop and Nick tugging that way for useful collaboration.

It's not like this is a new problem for the Mozilla Project, but I'll be curious to see how we, as a team of people who work closely together, end up solving it for ourselves.

And now, a friend from New York just IM'd me... so it's probably really time to get to bed now, so I can hide for an hour or two from a westward-marching sun.

___________________________
¹ I'm sorry Nick! I still love you though!
² Or so it feels like...
³ Not the least of which being it makes me feel like⁴ a huge deadbeat loser.
⁴ [other people are thinking I'm]
⁵ More than a build meeting already is, since he's currently working on the 2004/150twelve release.
⁶ And I've recently gotten back into hacking by candlelight... which I used to do all the time in college, but had forgotten how... awesome that is.

Posted by preed at 1:45 AM | Permalink | Comments (5)

AUS2, Mozilla's Automatic Update S{erver,ystem} is packing its bags!

rhelmer, morgamic, and oremj are furiously helping it stuff the update snippets into the U-Haul, as we prep to move it from OSL to the MPT colo. We've been planning to do this for some time now, but there's always been a release or firedrill or something else that prevented us from doing it.

We've got the AUS2's new diggs ready for it in San Jose, and we're starting testing now, before we have a housewarming party.

QA is helping us test on the client side¹, and with Cesar Oliveira's help², we're working on on the Build side, testing the server directly. If all goes well, we'll point aus2.m.o at the new installation next week, on Monday, May 21st.

To ease into it, we'll be removing all of the release updates for a couple of days while we test nightly updates. So on Monday and Tuesday of next week, please let us know if you experience nightly update problems.

If everything goes well, we'll re-add the release updates to AUS2 on Tuesday the 22nd. At that time, we'll also push out the 2.0.0.4rc3 release on the beta channels via the new AUS2 installation.

This will give AUS2 a full week of move-in time before we need to push any updates for a full release.

If there are any questions or you experience issues with updates next week, please file a bug, and let us know in #build, so we can take a look at it.

The AUS2 migration team—and millions of Firefox, Thunderbird, and Sunbird users—thank you in advance.

______________________
¹ If you're interested in helping, pop into #qa on IRC and ask about it...
² Ok, ok... I confess... I had to beg Shaver to let us grab some of Cesar's awesomeness to help

Posted by preed at 9:19 PM | Permalink

I swear... the amorphous blob of people, patches, and passion that is Mozilla never stops churning.

I leave for a long-weekend-mini-vacation¹, and the world completely changes: some taggable, hour-long YouTube video has everyone talking², my desk gets moved³, a friend gets engaged, and Mozilla is killing XUL Runner.

Except... we aren't. Not really.

Looking over Planet, there's a lot of "platform" discussions going on. I've seen Mark Pilgrim's "silly season" post referenced a number of times. To be sure, it's a great post (and relevant, too), but one Mark's other posts, linked from "silly season" really resonated with me: Freedom-0.

In that post, Pilgrim writes:

WordPress is Free Software. Its rules will never change. In the event that the WordPress community disbands and development stops, a new community can form around the orphaned code. It's happened once already. In the extremely unlikely event that every single contributor (including every contributor to the original b2) agrees to relicense the code under a more restrictive license, I can still fork the current GPL-licensed code and start a new community around it. There is always a path forward. There are no dead ends.

I could go on about how I was confused, because it didn't seem like I was reading the same post everyone else was reading.

But with shaver and Benjamin's clarifications today, I don't think I need to say anymore.⁴

I will, however, say: that's what's wonderful about the freedom of open source: the fact that those interested in a project can build up a community out of interested developers, can build a project out of a CVS repository/IRC server/mailing lists, and can build a product out of a bunch of bits.

I personally have always found XULRunner to be a very interesting project. I always thought it was neat that you could download this little bundle of binary bits, write up some JS and XUL, connect it with some XPCOM components, and get an entirely new app out of it all. And all the stuff we expect out of current (non-browser) applications—HTML rendering, network connectivity, platform independent I/O, an update mechanism—were just there.

I just wanted to add: count me among the members of the Mozilla Community that are interested in XULRunner and seeing it succeed.⁶ Materially, I'd love to contribute the time to make sure that XULRunner has the build (and eventually release) resources it needs.

As shaver notes, "As XULRunner itself is about 1000 lines of code that differs from Firefox, the bulk of the work is likely to be in build, packaging, update and other "meta" areas, I suspect." I suspect he's right, most certainly because Firefox really is built on top of XULRunner, even if that separation isn't as clear as we like, and it's not packaged entirely how we'd like. It's not like we could have Firefox release, but a so-completely-broken XULRunner build, that XR was unusable.

(I was going to run out and start setting up trunk Tinderboxen for XULRunner but then I noticed "Oh right... we already have those.")

So I guess others interested in XULRunner in the XULRunner Community will have to tell me how, as an individual contributor, I can best and most effectively be of assistance.

______________________
¹ I had the best two hour massage...
² I say this not to sound dismissive; however in the interest of full disclosure, I must admit that I started drinking scotch about fifteen minutes in, and the more I drank, the more it all made sense.
³ Admittedly, to a nicer location
⁴ Except to point out that we've been faced with this [perceived?] specter before, and not only did the "nightmare scenarios" never come to pass, even if they had, it wouldn't have mattered.^5
5 Ok, I'm done. Really.
⁶ Whatever we decide that means.

Posted by preed at 10:32 PM | Permalink | Comments (2)

Joel—yes, that Joel—made a couple of blog posts recently reminding people that today is Mother's day.

(Tangential aside: Hi Mom! I didn't turn out to be a famous movie star... or a wünderkind athlete... or a renowned writer... or a Nobel prize-winning scientist... but this blog [seemingly?] [and inexplicably?] gets syndicated all over the place, so if you Google for "preed" and "mother's day love" in like... a couple of weeks, this post should show up... and since I can't dedicate anything to you, like those other professions tend to lend themselves to, hopefully seeing those Google search results will remind you of how much I love you, not just today, but everyday!)

What I thought particularly interesting about both of his reminders was

a. He's offering a free day usage of his company's Copilot software today¹, so us tech-savvy children can help our Mothers update their vulnerability pockmarked Windows PCs.

and b. in both posts, he mentions installing Firefox on her computer, so she can have a cleaner, faster, more customizable, and (most importantly) safer experience on the Web.

I happen to be in Colorado right now, so I can accomplish those things with my Mom at the kitchen table²... but if you don't have the luxury of being within fifty feet of your Mother today, here's a chance to tidy up her PC a bit and make sure she stays safe on the Web.

So if you haven't already, take a few minutes to introduce your Mom to Firefox. She'll thank you for it, even if she doesn't entirely understand why.³

(My mom notes every time I see her that every few weeks, she's pleasantly reminded of me when she gets the "It's time to update Firefox" popup. For most of our users, it's an annoying⁴ distraction to using the web, but for her, it's like her son⁵ is giving her a hug from three states away.)

________________________
¹ And on Father's Day, too
² Actually, since Mom already uses Firefox (of course!), the big task for today is teaching her how to use flickr, since she got a digital camera for Christmas, but all the pictures she tells me about having supposedly taken have seemingly gone into a black hole!
³ Explaining Firefox extensions to my mother took awhile, but at the end of the conversation, she was very appreciative of shaver, morgamic, and everyone else's work on AMO3!
⁴ but necessary
⁵ Even though rhelmer and cf push releases as often as I do...^6
6 rhelmer and cf: please promise to be nice while giving my mother AUS2-hugs

Posted by preed at 11:05 PM | Permalink