March 2004 Archives

fc2t2

| 5 Comments

Today I installed Fedora Core 2 Test 2. The install went mostly OK with only one minor glitch in picking packages.

After install, I experienced consistent crashes trying to adjust the clock applet preferences and the iTunes knockoff crashed when I attempted to play some music it had imported from one of my audio CDs. I had some difficulties mounting and unmounting my USB keychain flash memory device but that's mostly resolved.

OK, that's the bad news. The good news is that it's fast. It feels considerably faster than FC1. I also had very little difficulty adding a few more applications and using those. I got Mozilla and Firefox installed without any problems, even got JRE 1.5 beta and RealPlayer both installed without any difficulty.

Now all I really need is driver support for my Broadcom integrated wireless and a couple of crash bug fixes and I'll be ready to move back to linux as my primary OS.

Have any of you tried FC2T2? What do you think so far?

Today is BugDay! and the beginning of CrashWeek. Our goal is to go through all of the Bugzilla reports of crasher bugs (about 1500 total) and identify all of the reproducible crashers and add a stacktrace or talkback ID to each of the reproducible ones. If you have a debug build, you can help by adding stacktraces to crasher bugs. If you don't have a debug build, you can use one of our builds with TalkBack and when you crash, send in the crash report and add the talkback ID to the bug with a comment about which build you used and which OS. If you add a talkback ID to a bug report, please add the keyword "talkbackid" so that we can easily find those bugs to attach talkback stack traces. While you're going through these lists, please resolve as Worksforme any bugs that cannot be reproduced and ensure that any bugs which do crash are Confirmed (status set to New) and have the crash keyword.

To help out with BugDay and CrashWeek, join us on the #mozillazine channel on irc.mozilla.org. You can either query Bugzilla yourself or get your buglists from the CrashWeek page.

bugday and crashweek

| 5 Comments

BugDay™ ;-) and CrashWeek™ ;-)

In preparation for making the 1.7 branch the next "long-lived" stable branch, I'm organizing a week-long effort to scour Bugzilla for crash bug reports and get them all cleaned up and ready for developer action. We have hundreds of reported crashes in Bugzilla but the majority of them are difficult or impossible to reproduce.

The first step will be identifying the reproducible crashers and make sure they have clear steps to reproduce and/or testcases. Once we've done that, we'd like to get stack traces attached to each of those reports. With stack traces, we should be able to resolve another batch as duplicates of other known crashers. There are a couple of ways to get stack traces. If you build yourself, consider making a debug build to help out. If you don't build, there are a few Mozilla (and Firefox) builds that contain TalkBack. TalkBack is simple crash reporting utility that will generate crash data, including a stack trace, and report that back to the Mozilla Foundation where I can retrieve it and attach it to a bug report. The Mozilla 1.7 Beta release contains TalkBack and the latest nightly Firefox GTK2+XFT builds also contain TalkBack.

Until we have a stack trace it's often difficult to tell whether two similar sounding crash reports are actually the same. Once we've resolved all the unreproducible crash bugs and attached stack traces to all the reproducible ones, we'll be making another pass to compare stack traces and resolve out duplicate crashers. This may also help us to identify which of the Mozilla crashers are most visible -- with duplicate reports acting as a crude visibility metric.

After we've got all these reports resolved or confirmed with clear steps to reproduce and stack traces, we can hand them off to engineers and along with the aggregate TalkBack data from thousands of Mozilla users, we should be able to get a clear picture of our most high-profile crashers so we can tackle the biggest problems first.

So join us this Tuesday, and all week long for BugDay and CrashWeek. Together we can make Mozilla 1.7, and Camino, Firefox, and Thunderbird releases from the 1.7 branch, the most stable Mozilla releases ever. BugDay is a weekly IRC event which takes place in #mozillazine on the server irc.mozilla.org. For you chatZilla users, consider using chatZilla in an alternate Mozilla app (ex. SeaMonkey if you're a Firefox user and Firefox if you're a SeaMonkey users) so that when you test these crash bugs, you don't take down your IRC client.

google gets personal

| 2 Comments

Google has just pushed a redesign that shouldn't be a dramatic change for most users (though I'm not terribly thrilled with the new look). What I am thrilled about is this new Google Personalized Web Search. The basic idea is that you tell Google what your interests are and then you can control how much influence those interests have on the ordering of the Google search results. This has some real potential. I'd love to see an "upload bookmarks, browser history, or blogroll" mechanism added to the personalization section that allowed me to add some weight to sites I already consider good resources.

luna from the patio

| 6 Comments

I'd hoped to get to some Ask Asa answers this evening but I couldn't pull myself inside and now I'm too tired :) Maybe tomorrow. Here's what had me distracted:
a photo I took of the moon this evening
I may try to take some Jupiter photos tomorrow night if it's clear and dark but with my tiny scope, they won't be particularly dramatic.

step outside

| 2 Comments

If you're not chained to your computer (heck, even if you are,) take a few minutes to step outside and look up at the sky. Tonight you should be able to see six or 7 (counting Earth) of our solar system's sexiest bodies.

Look west and you should see a very bright "star". That's the planet Venus. If you've got clear skies and it's dark enough, look down from Venus to just above the horizon, slightly north of west, and you may be able to make out faint Mercury. Looking back up and past Venus, about 1/4th of the distance between Venus and the Moon, you should be able to pick out tiny red Mars. Continuing up in the sky to just just below the Moon lies Saturn. If you continue to follow the ecliptic (that arc you can trace from Mercury to Venus to Saturn) past the Moon towards the south east, that other very bright "star" is Jupiter.

Even in light-polluted skies, you should be able to make out Venus, Mars, the Moon, Saturn, and Jupiter so don't miss this opportunity. Add in Earth, and you're looking at six of our solar system's most glorius gems.

If you've got a pair of binoculars, the moon is a nice target this evening and if you've got even a small telescope, Venus, Saturn, and Jupiter are all worth a look. Saturn's tilt is particularly nice right now with a good view of the gas giant's rings. You'll probably be disappointed in Mars so spend your time on the waning Venus (which looks about as full as the Moon,) Saturn, and Jupiter. If you've got dark skies, you might also want to take a look at the Pleiades, sitting between Mars and Venus.

Do go out and take a look, especially if you don't have a telescope and don't normally pay much attention to our wonderful skies.

ask away

| 9 Comments

I've got a couple of questions left over from previous insallments and a one or two new ones that have popped up in the comments since last week. If you've got questions for Ask Asa, get 'em in today and I'll try to have answers posted in the next day or so.

house finch rainbow

Male House Finches display extreme color variation, ranging from pale yellow to bright red. The depth of red coloring in each male depends on the amount of carotenoid pigments in the bird�s food sources during the molting period. Studies show that females prefer the brightest and reddest males; presumably the hue and intensity of color are indications of the male's fitness. (via Cornell Lab of Ornithology

We've had at least 3 house finch guests in the back yard this last week but one stands out. He's spent more time here than the others and it's his (happy) song that wakes me up most mornings. More than his song, though, is the beautiful golden orange color of his head band, chin, and throat that caught my attention. In the sunlight, it's the exact color of our california poppies.

I know the females are supposed to go for the redder males, but I find it hard to believe that they'd take to one of the drab, uninspired red guys when this glowing and regal, golden orange male steps into the sunlight and puts his song on for them.

Maybe I'll take some photographs tomorrow and post them here for you all to see.

crash week

| 4 Comments

Next week I'm going to be working to organize a week long bug cleanup effort for reported crashers. We have many hundreds of crashers reported in Bugzilla which need confirmation or resolving. With Talkback in 1.7 beta, we can easily get stack traces for reproducible crashers and that should help us resolve quite a few duplicate reports. Starting with Tuesday's BugDay, and going through the end of the week, I'll be available to help newbies and veterans alike as we slog through hundreds of bug reports and try to get a real fix on known stability problems in advance of 1.7 branching. If you're interested in being a part of this effort and need help getting started, join us on Tuesday in #mozillazine on irc.mozilla.org.

we've got a troll

| 4 Comments

In case any of you were wondering about those obscene and insulting comments that briefly appeared in a couple of the recent posts here, that's some guy named Alex pretending to be me (and other?) commenters. I'm working with mozillaZine to get the guy banned (IP banning is a bit tricky with how they have MT set up) so in the mean time, if you see a comment from one of the regulars here that just doesn't seem to fit (especially if it's full of obscenities or insults towards other regulars here) then just ignore it. Thanks for your patience and we should have this little annoyance cleared up soon.

the power of about:config

| 4 Comments

Do you just hate those sites (like mine) that disable toolbars in pop-up windows? It's easy to fix. Just type about:config into the address bar and hit enter. Then type dom.disable_window_open into the about:config filter field to trim the list down to the window_open features you'd like to block. Right-click on any of the items and select modify from the context menu (or double-click on the entry). Just replace the false value with a true value and you're all set.

I'm sure that this has been thought of before but I'll toss it out anyway. Why don't we capture additional meta data when we bookmark a page? This data could be extremely useful and it surely isn't difficult to acquire and store. I really, really want to see bookmarks/history get smarter. I can envision auto-categorization based on meta data, page title, neighboring history entries, all kinds of cool stuff. Why isn't a bookmark automatically created if I visit a site some threshold number of times? Why aren't bookmark "views" avaiable that display common browsing patterns, related sites, etc.? We could do so much better here.

And while I'm on the topic of grabbing meta data with bookmarks, why not grab link rel=alternate URLs too? Wouldn't it be nice to have the choice for any of your bookmarks (for sites that supported it) to open the HTML page or to open the RSS feed in something like RSS Reader Panel or Forumzilla?

And while I'm on the topic of viewing content my way, can someone please implement a Mozilla extension to CSS that allows me to select on a unique identifier for a web page (like, say, the URL)? My userContent.css user style sheet is getting really painful to maintain with all it's cluttered and hacky attempts to select on just the right HTML element to apply a style to one site but not another. If I could just specify in the style sheet that this rule or that rule only applied to one site, things would get a lot easier :-)

And while I'm on the subject of making things easier, if you're using IE and you want to make the web easier, Get Firefox!

ouch

| 45 Comments

Today I spent a big piece of the day trying to work in winIE 6. Why? Well, because it's been a while and it seemed like it might be fun and I thought it would be a good idea to remind myself of all the ways that the competition is still better. I put a few minutes into getting some basic bookmarks set up and putting shortcuts on my desktop and toolbars and then I dove into BugDay.

Man, what a pain. I mean, seriously! How can anyone use that POS? Not only did I not find any ways in which it was better than Firefox, it failed to even meet many the most basic of my needs. And I'm not just talking about geek features. I'm talking about being able to open up "popular" web pages and read without having to navigate a labyrinth of popups and in-content ads (it's really gotten a lot worse in the last year while I've been oblivious to the change because of ad-blocking userContent.css). I'm talking about being able to open a link in the background (it doesn't even have to be a tab, guys. c'mon, you can do better than this). I'm talking about basic usability issues that IE just falls down on Create a shortcut? How is that different enough from adding a favorite and used enough that it needs it's own context menu item? Is alt+v, x, l, really as good as it gets for jacking font sizes up one notch? And why doesn't that seem to work on about half the sites I tried? And please tell me they've got some better mechanism for organizing favorites than that lame little window.

I could go on but let me just cut to the end. The entire experience sucked. It was really a painful experience. Are IE users just numb or do they avoid the Web because of this pain? How do they cope?

This is a case where ignorance can't possibly be bliss.

I thought for sure that Microsoft would have turned up the dial some since my last major encounter (IE 5). If you are using something else and thinking about giving IE another shot, don't bother. If you are in IE pain and looking for some relief, get Mozilla Firefox -- it really does go to eleven!

"opportunity hits the beach"

| 1 Comment

The pre-show caption at NASA TV is titled "Opportunity Hits The Beach". See the previous posting for the view of Opportunity as she drove out of the crater onto the broad flat plains (a beach?). I'll try to get notes posted as soon as the briefing is concluded.

I was right. Bedrock formed in a shallow salty sea. Notes when it's completed.

(I had lots of connection problems and I haven't done any editing so these are just my raw notes, not particularly accurate.)

Latest from Opportunity operating in Meridiani Planum.

Opening remarks by Sean O'Keefe:

Good afternoon. Delighted to be here to announce latest scientific findings that prove that the spirit of exploration and discovery are alive and well. We're back on Mars. Great to be there and to know that human exploration is soon to follow. Exciting time for NASA. 9 billion hits since Spirit landed. 18,000 photographs, 20 Gigabits of data, 250,000 measurements. Ongoing mission demonstrates that when you dare to ask questions you may receive profound answers. Latest returns of science have profound implications for future exploration. Opportunity surveying and roving an area not much larger than the size of this auditorium but a most opportune and incredible location. It is my pleasure to introduce the team to you. Ed Weiller will set the stage and introduce the scientists to you.

Ed Weiller: Good a afternoon. About two and a half months ago we were having a press conference about the 6 minutes of hell during the landing. A lot of water under the bridge since that. Three weeks ago we were here on this stage with first direct evidence of rocks modified, altered by water. You had a lot of questions then. We couldn't answer those questions. About a week after that the data was gathering and the team was coming to some conclusions. Since the conclusions were very profound we though we would go through a peer review process with outside scientists. We completed that. It appears that the rocks at Meridiani were not just altered by water but were created in water, perhaps a shallow salty sea. If you have an interest in looking for fossils on Mars, this is the place you want to go.

Steve Squyres: Here we are again :) Three weeks ago we provided evidence that the rocks had water seep slowly through them changing them. Since then we've found strong evidence that the rocks were sediments laid down in water. The evidence for this that Opportunity is now parked on the shoreline of what was once a salty sea on Mars. When we looked with our X-ray spectrometer, we found Bromine. Not only there but the amount varied tremendously in different ares of the rock. Varied by a factor of 10 from place to place. Characteristic of rocks formed by evaporation of seawater. That was exciting but not enough so we went looking for crossbeds. If you have motionless water or air settling you get flat horizontal layers. Hard to tell what the fluid is. If the fluid is moving, you get crossbeds preserved in the rocks. If the fluid is moving then the nature of the cross beds is distinct. Formed in air or formed in water look different. John worked very hard to formulate a plan to get at this evidence. With our panoramic camera we saw rocks that looked like they had cross bedding. We designed these rovers to make them as flexible and capable as we could because no way to know in advance what we'd find. We used that flexibility. We drove to rocks and used the Microscopic Imager to make large mosaics (152 images at "Last Chance") Those mosaics with their very high resolution were able to capture the cross beds. Fantastic piece of work by the engineers. Still a lot that we don't know. We don't know how laterally extensive the water was, how long it was there, how common it is on Mars. We have the capability to find out. Endeavor crater 700 meters away. We're gonna traverse across the plains and look in Endeavor crater. in 2005 NASA's gonna fly an orbiter that can look to see if these salts are distributed globally? We have the capability to chase this problem. Why is this important? This was a habitable environment on Mars, a shallow sea, a salt flat. We have an environment that could have supported life. We have an environment that can trap and preserve evidence of what was in the water. A great place to go for a sample return mission.

John Grotsinger: Science was very different than earlier. It's very visual, about texture and morphology. I never expected to be looking at this. I want to thank all the guys in the Pancam and MI teams. Morphology. Problem was layering. If you just get settling of grains from gravity you get flat layers. In cross section you see parallel lines which don't give us a fix on what caused them. When they organize in a current, they form mounds and avalanche and produces layering at an angle. This is called cross bedding. I'd like to take you on a tour to show you what it looks like. This image shows lamination about 1mm scale thick. Notice how parallel these layers are. We're going to see layers that aren't so parallel. This movie shows water flowing over a be of sand and the bed organizing itself into these waves avalanching and creating crossbedding. This can only occur beneath water. In the next video is a simulation showing how ripples form in water. This image is at a rock called "Last Chance" We weren't sure if as we got closer we'd still see this crossbedding. Arrow in the middle shows these "smiles" curving up in a Pancam image. The lower arrow there shows lines inclined off to the right. Next image shows MI picture mosaic with no parallel lines. You can see these "smiles" opening upwards. Blue lines represent boundaries between successive ripples. Black lines define the individual avalanches. The next slide is at "The Dells". There are no parallels here. Everything has the open concave geometries. Again the blue lines show successive events. You can see one very well defined "smile" there too. We feel confident that this adds up to a story of ripples from water with gentle flows, maybe 1 mph.

Dave Rubin: When John and Jim first sent me some of the images we just looked at I was astonished. First, there on Mars were sedimentary structures just like we see on earth. Some of the structures were wind-blown but not talking about those today. Others looked like formed in water. Here is an example of ripples from the Colorado river showing same trough shaped smiles. You don't have to have a river that large to make these. They can form in a little creek. Doesn't take a long time but it does require flowing water. I was really surprised to hear that the Mars team has the same task that geologists do on Earth. I started thinking, where on Earth could we go to find a similar environment. I looked through my slide collection on Sunday and pulled out a couple of slides. This one shows an inter-dune basin in China. The white is a crust of salt. It's a very dry place. If you dig down you'll find soft wet sandy salty sediment. The dunes you can see contain clay pellets cemented by salt. This has some of the aspects of what we saw in the rocks that John showed. I think the team's explanation is the best possible explanation but if I was gonna come up with a counter example it would involve small windblown bedforms. Best way to keep them small would be to have water just below the surface so even in the best counter example I can come up with would have water involved.

Jim Garvin: To put in context, rocks make us smile. I think there are a couple of messages that are a hallmark of our program. We are living science driven exploration as we speak. We never would have believed this. We're sitting here, 50 days into the mission with results that have real impact. The value of microscopic imaging, we knew it would be of great potential. That new vantage point has opened our eyes, a hallmark of our program. Secondly, we've seen these layers. Layers are indicative of cycles of change. They attest to a record of processes. We've been seeing layers on Mars since we began exploring. We saw them with Viking, Mariner, etc. Now we see them at a fine scale. We now know there are rocks laid down by water. The rovers are going to extend that knowledge by driving. That'll give us a sense of how big, how much water. We're gonna follow this mission with Mars Reconnaissance Orbiter. It's job is to chart Mars at the scale of the rover that we can extrapolate across the entire planet. We can survey the planet for sulfate bearing rocks. That mission together with these rovers will give us targeting for 2009 Mars Science Laboratory. It will carry not only the devices like Opportunity but a new generation of instruments.

Ed: we owe a debt of gratitude to the teams that built this and launched it.

Q. Two of you used the "f" word, fossils. Would you expect one Earth to find fossils in these kinds of deposits. Would you be able to see them if they're there?

Dave: You'd have a hard time seeing such things. There could be on Earth some kinds of microscopic fossils in these kinds of environments. Some rocks like this on Earth have dinosaur footprints :-)

Steve: these are exceptionally good at preserving evidence of microbial life, within the salt crystals. Payload on this rover was designed to find evidence of habitable environments. I don't expect to find fossils and I don't expect to find dinosaur tracks :)

[connection flaked out here. Sorry.]

Q. Meridiani Planum is one of the flattest places, doesn't seem like a basin. Are we talking about a sea or briny pools dotting a landscape.

Steve: Good question and we don't have an answer at this point. Piecing together the total geographic puzzle is going to keep scientists busy for a long time. With respect to depths of water, we'll have better answers when we've explored further.

Dave: [signal loss again] You need a different scale of observations.

Jim: It's cooperatively smooth but there are smoother places. Secondly, some colleagues believe this area are exhumed, unburied. We have to be careful about seeing this in the light of a modern Mars.

Q. If you were to get these rocks back to an earth lab what tests would you run on them.

Jim: too many to describe. The kinds of things we'd do is read the proxies for the environments in the rocks themselves. We could look at crystals to see if we could identify the timing of their formation. We could look at them at nanoscale. That's the kind of capabilities our laboratories have. We could address the question of global climate, climate regime locally, reservoirs, with just grams of this stuff and that's why we hunger for these.

Q. What if a history of life is discovered.

Sean: The whole approach is to pursue exploration driven by science questions and informed by science as you move along. If we were certain what the right exploration pattern was, that would assume we already knew what we're trying to learn. Our program has to be adaptable, flexible. Stepping stone approach.

Ed: One specific example is the 2009 rover. Meridiani is now the prime landing site for that rover. Unless we discover something really exciting some place else, Meridiani is the place we'll want to send that rover. Because it's nuclear and can go a long ways we can cover a lot of ground.

Q. Can you say that there's a shoreline?

Steve: In a situation like this where you have evaporation, the shoreline came through. At some point in time there was a shoreline here. The extent of the water is something we don't have a good handle on. Taking data from MRO and MGS will give us a better handle on things.

[signal failed and didn't come back. sorry.]

another major announcement?

| 3 Comments

Alfons, in the comments here, points out that NASA is planning another announcement tomorrow. The last time they held one of these special press conferences was to announce their conclusions about the Eagle crater bedrock's watery formation. What are your predictions for this upcoming announcement?

My prediction is that it's one of these three (from likely to wildly unlikely):

One, The sedimentary rocks at Eagle crater were formed in a long-standing body of water (a lake or ocean). Two, Opportunity found current sub-surface liquid water. Three, fossil evidence of past life.

While we wait, check out Opportunity saying goodbye to the crater. Ohh, and he's put together a really nice panormama

update: Over at Mainly Martian, Oliver Morton also leans towards the sedimentary rock laid down in "a big old lake or sea". Thanks to Martian Soil for the pointer.

I'll try to break away from today's Mozilla BugDay for a few minutes to take some notes from the briefing and get them quickly posted. If you can't wait for the evening news to mangle the story or you don't trust the lame wire coverage, tune in here mid-day and I should have something posted.

Here it is, another installment of the amazing blog sensation, "Ask Asa" ;-)

Adam Hauner asks, "Will be crash analysis data of 1.7b available again on ftp://ftp.mozilla.org/pub/mozilla.org/data/crash-data/?" Adam, we'll be doing pretty well if we can just collect some data and do preliminary analysis and bug reporting of the top crashers in time for some fixing within the 1.7 cycle. Generating clean reports for publishing on FTP would certainly be a lot lower on my priority list than getting the servers working and the basic reporting hooked up so that we can quickly get some bugs filed and fixed. Maybe in 1.8 or 1.9, but it's just not a priority as I see it.

René Pronk asks, "How many e-mails do people like David Baron and Boris Zbarsky get on an average day? What is the all time record most-emails-on-a-single-day of a single member of the Foundation?" René, that's probably a good question for Boris or David. You might be interested in the BZ's blog post where he did some analysis of time spent responding to bugs and review requests. If you want a real answer rather than my dodge, you could pose the question at bz's blog or dbaron's blog.

José Jeria wonders, "I see that mozilla drivers (i think, choffman for example) are setting the flag to block the next release sometimes. And then when no patch arrived, they unset the flag. Does the person that set the "+" flag then expect that sombody voluntary sees it and writes a patch? Its confused me a bit when I see the "nobody came up with a pacth" comment and then unsets the flag. Shouldnt drivers when setting the "+" flag assign the bug to somebody at mozilla.org?" José, I don't see the "+" flags getting unset. I see some of them get set to "-" if that's what you mean. The plus flag is a notation drivers use to mark a bug that they feel ought to be addressed for that particular release. Drivers work with our development community to try to get resources applied to those bugs. Because Mozilla depends heavily on volunteer contributors (only 5 or 6 of the nearly 80 people that landed code in 1.7 so far are employed by the Mozilla Foundation,) we don't always have the resources to get fixes for all the bugs we'd like fixed. We re-evaluate our plussed list regularly as we get closer to the release and some of them are inevitably set to minus meaning we wouldn't hold the release for those bugs.

Bogdan Stroe says, "There used to be a page called 'Upcoming landings'. I've seen the presentation about the future of Mozilla, but it would be good if the near future would be more predictable. So, are there any plans to restore that page?" Bogdan, that's a good question. The branch landing tool, which listed major upcoming landings, was used to make sure that we didn't land really big or scary changes haphazardly, without sufficient testing or coordination with other large landings. This was particularly useful when we were making lots of significant feature additions and rewriting large hunks of code. With fewer of these major changes, better communication between our developers, and improved tools within Bugzilla (like the flags system), we've been able get by without the branch landing tool. I'd actually like to see Bugzilla incorporate a bit more of this scheduling and coordination functionality because using a separate tool just never really worked very well without a lot of pushing from "management".

Jason Barnabe asks, "Where is the bottleneck in the project right now that prevents faster growth? Bug triaging, patch-making, reviewing...?" Jason, I'm not sure that "faster growth" is really desirable. We could certainly use more help in all of those areas but I'd rather see us making smart, targeted progress on simplifying and shrinking our codebase and featureset. Bottlenecks to faster (feature?) growth don't bother me much.

Andrew Wooldridge says, "Asa, after poking around a bit I found a nice tutorial on how to create a mozilla extension http://www.mozilla.org/docs/tutorials/tinderstatus/ but I dont see anything like that for creating a mozilla theme. Do you know of something like that? Are there any plans to create something like a developer.mozilla.org to have stuff like this?" There are certainly plans to improve code documentation at mozilla.org. Brendan spent some time talking about plans for a msdn library-like site during his presentation at the recent developer day, most directly related to your question, he notes the need for tutorials and called on the community to contribute to this documentation effort. Outside of mozilla.org, there have been several efforts, including the Theme development section of the mozillaZine Knowledge Base, the Creating a Mozilla Skin doc, the Basic Theme Project, the IBM Developerworks tutorial, and inside of mozilla.org, there's not much that I know of, though you'll probably remember our stalled MAD courses which would be nice to get going again. I think that extension and theme development tutorials and information would be really nice to get nailed down and then kept up to date at developer.mozilla.org or the mozillaZine KB.

mcsmurf asks "to comment 1: is Talkback working again (can't try it since i build myself)?" Yes, Talkback is working again. We still have a ways to go before we have all of the reporting set up and we still don't have it in the nightly builds, but we're making progress.

Pat Dunn asks, "My question is what is the future of the suite?" Pat, we continue to maintain the Mozilla application suite. From a UI and feature standpoint, it's on a, in Brendan's words, "sustaining engineering footing and should not be subject to radical change" so you'll see improvements to core code, with minor cleanup in UI and features, but probably (hopefully, as I see it) nothing earth-shaking in terms of non-gecko feature development.

Michael Ward says "You probably aren't the best person to ask this...but...I'm in my first year of college working towards a computer science major...I'm wondring how "good" you have to be to program something like mozilla?" Michael, since I'm not a programmer, you're right that it's a bit difficult for me to answer this. But when have I ever let that stop me ;-) Anyone that's been around the project for very long would probably agree that there are a few really strong hackers, a larger number of "OK" hackers, and even a few not so good hackers contributing to Mozilla. I've contributed a few patches over the years and I'd say that I'm definitely in the "not so good" category :-)

Paul Jankura says, "I'm a second year computer science student currently in a usability engineering course. Looking at the differences between Seamonkey and Firefox, Firefox looks like a case study in cleaning up a user interface (simplfying the menus, moving options from the pull downs to the Options box, adding customizability, etc). I was wondering who made these decisions and what were some of the specific goals and logic behind them?" Paul, I'd say that most of the credit goes to the three or four engineers that wrote the bulk of Firefox (first m/b, then Phoenix, then Firebird, now Firefox). The short answer is that Ben Goodger, Blake Ross, and Dave Hyatt had a lot of experience doing browser development on the old Mozilla application suite and they took everything they learned on that project and, without any of the various marketing, management, scheduling, etc. pressures, they set out to make a great web browser that wasn't going to try to be all things to all people. The goals have changed some over the years but I think that the original README for the project answers this question better than I can.

  1. CVS access is restricted to a very small team. We'll grow as needed, based on reputation and meritorious hacks to mozilla/browser.
  2. This will be a single process for the browser only. Mail clients, web editors, etc, will be out-of-process. Hooks for other apps will be provided eventually, although that is not an immediate goal.
  3. No profile manager UI on startup, although you can still select multiple profiles from the command line.
  4. The default theme will be Classic. Additional themes will be supported but will not be part of mozilla/browser.
  5. The toolbar(s) will be configurable. That includes moving the location bar where the user wants it (not just splitting it so it takes a whole toolbar width).
  6. The personal toolbar is the personal toolbar, not the whorebar.
  7. All wallet-like functionality will be rewritten from scratch.
  8. We will have a sidebar, but it may work differently from Mozilla's current one.
  9. There won't be 239 access points for Search and for Bookmarks!
  10. We may drop the throbber.
  11. The interface will not be "geeky" nor will it have a "hacker-focus". Nor will it be "minimal". The idea is to design the best web browser for most people. (This doesn't mean every feature has to be enabled by default.)

Tom Graham asks, "If you had unlimited resources, what element of mozilla would you invest in to improve and develop more?" Tom, I personally would favor investing in distribution. With unlimited money, I'd work out deals to see Mozilla applications shipping on every new computer. I'd mail out Mozilla and Firefox shaped USB keychains with the apps ready to run. I'd push for a massive internet and traditional media advertising campaign. I'd just go all out on getting Mozilla onto every single desktops because that's an area we must improve if we're going to stay relevant.

Jeff Walden asks, "When's the next BugDay? I have a feeling there either wasn't one this week (due to 1.7b) or I simply missed it." Jeff, every Tuesday is BugDay! We may be adding a second day or partial day (maybe a Friday or Saturday) for people that can't make Tuesdays. This last Tuesday, I was, indeed, overrun with release activities so I wasn't as active on IRC as usual, but I was there and so were a half dozen or so others who regularly help out on BugDays. Every Tuesday! Jeff went on to ask, "How does one accurately determine the number of bugs one has resolved (through a Bugzilla query, most likely)?" A query in the boolean charts for "status changed to resolved" AND "status changed by asa@mozilla.org" would give a list of the bugs I've resolved.

Samual Icky has a few questions:
"When will we see Pinstripe for Mozilla Thunderbird? Kevin mentioned in his blog we that should expect to see it late to mid-February." Not sure. You'll have to ask Kevin that question. I suspect that rsn is a reasonable guess :-)
"Will we ever see Sunbird?" You can see it today.
"Will any of the remaining Classic Mac OS bugs ever get closed. I know some one started that a few weeks ago but it appears the person stopped for one reason or another." Sure. We're workin' on it. There aren't that many left. If you'd like to test any of the remaining bugs and resolve them if they don't impact OS X or update the OS field if they do, that'd be great.
"Do you think the Mozilla Suite or Mozilla Thunderbird will ever have access to Mac OS X Address book? Alternatively, will the bird or suite ever support the Keychain?" Ever? Yes.

Marc Randolph asks, "do you know of a true streaming rss reader that fits in a Mozilla browser? I'm thinking of something that is exactly like what's shown at http://www.linkston.com/ ... except I want in my Firebi^H^Hfox sidebar." Marc, I don't know of any RSS extensions that currently allow you to aggregate feeds into a single list. RSS Reader Panel and Forumzilla are the two XUL feed readers I use. I think viewing all feeds in a single sortable list would be a nice feature addition for both of those apps. You might check out NewsMonster and Aggreg8 to see if either of those offer something closer to what you're looking for. I don't think they do but I haven't used them in a while either so I could be wrong.

Blonker got in just under the wire with this question: "I don't think this has been asked before. What do you think about the "UFO" Spirit saw this week? Reference info: http://news.bbc.co.uk/2/hi/science/nature/3520636.stm
Well, it certainly is an unidentified flying object. Unless we get a repeat, I don't think we'll ever have a definitive identification but I agree with all of the serious reporting, that it's very probably a meteorite or a man-made Martian satellite. My money's on it being a meteorite, but I wouldn't be surprised to find out that it was Viking 2.

Well, that concludes another installment of Ask Asa. Feel free to ask follow-up questions, to discuss or add to my responses, or to pose new questions. I'll look to the comments at this post for questions for the next installment.

cool mozilla testing utility

| 6 Comments

I regularly find myself looking at a bug in Bugzilla which reports a site not displaying the same in Mozilla as in, say, IE 5.5. At work where I have several machines running different versions of Windows and IE, I can just move over to some other machine to compare IE and Mozilla rendering. When I'm at home, though (evenings and weekends,) I only have one IE version and if my machine is booted into Linux then I have to reboot to use it.

Along comes ieCapture (found via Two Tall Socks) which will hand you a screen capture of the page as seen in IE 5.01, 5.5, 6.0, Opera 7.23, and Firefox 0.8!

This service totally rocks. If we could set up an installation at Mozilla, it might really speed up some of our bug triage. It takes about 45 seconds to return results and I don't know how much of that is network bound and how much is the actual tool and hardware speed. Maybe this tool or one very similar ot this tool running on high-end hardware with a fat pipe could return results faster.

What do you all think? Would something like this help incoming bug triage?

backyard birding

Deanna and I spent several hours just relaxing in the back yard today. To our delight (but not at all uncommon here) we had repeated visits from a wonderful variety of birds.

From big to small, we watched: 4 red-tailed hawks, a canada goose (at a great distance), several common ravens, a beautiful northern flicker, a few rock doves, two (very noisy) western scrub-jays, a mourning dove, several very colorful spotted towhee, a pair of california towhees, a house finch, several sparrows (unidentified), an oak titmouse or two, a bewicks wren, a chestnut-backed chickadee, an early lesser goldfinch, and finally, an anna's hummingbird.

Also seen in our neighborhood, but not seen today are california quail, robins, mockingbirds, gulls, nuttall's woodpeckers, crows, american goldfinches, junkos, black phoebes, western bluebirds, various sparrows, and I'm sure I'm leaving off a few.

Looking just beyond our neighborhood the variety skyrockets. We live at the western edge of Redwood City, at the base of the Santa Cruz mountains. It's a 45 minute drive over the mountains to the coast and a 15 minute drive east to the marshes and the bay. If you enjoy birds, this area is just great.

lazy saturday

| 2 Comments

I'm still planning on getting some Mars notes posted and I've started to put together some responses for the next installment of Ask Asa. I probably won't get all that posted till this evening or tomorrow. In the mean time, check out Udell's latest on Mozilla Firefox. "I�ve abandoned Safari on OS X for the same reason I�ve abandoned IE on Windows. Firefox does more, it�s moving faster, and � here�s the kicker � it runs identically on Windows, OS X, and Linux. On each of these platforms, I enjoy a state-of-the-art end-user experience."

nasa press and ask asa

| 20 Comments

I hope to have notes from this morning's NASA press briefing posted tonight or tomorrow morning. I'd also be happy to do another installment of "Ask Asa" in hte next day or two, but I need more questions :-) so use this space to ask any questions you've got.

Bonneville Crater

soup

| 1 Comment

Mozilla 1.7 Beta is finally done.

gettin' close to beta

| 2 Comments

We're working out some last-minute talkback issues and hope to have a release real soon now. If you'd like to help us test these (hopefully) final builds, join #mozillazine on irc.mozilla.org and let me know. You can get candidate builds here: windows, linux and mac

Also, if you have any corrections, suggestions, etc. for the What's New section of the release notes, please let me know.

above and beyond

| 2 Comments

Nigel McFarlane (of 'Rapid Application Development with Mozilla') has a new article called Above and Beyond DHTML Menus, posted at DevX.com, which takes a look at XUL as a replacement for DHML menus. It begins:

Here's a little sanity. It's apparent that the decision to build multi-level menus forces some assumptions on the target browser, so let's make a break from the standard assumptions and see what happens if you assume the target browser is exclusively Mozilla. Many user communities now exist where Mozilla use is the primary or only choice, or where Mozilla use is increasing rapidly. The growing number of Linux users is an example.

An interesting read and a good find by Rant Central.

ultraedit users?

| 8 Comments

Are there any UltraEdit users out there? I'm looking for a CSS wordfile that's better than what's available at ftp://ultraedit.com/wf/css2.txt. If you know of one, please share it in the comments here or email me if the comments are still wonky. Thanks.

hematite in the blueberries

| 2 Comments

David Chandler, of NewScientist, is reporting that the hematite is in the blueberries. Not surprising. Does that mean that these concretions cover the entire area that MGS TES sees the hematite?

not the imminent threat we hoped

| 1 Comment

We're investigating a bug that causes the Modern theme to include classic styles for various UI widgets and I think our chances of releasing today are getting slim.

bunny ears

| 1 Comment

NASA/JPL have posted a cute article on the "bunny ears" first spotted in the mission success panorama at the Opportunity site. While not completely solved, the mystery is certainly a lot less mysterious :-)

is it soup yet?

| 2 Comments

Mozilla 1.7 Beta is very, very nearly wrapped up. We're making what we hope are final builds right now and if they test out OK, then we'll have something ready for download rsn. It's looking more and more likely that won't be until tomorrow morning at the earliest.

1.7 beta on the way

| 10 Comments

We're very close to releasing Mozilla 1.7 Beta. There are some really good changes in this release. I've just landed the first drafts of the What's New and rough changelog pages. If you have corrections or additions, please let me know.

comment spam

| 8 Comments

With comments broken most of the time, I don't expect to see a lot of comment spam but if this movable type throttle solution ends up being worse than the spam problem, I'm thinking about other ways to deal with spam floods. One thing I've been thinking about is just removing the "post" button and forcing everyone to go through "preview" which seems like it would cut down on a lot of the spam without too much hardship for commenters.

What do you all think. Do you have experience with spam floods at your weblog? Besides MT blacklist and throttling, are there other good solutions?

darkness :-)

| 5 Comments

(I think comments are working again)

Tonight, when Deanna and I got home from eating at Little India (really tasty and really affordable, downtown Redwood City) I noticed that my neighbor's massive floodlight was out. Whoopie!, I shouted to myself making my way to the backyard.

The sky was free of clouds and while the lights of suburbia dim much of what's available, without my neighbor's massive floodlight glaring up our entire yard, I quickly drilled in to the Trapezium cluster in the beautiful Orion Nebula. It was really a surprising view, not what you get on the other side of the hills, away from all the light, but pleasant none the less. After soaking that up for about a half hour (and sharing it with Deanna, briefly) I turned to the very bright gibbous Venus. By that time, Venus was already getting low in the sky (and into the neighborhood lights) but still a beautiful and alarmingly bright view.

I may head back out for a look at Saturn which should still be fairly high in the sky and if I get back out quickly, Mars may still be above the lights. Gotta take advantage of that burned out floodlight bulb :-)

thunderbird improvements

I'm using a new build of Thunderbird email and so far so good. redemption in a blog has all the details so go check it out.

extended mission

| 6 Comments

(I think the comments are still broken, sorry.)

There's been lots of talk since Thursday's press briefing about the extended mission for the two MERs. Jennifer Trospers mentioned that the team thought the rovers could make 200 sols, more than double the mission's 90 sol nominal lifetime. Last month Steve Squyres suggested that the rovers could be driving well into the summer.

What does this extended mission mean for the Spirit rover?

It's looking more and more like Bonneville crater, where the MER-A currently sits, isn't going to prove interesting enough to drive down into. If either the science team determines that Bonneville's interior is not interesting enough or the engineers decide that it might be a bit of a rover trap, that's going to make the East Hills complex the next target. At a distance of roughly 2.5 kilometers, it's a fairly distant target.

Spirit's taken about 30 days to drive the 350 or so meters to Bonneville. Today I read, over at Due Diligence, that Spirit's driving speed of 5 cm/sec makes for a fairly long trip over to the East Hills complex.

I suck at math, but I think that 5 cm/sec must be max-speed, rolling downhill, on smooth pavement or something. By my admittedly poor math, that would work out to 180 m/hr and that seems really, really fast given that on top sols, Spirit only made 30 meters (though I seem to recall Dr. Squyres suggesting that a 100 meter sol was not out of the question). I know that Spirit doesn't drive for her full sol uptime, and she was certainly spending considerable time (and more importantly, power) on science targets, but at speeds like 5 cm/sec, she would surely do more than 30 (or Squyres' 100 meters) in a sol. I think that 5 cm/sec is probably just raw motor speed and doesn't take into account any other requirements for actual driving.

Assuming that 100 m/soly is the upper limit and with 30 meters/sol as the proven baseline capability, how long until Spirit's sitting at the foot the East Hills? My math says, roughly, something between 25 and 85 sols. If we don't find anything terribly interesting along the way, I'm guessing in the middle of that range and estimate that it's going to be about 2 months of driving to get to the hills.

That's about how long it's been since Spirit's wheels first hit the ground and would put Spirit at the 2/3rds mark for the extended mission. That's quite exciting to me -- in the hills with as much as 2 months of remaining life to do science. That would totally rock. Heck, even at only 20 m/sol, Spirit could still make it to the hills, or very close, and get some really nice Pancam pics and mini-TES data.

As a spectator, my biggest concern is not for the capability or lifetime of the rover, but for the budget that's making all this science and coverage possible. Does anyone out there have any information on whether the "extended" mission will actually be funded? Will, for example, the folks keeping the images flowing to the website and the people doing the press releases still be around and paid to continue these activities? Will the science team members all return to their jobs in academia and elsewhere or will they continue full-time involvement with the rovers until the very end? Were these questions already asked and answered and I just missed it?

(If you've got anything to add and my comments still aren't working, then please use email or your blog to comment. Sorry, again, for the brokenness of things here).

commenting problems again

| 1 Comment

If your comments aren't being accepted, please send me email. I think it's acting up again.

more feed fiddling

| 5 Comments

I've been playing around with the two feeds (Atom 0.3 and RSS 1.0) and have something now that I think I like. I'm now serving the full content of the post in the feed and I've also added a link back to the HTML so you can participate in comments. I'll be investigating how I can serve comments as items within my feed too, but I need to study a few more aggregators to see how they'll handle that. So far, I'm doing all my testing with the Feed Validator and Forumzilla so it's not very broadly tested.

For those of you with feed readers, are my feeds sufficient? Would you like to see them changed? How? What readers are you using? Let me know. The feeds are for you, not me, so I'm happy to make changes.

ask asa again

Andrew Wooldridge asks, "what is your take on adding SVG to the default builds?" and Albert follows up with, "Do you know when SVG will become part of the default build, now that the backend rewrite's complete?"

Well, I didn't realize there was a "backend rewrite" that had happened. I guess I wasn't paying close enough attention. I just assumed the recent major chunk of work was to merge the long-lived SVG branch with the tip of the trunk. I'd be interested in seeing SVG become part of the default builds when it's more complete, when all of the code is fully reviewed, and when we've got a decent set of testcases and a sufficient number of people committed to regular testing.

Fabiano G. Souza says, "Since you says that 'I'm not a developer so I won't be coding any time soon', it would be interesting to know what your background is and how you ended up in the mozilla world" and Jens Bannmann continued, "do you plan to learn coding, or are you happy with staying a non-programmer, so to say?"

My background (pre-Mozilla) is in architecture, historic preservation, and fine art conservation and restoration. I ended up in the Mozilla world thanks to some buddies at Auburn University (where I was studying architecture) -- early linux adopters who got me interested in open source a couple of years before Netscape opened the source and launched the Mozilla project. I really liked the idea of open source development but Linux just didn't appeal at all. When Mozilla happened, it looked like a great opportunity to get involved in open source on an application that I really liked, the Netscape web browser. I started filing bugs and helping others file bugs and the rest is history :-) I'd certainly like to learn a couple of scripting languages but I have very little aptitude in that area and it's goint to take more time than I can afford right now so it'll have to wait.

George Deka wonders, "So what is happening with the whole trademark thing for firefox and what is your perspective on the debian debacle going on at the moment as to wether firefox is still considered free software as per the DFG"

I'm not sure I'd call it a debacle. Actually, I'm quite sure I wouldn't. believe strongly (though IANAL) that Firefox is free software per the DFSG. Our trademarks, however, are not software, and they're not free, and we intend to protect our marks. All parties involved want to see Debian ship our application and to call it "Firefox" and I think we're close to a solution for that. The Firefox logos are tricky and it may be the case that Debian ships with alternate artwork, either supplied by the Firefox team, or a 3rd party.

vfwlkr asks, "Where did the phrase 'everything but the kitchen sink' originate from?"

I'm gonna just take a guess at this one and say that it comes from moving where you pack up and move everything that isn't bolted down. Or maybe it's got more violent roots than that and it comes from an account of a wife, displeased with her husband and throwing dishes at him, then chairs, and eventually everything except the kitchen sink :-) I honestly don't know. It was fun thinking about though.

José Jeria asks, "Are there any plans on hiring more programmers to the Mozilla Foundation? For example today, mscott develops Thunderbird on his free time. Would be great to hire 2-3 guys like him to work on a project such as Thunderbird fulltime."

Scott MacGregor is an employee of the Mozilla Foundation and he's working on Thunderbird on company time (and his own time as well, I'm sure). It would be nice if we had a few more engineers, but right now I don't know of any plans to hire more programmers.

Andrew Smith says "And other silly question: How do you pronounce Asa? Ah-sa? Ay-sa? Ah-za? Ay-za? (Let's call the whole thing off...)"

Good question Andrew. I pronounce it two ways, A-suh and Ace-uh, both with long As.

Well, that's it for another instalment of Ask Asa. If I didn't get to your question then be sure to ask again for next week's installment. Use this post to talk about any of these answers as well as to ask questions for next week.

update: I dropped the ball on a few questions that I got in email and had intended to try to answer this week. I suck. If you sent me questions in email, I'll try to get them into next week's post. Sorry.

latest mars news

I'll try to get some briefing notes posted this evening. Bonneville crater sure looks interesting. In the mean time, use this post to discuss the latest Mars news or ask any last-minute questions for Ask Asa (which I hope to answer tonight or tomorrow morning). Email me at asa@mozilla.org if you have any difficulties posting comments.

update: ugh. my recording of the press briefing doesn't seem to have worked. I'll see what news I can pull together from around the web and do a status update in the next day or two.

Today's MER Press Release is a good place to start.

ask asa delayed

| 11 Comments

I'm going to hold off on posting "Ask Asa" answers until we've got this commenting problem sorted out. I'm really not sure what's going on and it's mostly in the hands of my hosts at mozillaZine who maintain the MT installation.

For some reason, there doesn't seem to be this problem at any of the other mozillazine-hosted blogs. If any of you have any idea what might be going on, please email me.

commenting problems

| 1 Comment

I'm having some difficulties commenting and assume that others might be too. Our wonderful hosts have been working on reducing spam to the blog comments and I've let them know that it seems a little bit over-agressive. Don't be discouraged if your comments aren't making it through. Try back in a few hours.

update: Still not sorted out. If you've got questions for this week's "Ask Asa", you'll have to mail them to me. I'll be taking questions for another few minutes :-).

bugzilla article preview

| 1 Comment

I'm beginning a series of short (trying to keep them in that 800-1000 word range) Bugzilla articles. The first few will be covering the new features we've recently gained in our latest Bugzilla upgrade. After that, I'd like to start doing "tips and tricks from a Bugzilla power user" (or some more catch title) articles. I'm posting the first installment of this new series here at the blog for your feedback before I try to get it run at mozillaZine and maybe other outlets. I'd appreciate any feedback you have (especially if it helps me trim a couple hundred words :-)

Bugzilla Improvements (part 1): Find a Specific Bug

As most of you know, mozilla.org upgraded Bugzilla last month bringing us up to version 2.17.6 (and maybe a little bit more). It had been about a year since the previous upgrade and so there's lots new to love about this latest rev. While I'm sure there are scores of bug fixes and changes that make Bugzilla more robust, secure, and easier to set up and administer, this series isn't about all that wonderful backend work, it's is about a few of the new end-user features I think that b.m.o users will want to try out.

The first new feature, and I think the most exciting, is the new "Find a Specific Bug" interface. I regularly run two basic types of queries. The first is when I'm looking for a group of bugs like "all bugs with driver approval requests" or "bookmarks crasher bugs assigned to ben". These queries are about isolating a category of bugs, getting bug lists or bug counts. The second type of query I do is when I'm looking for a specific bug. Maybe I've seen the bug before and I'm trying to find it again, or maybe I'm about to report a new bug and want to make sure it isn't already reported. In those cases, it's a particular bug I'm looking for, not a category of bugs. The new "Find a Specific Bug" search feature makes this task much, much easier.

"Find a Specific Bug" uses MySQL "full-text search" functionality to match and sort on what it calls "relevance". The magic behind this "relevance" indexing and searching is available to any of you who want to ask the MySQL documentation or investigate the Bugzilla code that uses it. The important bit of information here is that the results of this "Find a Specific Bug" search are sorted with the most relevant matches at the top, just like Google! No more sorts on bug number or Component, or other not very helpful ordering. Now Bugzilla just puts the most likely match at the top of the list.

The interface to this feature is quite simple but the results are amazing. The first field you can set is the Status and the choices there are "open", "closed", and "all". Open bugs include the Unconfirmed, New, Assigned, and Reopened states. Closed includes Resolved and Verified. The second field is the Product select and that list should already be familiar to most of you, though it's nicely grouped by product categories in this interface. The last field, "Words", is where the magic happens. Punch a few words into this field and Bugzilla searches through the database of bug reports and returns a buglist of the top 200 most relevant results. 200 may sound like a long list of bugs to return, but I almost never have to move down past the first page of the buglist because my bug is almost always in the top few spots on the list.

This tool is designed to be simple to use and I would like to see all bug reporters doing at least one query here before submitting new bugs so I hope the interface doesn't get any more complex (I could actually see it getting simpler). But don't let it's simple interface fool you. The results are a big improvement over the standard buglist when your goal is to find one specific bug report

For the power users, I have two sets of tips. The first is for use in the "Find a Specific Bug" interface and it's called boolean full-text search. The "Words" field will accept a set of boolean operators, +, -, < >, ( ), ~, *, and ". The + operator, added to the front of a search term, says that word must be present in any bugs that make the results listing. The - flag appended to the front of the term excludes any bugs that contain that word. The < > are used to decrease and increase the relevance value that word adds to the overall relevance value of the phrase. The ( ) operators group words into subexpressions. The ~ is a negator which can be used to make a word's relevance contribution negative, pushing any matches on this word down the list some. The * can be appended to the end of a word to match all words starting with that string. Finally, " can be used to wrap a phrase so it matches only exactly as you typed it. When limiting your searches using the boolean operators, your results list may have fewer than 200 bugs.

The second, and even more powerful use of the full-text searching is in the " Advanced Querying Using Boolean Charts" interface located at the bottom of the "Advanced Search" page. Selecting "content" from the first select list, and "matches" from the second select gives you the same basic functionality you get from the search field on the "Find a Specific Bug" interface. The beauty of this "Advanced Search" is that you can combine the power of the full-text searching and relevance sorting with all of the other fields available to you in the "Advanced Search" interface. You could, for example, limit the results to a particular Status or Resolution, limit to one OS, or get specific with a single Component search.

The full-text searching is still in development and will hopefully provide even more accurate results as it is fine-tuned but it's already a big leap forward in ease of use. This new feature should really help us cut down the number of duplicate reports as well as make it a lot easier for the teams of contributors doing bug triage to weed out duplicate reports. For the next installment of my "Bugzilla Improvements" series, I'll be describing some of the new "Reporting and Charting" tools, so stay tuned to this space if you'd like to learn more about our improved bug graphs, tables, and charts.

another good bugday

| 2 Comments

Today in Bugzilla, over 350 bugs were resolved as either Fixed, Invalid, Duplicate, or Worksforme. It was a good day for bug cleanup with the growing BugDay team knocking down about 280 Invalid, Duplicate, and Worksforme bugs. If you're interested in being a part of the BugDay efforts, come join us on IRC each and every Tuesday.

Just as a side note, I haven't posted my Mozilla Developer Day presentation yet (hopefully in the next day or two) but in prep for that event, Myk and I did a little bit of digging in the Bugzilla data to update some of the community involvement statistics I like to brag about in these kinds of presentations. These are all rounded off but I certainly think they're exciting, so I'm sharing them here as well.

We have about 50,000 people who have ever reported a bug in Bugzilla. About 17,000 of those people are repeat reporters who account for about 200,000 reports.

Henrik Gemal is the top bug reporter with almost 2,600 bugs reported. Ten people have reported more than 1,000 bugs. About 50 people have reported 500 or more bugs. Just over 1,000 people have reported 30 or more bugs, and about 3,000 people have reported 10 or more bugs.

On the bug resolving front, including Fixed, Duplicate, Invalid, Wontfix, and Worksforme, more than 7,600 people have resolved at least one bug report.

Boris Zbarsky is our top bug resolver having personally put to rest over 7,700 bugs (your fearless blogger, here, has resolved just under half of that number, mostly as Duplicate, Invalid, and Worksforme). More than 50 people have resolved 1,000 or more bugs. 350 people have resolved 100 or more, and about 900 people have resolved 10 or more bugs.

We've got a large and prosperous community of engineers and testers but there's always room for more. Every week we're growing those numbers, working with lots of new faces -- people who have decided that they want to be involved with more than just an occasional bug report. If you're one of those people who wants to make a real impact on the quality of the Mozilla products, join us on BugDays, every Tuesday, and we'll have friendly and knowledgeable people on hand to help you take that next step. It's fun and rewarding.

hubble ultra deep field

| 2 Comments

I'm sure most of you have already seen it but the good folks at NASA have just released the super-sexy "Hubble Ultra Deep Field" (taken by ACS) which peers all the way to the edge of the visible universe, making visible some of the first galaxies as they looked about 13 billion years ago.

This images, which shows nearly 10,000 galaxies (those really big things that contain billions of stars), like it's older brother the Hubble Deep Field, is actually a very tiny window in the sky, taking up about the same space as the area covered by Roosevelt's eye on a dime held at arms length.

The universe is a pretty big place. We're finally reaching the visible edge and it still feels really, really big.

update: absnath, in the comments, points to the latest from the ESO's VLT -- now they're really at the edge! Wow. Mind blowing.

orkut does mars

The Mars Exploration Enthusiasts community that I set up on orkut is just a couple of people away from the 300 member mark. If you're interested in Mars exploration and you're an Orkut member, join up today!

rats! mars roundup

I learned over at Daniel Morris' From Behind the Wall of Sleep that there were problems with Opportunity's scheduled RAT sequence today. Spirit, now into the final third of her nominal mission (though it's highly likely that the rovers will push on beyond the scheduled 90 days) is driving toward Bonneville crater and on sol 62 made it nearly 86 feet. Also, Beagle II's been in the news the last couple of days but the wire reports aren't nearly as good (or honest/accurate) as what you can get from Mainly Martian so head over if you're interested in more on the Beagle II.

blog updates

| 15 Comments

I've made a couple of changes to the layout of adot's notblog* and even though most of them are minor, I thought it would be a good idea to note them here so no one thinks their browsers broke :-)

First, I've removed the short blogroll over on the left side while I rethink how to make it work better, or if I'm going to have one at all. Even with a list that short, links were rotting and I'm not sure anyone was really using it so for now it's gone.

Second, I pushed everything left a bit to give a little more space to the primary column and for the single post archive view I eliminated the left column completely to make the pages a little more functional in feed readers (like forumzilla).

Third, I tried to improve the visibility of the two Feedster tools underneath the archive links in the left nav column. To make a little more room for text entry I removed the search button on the Feedster search (just hit enter to submit the search and you'll get results for adot's notblog*) and I enlarged the button for the Feedster "table of contents" which gives a nice Feedster listing of all of the adot's notblog* posts.

I'll be making a few more tweaks, mostly to improve the site's appearance and usability in feed readers so they'll mostly be confined to the archives. I'd still like to keep some uniformity across the site so some of the changes I'll be making to the archive pages will probably bleed into the front page as well.

As with any of my updates, I try to give a quick glance at how things look in the lesser browsers and if it's not terribly difficult, try to make things display OK there too. If you see anything that looks broken in IE, Opera, or Safari, please let me know (patches welcome too).

update: well, I've done a bit more research and decided that rather than try to style the content for feed readers, I'd just stop linking to the website content from within the feed and start pushing the full post instead. I've updated the RSS 1.0 feed to "full content" and added an Atom feed (also full content) as well. If you're pulling down my feed(s) and have any problems, please let me know.

my dream machine

| 4 Comments

My dream computer is coming together. I want a computer that fits in my pocket with all the power and usability of my desktop PC. Today I see that one more component is about to arrive :D

Think of an iPod-like device that carries your OS and files, that has a built-in projection keyboard and a built-in miniature projector. You set the hand-held device on a flat surface and out of one side it projects a gorgeous video display onto a nearby wall or other vertical surface, and out of the other side it projects a keyboard and touchpad mouse onto the table or desk on which it sits.

All that's missing now is ubiquitous wireless and that's probably not far off either. I can't wait for the future ;-)

Oh, one other feature I forgot to include, and that's the ability to just hijack the peripherals from any desktop I happen to be near. If I set the device down next to a machine with a nice keyboard, mouse and monitor, it should just be able to wirelessly (bluetooth?) connect to those and "borrow" them.

ask asa supplemental

| 7 Comments

Earlier in the week I attempted to answer one of the "Ask Asa" questions about websites that use JavaScript to disable context menus. As I was investigating that issue, I called in some expert advisors, Chris Aillon and Johnny Stenback. Well, Chris and JST helped me with the answer and today Chris helps us all with the fix :)

If you're tired of website's disabling your context menu, grab a new build of Firefox or Mozilla tomorrow and set the pref. You can do this by editing your preferences file or by using about:config. To use about:config, type about:config it in the URLbar and right-click anywhere inthe resulting list of preferences. Select New -> Boolean from the context menu and then fill in the values dom.event.contextmenu.enabled and false. That should block sites from being able to suppres your menus :-)

Anyone want to throw together a patch for Firefox's Advanced JavaScript Options window so we can set this with real UI?

late posting but...

| 6 Comments

Mozillazine-hosted blogs weren't completely functional yesterday so I didn't get this posted when I first ran across it (so you've probably already seen this but...)

Check out Skip Happens' post on Firefox. Great stuff :D

After looking at the image for a while, I think Hubble is actually seeing it upside-down and backward :-) Tell me what you think.

blog plugs

| 1 Comment

I don't maintain an extensive blogroll, like many of the sites I visit regularly. This is mostly because I don't find them particularly useful and I'm not convinced that readers find them useful either, especially if they grow to be really long.

In light of this "shortcoming" I've decided to try to do a regular, hopefully weekly, installment of what I'm calling "blog plugs".

Blog plugs will just be a chance for me to share some of the many weblogs I read regularly but might not include in my normal posting. If I'm already mentioning a site regularly as part of one of my interests (say, Mars, or Mozilla) then it probably won't make blog plugs, though I reserve the right to gratuitously plug and re-plug any blog at any time :-)

Blog plugs will also be an opportunity for you all to share with me. If you know of strong blogs that you think might interest me (or you have one that you'd like me to read and maybe plug) just let me know in the comments section of any of the "blog plugs" posts.

With this inaugural blog plug installment, I want to highlight a real gem called The SpaceWriter's Ramblings. This fantastic blog is written by Carolyn Collins Petersen and it's such an amazing read that once you start, you won't be able to stop until you've read through every one of the archived posts. It's really that good.

It was posts like this that inspired me to start blogging about my favorite Mars pictures (remember my old image link dumps?). Carolyn's "Does This Telescope Make My Ass Look Too Big?" and "Astronomy and Taxes"(ed. link corrected) are wonderful examples of what blogs can do that just doesn't get done elsewhere. Carolyn inspires me and this kind of writing makes it clear that blogs, even in their often derided "personal journal" format, in the right hands, can transcend themselves.

Go check out The SpaceWriter's Ramblings. You'd be hard pressed to find more entertaining and informative reading, in the blogosphere or any sphere.

trench pics

| 1 Comment

Michael Lyle over at Mars Exploration Rover Imagery has some pseudo-color images of the Opportunity trench at Meridiani Planum. These are way cool, check 'em out. image 1, image 2, image 3, image 4, image 5, image 6. I think that one and three are just awesome.

And this is a darned nice RHazcam image :-)

Oh, one more. This look over the rim of Opportunity's small crater shows that these plains were made for drivin'. I don't think she's gonna have a difficult time making tracks toward that large crater.

Also, Steve Squyres updated.

another ask asa!

| 13 Comments

Here are the answers to your questions from the last week. Enjoy. And if you have questions you'd like me to try to answer for next week, just plonk them down in the comments section.

Anon asked, "When will we get a new roadmap?" and "When will Firefox engineers stop fixing bugs and start reviewing patches?" or something like that.

Well, Anon, Brendan put forward some direction and roadmap ideas in his Mozilla Futures presentation at Developer Day last week. That's probably a good place to start. As far as reviewing Firefox patches, I'm confident that the Firefox engineers have prioritized their work in a reasonable fashion. If reviews are low on that list right now, that's just the way it is. Good luck.

Several people asked the questions like "How will the Mozilla Foundation sustain itself?" Rather than answering those individually, I'll try to cover the basics in one reply.

The Mozilla Foundation started its life with a grant of money and other resources from AOL, Mitch Kapor of the OSAF, IBM, Sun Microsystems, Red Hat, and other organizations. Since the Foundation was formed, several people, including Bart Decrem, Chris Hofmann, Mitchell Baker (and I'm sure a few others) have been working to build revenue streams through relationships with companies and organizations interested in building on top of the Mozilla technologies as well as direct deployment of Mozilla products. Mozilla Foundation is a non-profit and we're also soliciting donations through the website. We're making progress but still have a ways to go. For some perspective, the Foundation is a little over six months old, and already half of the employees have their salaries covered by other than AOL money.

Kovu asked about the mating habits of the Mountain View squirrels and all I have to say about that is "Darn! Give them some privacy, why don't ya." :-)

Tim Powell asked about automated testing. Tim, we're not as far along with this as we'd like to be, but we do have a suite of tests that run on the Tinderboxen which measure changes in page load, start-up, and new window performance, as well as code size and other memory characteristics. All of those tests and their results (including years of graphed data) can be tracked at the tinderbox pages. Also, Robert O'Callahan (roc) has written a layout automated testing tool which does page compares to identify regressions. I'd like to see us get that hooked up to tinderbox if possible. On the functional test front, we've had several efforts in the past to build automation into functional testing, including one app called "autosmoke" which hooked into the Mozilla chrome and attempted to run the daily verification smoketests. It, unfortunately, wasn't completely automated so one had to "tend to it" while it ran. Eventually it bit-rotted. I'd welcome, enthusiastically, any help in developing test automation for Seamonkey or any of the Mozilla applications. Unfortunately, I'm not a developer so I won't be coding any time soon. Until we get more automation, I'm spending some time with Myk to build a tool for storing tests and recording the results of functional testing. I figure if we can break our tests up into little pieces and make them available to lots of people, we can get pretty good testing coverage without the massive time requirements for anyone one person completing a full area of testing (as is the case without a tool to track what's completed and what's not). If anyone is interested in being a part of developing the automation or manual testing programs for the Mozilla applications, please let me know. If you're concerned that we might not be getting any regular testing coverage without automation, don't forget the many thousands of people who download and use our nightly builds every day. That's not to say that more automation wouldn't be a great thing.

AndrewW asks about free tools for win32 systems. Well, Andrew, as you rightly guessed, I'd start out recommending Firefox and Thunderbird. Cygwin, as you also noted, is a very powerful set of tools. I really also like the jEdit java-based editor for my text and markup editing and OpenOffice 1.1 is getting pretty good for wordprocessing and spreadsheets. I like (free but not open) Shareaza for that all-important file swapping and bittorrent sharing, along with, maybe, Filezilla for your FTP needs. If you need oss file swapping, then LimeWire seems to be next best. Also, I hear that Gaim is available for Windows now, but I haven't tried it yet. You might give it a look. Lastly, Audacity 1.2 was just released so that's worth investigation if you need audio editing and playback. (Chris Aillon reminds me) X-Chat for your IRC needs (if Chatzilla doesn't float your boat.)

Udo asks, "What are the chances that we'll ever see the 'big two' future mozilla app's (Firefox and T-Bird) running on one single shared GRE." I think the easy answer is that the chances are good. When, now that's another question. I don't think that either Firefox or Thunderbird leads have plans to tackle this before their 1.0 releases.

Lauritz Jensen asks, "How would one, that have been using, say, the mozilla-win32-svg-GDI-mathml.zip version of mozilla, go about switching to Firefox[1] (and Thunderbird[1]) that we have been hearing so much about, while preserving (and/or copying) mails, bookmarks and preferences?" The answer to this one is about to get a lot easier. Tomorrow's Firefox build will contain import features that should help you easily migrate from the Mozilla browser to Firefox. If you just can't wait for tomorrow, or you want to use the 0.8 release, it's really quite simple to just copy over your bookmarks file. For Mail, it's as simple as copying your mail folders from your Mozilla profile into your Thunderbird profile. The Thunderbird FAQ has some slightly outdated (I think the paths are no longer absolute, I could be wrong) instructions on migration.

Fabiano Guilherme de Souza asks why we don't bundle Flash with Firefox. There are probably a couple of reasons. The first, and I assume most important, is probably legal. Mozilla applications are distributed under the MPL license and bundling a commercial product, owned by another company, with Firefox will probably require some legal maneuvering. I'd like to see flash ship with Firefox, too. In the mean time, it's not terribly difficult to install if you don't have it and if you already had it installed for some other browser, Firefox should just use that.

Joe Dunsmore questions, "Why is there no easy way to disable the javascript that blocks a user from right clicking on a webpage without disabling all javascript?" Well, Joe, it turns out that sites block the context menu using various techniques so doing something as simple as using our Configurable Security Policies to set user_pref("capability.policy.strict.Window.oncontextmenu", "noAccess"); probably won't get them all. This is being tracked as Bugzilla bug 86193 and maybe I can get Christopher Aillon to guest next week on Ask Asa to go into more detail (though he's talking with JST about it at this very moment so maybe he'll have solved the problem by then.) You could certainly try using configurable security policies to block the various common website tactics but my guess is that you'd start to break legitimate uses too. update: Patch attached :D

Joe also asks if we can bundle the open source flash equivalent. I don't know a thing about this plugin so let me turn around and do an "Asa Asks" for this one. Can any of you who have experience with swfdec let me know how complete and how functional it is?

gearbomb asks, "What do you think of the enterprise mission? And have you seen any photos from the MERs that looked like artifacts?" For those of you who don't know what Enterprise Mission is, well, it's a bogus space-alien conspiracy theory website that won't let go of the "face on Mars" and other long-dismissed "evidence" of extra-terrestrial civilizations within our solar system. Does that answer the "what do I think of it" question? For the second part of your question, yes, I have seen photos from the MER camera that look like artifacts. I've seen photographs of our landers which certainly are 'artifacts', I've seen photos the rovers have taken of themselves (they're sort of artifacts, aren't they?) and I've seen photographs of bits of debris that we carried to Mars scattered around the landing sites. Have I seen any images of objects which lead me to believe that advanced civilizations exists on Mars? Nope :)

There have been several requests for descriptions, or better yet photographs, of the Mozilla Foundation office and its contents (the bridge and people) so here you are, have a look at the partially reconstructed soda-can bridge in the Mozilla Foundation office, and because I'm so vain, here's a picture of me at Developer Day. Both photographs courtesy of JST's Nikon (drool) but I've whacked them way down in size and color so you won't be able to appreciate how awesome JST's camera really is. (Bonus pics from my little digital: my desk, dbaron and pavlov, developer day gathering, and leaf and myk.)

Arnaud asked about Mozilla support for DocBook, specifically if I thought a couple of DocBook support bugs would be fixed any time soon. My answer is "we're accepting patches." :D

Mike asked, "Space Rotini: Mars Fossil or strange Rock Bubbles?" and I'll pick "c) none of the above." I think the infamous "rotini" is actually just a trick of light. Remember that we're talking about the Microscopic Imager here, so that entire field of view is just 31 mm across. That makes the "rotini" about 1 mm long and about 1/4th of a mm wide. It's nothing, literally.

backpack wonders, "what missions to the outer planets NASA has in the works, if any. I know Cassini has almost met up with Saturn, but will there be further exploration missions headed that way in the forseeable future?" Yes, Cassini is the nearest term exciting mission. It's scheduled to arrive at Saturn in just 118 days. I can't wait. The interest seems to be on Mars, Earth, the Moon and the Sun, these days so there isn't a lot in the immediate future in store for the outer planets. One interesting bit of news is that Ulysses is back at Jupiter (a decade later) and gathering some interesting science there for the next month or so. A lot further out, NASA's Pluto - Kuiper Express Mission, which will study Pluto, Charon, and the Kuiper Belt, just cleared the hurdle of initial funding last month but it wouldn't launch until 2006 at the earliest and arrive at Pluto sometime in mid-2015.

Oh, and someone asked why Boris was grumpy and rude. The answer is that he isn't. Thanks for playing.

Oh, and no one asked, but I thought I'd mention it anyway. I've blogged over 130,000 words so far in 2004. Crazy.

Last Wednesday I answered most of the questions posed on the original "ask asa" post. I also solicited new questions there and a few of you responded. As long as there's interest, I'm going to make this a regular Wednesday feature here at adot's notblog.

So, if you want to get a question in for this week's installment, post it to the comments here or at last week's answers post. Time is short and there have been some large events in Mozilla and Mars news this last week so get your questions in soon.

also blogged

| 3 Comments

The Blinne Blog also blogged the briefing and has caught some bits I missed.

There are lots of excerpts from the press releases and the wire stories but I'm not seeing much for original content covering the news. If any of you see good stories around the blogoshere, please let me know. Thanks.

Oh, and the official press release is here.

nasa press briefing

| 4 Comments

These are really, really, really, rough notes from the press briefing. I recorded the stream by my connection sucked. Maybe I'll clean them up this evening if I can. The big news in one sentence: large amounts of groundwater were necessary to have formed the bedrock at Meridiani Planum. Here's my notes:

Dr. Ed Weiler: three and a half years ago, several of us on this stage to tell you about our plans to send two rovers to Mars to investigate water on Mars. We'd just suffered two failures. You're about to hear that Opportunity has landed in an area of Mars where liquid water drenched the surface and was around for a habitable time. Today's results are a giant leap.

Steve Squyres: Ever since Opportunity touched down on Jan 24 we saw this marvelous outcrop right in front of us we've been trying to puzzle out what it has to tell us. For the last two weeks we've been attacking it with everything we have. Every piece of our payload have been used. Over the last couple of weeks the puzzle pieces were falling into place. We've concluded that these rocks were soaked in liquid water. Were they laid down in liquid water? we don't have an answer yet. Were they acted upon and altered by liquid water. We believe yes. First, the little spherules like blueberries in a muffin are embedded int his rock and weathering out of it. Three ideas, lapilli, little volcanic hailstones, one possibility. Two, droplets of volcanic glass or impact. We've looked at these things very carefully. Probably concretions. If so, it's pointing towards water. Second piece of evidence is that when we looked at it closeup, it was shot through with tabular holes. Familiar forms. When crystals grow within rocks, precipitated from water. If they're tabular, as they grow you can get tabular crystals and water chem changes and they go away or they weather away. Next piece of evidence comes from APXS. We found it looked like a lot of sulfur. That was the outside of the rock. We brought with us a grinding too, the RAT and we ground away 2-4 mm and found even more sulfur. Too much to explain by other than that this rock is full of sulfate salts. That's a telltale sign of liquid water. Mini-TES also found evidence of sulfate salts. Most compelling of all, the Mossbauer spectrometer in the RATted space showed compelling evidence of Jerosite, an iron sulfate hydrate. Fairly rare, found on earth and had been predicted that it might be found on Mars some day. This is a mineral that you got to have water around to make. We believe that this place on Mars had a groundwater environment that would have been suitable for life. Habitable place at one point in time. This is a place where minerals precipitated out from liquid water. One of the best kinds of rocks that preserve evidence for life are rocks where minerals precipitate and trap and preserve evidence of past life. These are very, very interesting rocks. Just as a teaser, we have tentative evidence that not only were they modified by liquid water, they may have been laid down by water. Once we have finished up on El Capitan, we're driving to Big Bend and we'll take some very detailed pictures to try to determine whether these rocks were laid down in liquid water.

John Grotzinger: Geological field trip to el capitan location. All the observations fit together in a very specific way to narrow down the case for a specific story of what we have. This movie will show opportunity ledge, about 20 meters wide, 20-35 cm high. Color change, fault, ubiquitous layering. El Capitan, has well preserved textures and layering. We see lamination, the voids steve was taking about and the blueberries. Another still shows this fine layering and one of these spherules. Laminations don't deflect around it. These spherules are concretions that result in the displacement of materials rather than pushing the layers down like they would if they were lapilli. Also, randomly distributed, not in layers. These tabular voids show greatest width in the middle and tapering at the ends. Reminds us of gypsum. Requires water percolating through the pore network. Their absence may be evidence of fluid erosion too. In the next slide, we have where we're going in the future, 7 days of experiments to evaluate rock Last Chance. See layers that are cross-bedded, (only a hint) it requires sediment particles be moved in a flowing current, could be air, could be water, could be volcanic gasses. Experiments designed to help test that out.

Benton Clark: Spectrometer science. You won't see pictures, instead see graphs, the two German instruments and mini-TES. Before we landed we had picked this area because TES on MGS had said it had interesting mineral content. First chart shows the APXS samples. Red is the original soil right off the lander. In the blue dots you see sulfur is much higher in the outcrop. Chlorine about the same. Bromine showing up on the right side. We had known that sulfur was high on Mars from Viking. Inferred at that time that it could be salts. When we analyzed rocks at Pathfinder and Gusev, the rocks didn't contain salts. At Meridiani that was different. At Meridiani, chlorine in green is small, sulfur is in yellow. Sulfur jumped up at McKittrick before we RATted. In third bar, the sulfur jumped up (after RAT) and at Guadalupe, we have the record on Mars, almost 5 times the amount. We interpret this sulfur to be sulfate so we expect magnesium sulfate, epsom salts, on Mars with less water it's called kesorite. Kesorite plus the chlorides add up to a salt concentration that may be 40% of the outcrop. This is astounding. No longer can be considered to be a volcanic construct. Only way you can form such large concentrations is to dissolve it in water and have that water evaporate. Further evidence is that the chlorine didn't go up. Also, bromine showed up high. Up at Guadalupe we have highest level of sulfur and down at McKittrick we have highest level of bromine and chlorine. We have an evaporative sequence. There should be additional salts in such a sequence. Next graph is the Mossbauer spectrum that has detected 4 types of minerals in McKittrick sample, including Jerosite, a large fraction of the iron, about a third. It forms in water at a fairly acid PH. Finally we have mini-TES that has looked inside RAT holes and found evidence of sulfate in the spectrum.

Joy Crisp: After a more close-up investigation we're going to want to broaden our view. How extensive was this liquid water. Our near long term plans include looking at younger material above the outcrop and on nearby plains. We'd also like to drive to Endurance crater. This graphic is a rover Pancam view of Endurance and a smaller crater between it and the rover. This MOC image shows large crater with bright rim around it. We're interested in finding out what that bright rim is made of. We've attributed it to being the older etched unit that underlies the hematite unit across the Meridiani plains. Is it the same as the outcrop bedrock? Endurance is 30 m deep so we would like to visit it. There's mottled plain to the south that we'd like to get to if possible. This MOC image is 3 miles across showing mottled terrain. We would like to find out if the bright material is the same or different from our outcrop rock. We will drive around and try to determine the water history for this area.

James Garvin: What an amazing time to be alive and doing science on Mars. What immediate scientific impact on our program. How can we use these results to target our program. Mars Reconnaissance Orbiter will do remote sensing from orbit and look for new landing sites. We have earth laboratories and we'd like to bring some of that stuff home to earth. We now have a possible target for a Mars sample return mission. These rovers are the first step to take us to see the new Mars.

Q. Does the data suggest how long the water was there or how deep?

Steve: I want to again differentiate between a standing body of water and water percolating up. We don't know if this bedrock was created in standing water. Best way to address the age problem is to see how extensive this stuff is, how thick this layer might be. Best way is to bring some of it back.

Q. How might you modify what you were going to do given more money and these findings?

James: over the last two years we have worked with our science community to craft a series of missions over the next decade. We've crafted those based on forecasting science. We have resilience in the science elements to follow up on these results from orbit and landers. blah, blah, Mars Lab, Astrobiology Lab, Sample return...

Ed. There are three things in the next decade. Sample return is clear. Both for scientific and in prep for human landings. Clear that we need in situ astrobiology missions. Third priority is to land some things that will prepare for human landings, test for toxicity, etc.

Q. any more on age?

Steve: getting at the duration of this specific formation event is going to be very hard. I'm intrigued by the possibility that something cool could turn up at our other landing site. If you want access to geologic information on these flat plains you need a hole. We got lucky at Meridiani. At Gusev, we landed 250 meters from a crater. These two sites are of different ages so if we find evidence of water at Gusev that would be interesting.

Q. If you found rocks like this on earth what are the changes you'll find life there.

John: I think the answer is simple, on earth, finding fossils in ancient rocks is very rare. Preservation is the problem. You target strategies to go looking for rocks where things would be preserved. This location could be a good candidate. You need to get around and look at a lot of rocks and different samples because there's a tremendous bias for preservation. It's a challenge.

Ben: In addition to physical evidence you can have chemical indications. (lost signal, sorry)

Q. what are key pieces of evidence for soaking rather than small amounts.

Steve: massive quantities of sulfates. with this quantity you have to have had a lot of water involved.

Q. Given geological context, if you find there was standing water, what does that imply about how large a body of water?

Steve: that's part of the reason I haven't fallen over that particular cliff yet. It's difficult at this site to point to a well defined basin. Mars can change its topography, eroded, tilted tectonically. This stuff may be fairly old. Fact that we don't see a well-defined basin I don't think argues compellingly against these rocks having been laid down in liquid water.

Q. Are there any geologic formations on earth that are similar.

John: whether this rock is the result of the accumulation of basaltic ash for which Hawaii is an example or if it precipitated from a salty sea. In another week or ten days we'll be able to get at that.

Q. Don't know how long ago the water was there? Millions of years, centuries?

Steve: when I said I didn't know, it's because I didn't know. In order to date this stuff you need laboratory quality equipment. In order to say how long it was there you need a complete stratigraphic section and we've only seen a small part.

Q. How long before you get up to Endurance crater, and secondly, what about the hematite?

Steve: it's gonna take us another week or 10 days in this crater. We want to go to Big Bend and look at ripples and cross-beds (if that's what they are). We don't yet know what those spherules are. There's a depression filled with these guys and we're going to go there and try to get a handle on what they're made of. Then we head out. As soon as we crawl out we'll find new and interesting things and want to take a good look around for a few sols then head across the countryside towards the crater. I think we'll make good time. Spirit is far out ahead but I think that's gonna change. We're looking at 50-100 meters per day at Meridiani. Several weeks before we get there. That is gonna be one heck of a view. With respect to the hematite, I've always looked at it as a chemical beacon visible from space saying that something interesting chemically happened here. There certainly is a lot of hematite here. I don't think we'll have a good answer until we crawl out of this crater. Mini-TES says highest concentration is above the crater.

Q. What might have happened here, lakes, rivers?

Steve: two possibilities. One, volcanic eruption and ash layers with lots of pore space then water percolates through that rock and deposits sulfates. Spherules grow, crystals grow and go away. Fundamentally alteration of the ash. Totally different scenario, you had a salty sea with currents, maybe waves, then as that stuff evaporates away, salt crystals settle out. Maybe that happens multiple times. Then you have water percolate through them and spherules and crystals grow. We may not find out.

Q. what do you mean habitable.

Steve: an environment suitable for life as we know on this planet. With respect to what this tells us about the atmosphere, not a whole lot. Could be groundwater, no surface water. If that's the case then it won't tell us a whole lot about climate. There's nothing like this going on Mars today.

Q. Can you say specifically what measurements in the next few sols to determine precipitated or percolation.

John: first look at last chance to examine some form of cross-bedding. Different geometries can tell us if there was a flow of fluids or an accumulation of sediment in a current. Minerology and geochemistry we hope to address formation process. The Dells and Slick Rock next. Most abundant set of MI pictures, some 2x10 images.

Q. What do we know about blueberries at this point.

John: We're going to wind up at the berry bowl, a hollow with lots of berries touching each other. There we can hopefully get their content.

Ben: keep in mind that we've only measured two spots on this outcrop and they're different.

Q. Cross bedding indicates strong current environment.

John: we're uncertain about the cross-bedding. We're hopeful and we're allocating time to test it. If there is cross bedding then we have to look at geometry in relation to grains that make them to understand the regime that created them.

Q. (missed)

Steve: at Bonneville we'll have access to a wider range of materials. Right now on the surface we're seeing basalt so there's volcanic activity. We need to get access to a wider range of materials.

Q. Is there any operational consideration that might constrain new outline of science.

Joy: no operational limitations. We foresee at least several more months. Something may break eventually and we have no way of predicting that. In terms of energy, thermal and mobility we don't see any reason why we can't keep going.

Q. Are you able to analyze rocks at opportunity to see if the rocks are basaltic?

Steve: By looking at the elemental and mineral composition we can say with a high-degree of probability at Gusev that the rocks are basalt and with certainty at Meridiani that it's not a pure basaltic rock.

Ben: one of the things we haven't done at Opportunity is measure a dark rock and there are some at the surface.

Q. If the water on Mars is briny, could it continue to exist?

Steve: it could, but you might have to go pretty deep to find it, 10s 100s of meters, maybe. As you go deeper it gets warmer.

Q. Are you announcing that water was stable on the surface of Mars in the past.

Steve: This could have taken place beneath the surface. This could be a groundwater thing.

Q. If there are organisms that like salt and there are microbes in Antarctic ice, can you look for life on Mars?

Ben: We do not analyze organic compounds on this mission. There will be future missions that may analyze organic compounds.

James: We can speculate but we don't know. Pessimistic view is that liquid water might be really deep.

Q. Some scientists suggest water could be near the surface in ice and might be released at an impact.

James: Phoenix mission targeted for ice-bearing soils will explore ice using its tools.

Ben: an impact crater could create conditions that would be warmer for thousands of years.

Q. Personal feelings about this important findings?

Steve: It's been interesting to watch all of the reactions. We all went in with our own prejudices, hopes, and desires. As we've accumulated the evidence the puzzle was coming together. It's been interesting to watch as we all came to the conclusion that water was involved. Some people made the leap right away, others took longer. It feels good. We worked for years to make this happen. On the other hand, we're just getting started. Maybe much better stuff out there. We're enjoying this but also chomping at the bit to get out there and look at more.

Ben: This group of scientists and engineers have been working unbelievably hard. Every day discoveries. Just the tip of the iceberg on this stage.

major announcements

| 12 Comments

Today is BugDay and so I'm not sure I'll be able to break away from the Mozilla bug hunting and squashing activities, but if I can, I'll see what I can do to cover the "big news" that's expected out of NASA this afternoon.

If I'm not blogging the press conference live at 11 am PST, then check back later in the evening for "rough transcripts" because I'll certainly be recording the NASA feed.

update: My sources close to the science team are suggesting that this will be a significant briefing.

prediction: My predictions for this press briefing are that they'll announce they've got a pretty good idea about the local geology at Opportunity's crator in Meridiani Planum and that they are fairly confident they know which rocks at the site contain the coarse gray hematite they came looking for and that it (or its precursor, goethite) most likely formed in large bodies of standing liquid water. If we're really lucky, they'll also have news about the liquid water (in brine) near the surface of the rover (possibly both). I think the chances that they'll have anything to say about life, other than that water was or is there in abundance, are pretty slim.

mars in 3-d

| 1 Comment

It's been a little while since I plugged the really nice 3-d image work over at Thom Bone's Mars Site - Gorgeous 3D Pics from the Spirit and Opportunity Rovers!. Grab your red and blue or red and cyan glasses and head over to see Mars up close and personal. Great work, Thom!

mars excitement

| 2 Comments

Space.com has an interesting article on the recent "buzz" around the JPL facilities. It's worth a quick read, though the last few paragraphs with comments from Gilbert Levin are sort of over the top.

See also:
Mars Blog
ATSNN
MainlyMartian

blogs starting to make a dent

| 1 Comment

Via Matthew Yglesias I've learned of a Pew study (sounds like a national study, not worldwide) that says "Eleven percent of Internet users report visiting blogs written by others. And of these blog readers, a third report posting to or commenting on the blog entries that they have read. "

That's a lot of people. Even more interesting, I think, is that the study finds that 13% of those surveyed maintain their own websites. If that's the case, then it looks to me like most people maintaining personal websites are doing so with blogs.