Mozilla DevCenter
advertisement

Sponsored Developer Resources

Atom 1.0 Feed RSS 1.0 Feed RSS 2.0 Feed

Related O'Reilly Books





What Is Firefox What Is Firefox
Brian King provides a brief look at Firefox's origins and evolution, and then dives into its support for web standards like CSS and XML, its debugging and extension capabilities, and some cool new features in the upcoming 1.5 release. If you're considering a switch to Firefox, this article may help make the decision for you.


Mozilla as a Development Platform: An Interview with Axel Hecht  Axel Hecht is a member of Mozilla Europe's board of directors, and a major contributor to the Mozilla project. At O'Reilly's European Open Source Convention (October 17-20), Dr. Hecht will be talking about Mozilla as a development platform. O'Reilly Network interviewed Dr. Hecht to find out if the long-held dream of Mozilla as a development platform was about to come true.   [O'Reilly Network]

A Firefox Glossary  Brian King, with some help from Nigel McFarlane, covers everything from about:config to "zool" in this fun, fact-filled Firefox glossary. It's by no means exhaustive, but you'll find references to specific chapters or hacks throughout the glossary to Nigel's book, Firefox Hacks. When you're ready to dig deeper, check out his book.   [O'Reilly Network]

Important Notice for Mozilla DevCenter Readers About O'Reilly RSS and Atom Feeds  O'Reilly Media, Inc. is rolling out a new syndication mechanism that provides greater control over the content we publish online. Here's information to help you update your existing RSS and Atom feeds to O'Reilly content.  [Mozilla DevCenter]

Hacking Firefox  This excerpt from Firefox Hacks shows you how to use overlays (essentially hunks of UI data) to make something you want to appear in the Firefox default application, perhaps to carry out a particular function of your extension. For example, you might want to add a menu item to the Tools menu to launch your extension. Overlays allow existing Firefox GUIs to be enhanced.   [O'Reilly Network]

Mozile: What You See is What You Edit  Most modern browsers don't allow you to hit "edit" and manipulate content as easily as you view it, WYSIWYG-style. Mozile, which stands for Mozilla Inline Editor, is a new Mozilla plug-in for in-browser editing. This article by Conor Dowling provides an overview of Mozile and what in-browser editing means.
  [ Mozilla DevCenter]

The Future of Mozilla Application Development  Recently, mozilla.org announced a major update to its development roadmap. Some of the changes in the new document represent a fundamental shift in the direction and goals of the Mozilla community. In this article, David Boswell and Brian King analyze the new roadmap, and demonstrate how to convert an existing XPFE-based application into an application that uses the new XUL toolkit. David and Brian are the authors of O'Reilly's Creating Applications with Mozilla.   [Mozilla DevCenter]

Remote Application Development with Mozilla, Part 2  In their first article, Brian King, coauthor of Creating Applications with Mozilla, and Myk Melez looked at the benefits of remote application development using Mozilla technologies such as XUL and web services support. In this article, they present a case study of one such application, the Mozilla Amazon Browser, a tool for searching Amazon's catalogs.   [Mozilla DevCenter]

Remote Application Development with Mozilla  This article explores the uses for remote XUL (loaded from a Web server), contrasts its capabilities with those of local XUL (installed on a user's computer), explains how to deploy remote XUL, and gives examples of existing applications.   [Mozilla DevCenter]

Mozdev.org Made Easy  Now that mozilla.org is about to release Mozilla 1.2 and Netscape has come out with the latest version of their own Mozilla-based browser, Netscape 7, this is a great time to see what other people are building with Mozilla's cross-platform development framework. Here's a little history about, and a roadmap to, mozdev.org.   [Mozilla DevCenter]

XML Transformations with CSS and DOM  Mozilla permits XML to be rendered in the browser with CSS and manipulated with DOM. If you're already familiar with CSS and DOM, you're more than halfway to achieving XML transformations in Mozilla. This article demonstrates how to render XML in the browser with a minimum of CSS and JavaScript.   [Mozilla DevCenter]

Roll Your Own Browser  Here's a look at using the Mozilla toolkit to customize, or even create your own browser.   [Mozilla DevCenter]

Let One Hundred Browsers Bloom  In this article, David Boswell, coauthor of Creating Applications with Mozilla surveys some of the more interesting, and useful, Mozilla-based browsers available now.   [Mozilla DevCenter]

Using the Mozilla SOAP API  With the release of Mozilla 1.0, the world now has a browser that supports SOAP natively. This article shows you how Web applications running in Mozilla can now make SOAP calls directly from the client without requiring a browser refresh or additional calls to the server.   [Web Development DevCenter]





Today's News
July 09, 2008

Nagappan: Announce: Linux Desktop Testing Project 1.2.0 released Highlights of this release
* Performance fix, which improves the LDTP execution time drastically
* 3 crasher fixes in LDTP execution engine
* LDTP editor bug fixes reported by Shreyank Gupta
* Added 2 new API required for VMware Workstation automation
* API manual is updated
* Moved from CVS to GIT - Thanks to FreeDesktop administrators
* Thanks to Ubuntu automation team for using / evaluating LDTP
* LDTP is being evaluated by the project Open Source based Desktop Benchmark of the Linux Solutions Group e.V. (LiSoG) in Germany, Switzerland and Austria [Source: Planet Mozilla]

Andrew Sutherland: gloda’s first (primitive) visualization

Author activity over time, current thread in blue, selected message in darkest blue.

A primitive visualization augments the gloda “other messages by author” listing by showing the messages sent by the author over time.  Messages are stacked by day.  The currently selected message is in darkest blue and also very wide.  Other messages from the same thread/conversation are in lighter blue and less wide.  Messages not in the conversation are light grey and rather narrow.

It’s not clickable, it lacks any form of scale or any feedback at all, and there are scaling issues.  (If anyone wants to save me the effort of figuring out how to get the canvas to maintain a 1:1 pixel mapping to the actual display and still ‘flex’ by adding/losing pixels, please do drop me a message or leave a comment.)  These will all change, but not yet.

I’ve pushed the changes to the mercurial repos and updated the stable tag, but I’m not publishing updated xpi’s, so you’ll need to roll your own if you care.  (The DB schema has not changed and so does not need to be blown away.)

[Source: Planet Mozilla]

Jane Finette: Mozilla Events Triage call Jul 9th - please join in


Reminder - we have a Mozilla Events Triage Call tomorrow July 9th, 2008 at 10 a.m. PDT (that’s 6pm GMT, 7pm CET)

Please join us!

Dial-in is 650-903-0800, ext 91, id 248.

Here is the agenda:

* OSCON:
o Booth
o QA BoF
o Community Party
* Black Hat:
o Milk & Cookies Party
o T-Shirt
* Jornadas Regionales de Software Libre
o Need to determine preferred speaking day for Chris Hofmann
o Any other needs from Mozilla Argentina for the event?
* Congresso Estadual de Software Livre – Ceará (CESoL-CE) - August 19 – 23, 2008
o Need to determine preferred speaking day for Chris Hofmann
* Test Writing Workshop

[Source: Planet Mozilla]

QMO: Thunderbird Bugday, Thursday 07/10 - Help us triage Thunderbird bug reports!

2008-07-10 12:00
2008-07-11 02:00
Etc/GMT-7

Hello Thunderbird Enthusiasts!! *Join us this Thursday, and every Thursday, for great bug triage*

July 4 and Canada Day are past. Spring is gone. But the bugs are not - they're still here!

You don't need special skills - experienced staffers are available to help you in #bugday IRC.
And bug day is fun!

See http://wiki.mozilla.org/Thunderbird:Bugdays for schedule (spread throught the day) and simple
steps to participate.

read more

[Source: Planet Mozilla]

Meeting Notes from the Mozilla community: Mozilla Project Meeting Minutes: 2008-07-07

WeeklyUpdates/2008-07-07

From MozillaWiki

« previous week | index | next week »

Meeting Details

  • 1:00pm Pacific time (20:00 UTC until November 2, 2008)

  • Mozilla HQ, 1st floor conference table
  • +1 650 903 0800 x91 Conf# 8600 (US/International)
  • +1 416 848 3114 x91 Conf# 8600 (Canada)
  • +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
  • join irc.mozilla.org #staffmeeting for backchannel

note: all participants are muted automatically; if you want to talk, press *1 to un-mute yourself


Friends of the Tree


Development Updates


Fx 2.0.0.15 / Fx 2.0.0.16 / TB 2.0.0.16

Firefox 2.0.0.15 came out of the oven like a warm apple pie last Tuesday. We attempted to have a post-mortem today, but have instead moved it to Wednesday at 11am. Please add your agenda items to the wiki page.

Firefox 2.0.0.16 is almost ready for baking to our beta channel. We intend to pop it in the oven tomorrow.

Thunderbird 2.0.0.16 is in the hands of build who have started the process. Builds are in process and should be available for testing tomorrow.


TB 3

  • 3.0alpha2 code freeze is Tuesday evening, 23:59 Pacific

  • We’ll be moving forward with the proposal for shipping Thunderbird 3. We may shift some milestone dates around a bit; mozilla.dev.planning discussion forthcoming.


Gecko 1.9.1

  • For a great update of what’s going on in Gecko, take a look at last week’s Gecko meeting notes. Highlights include:

    • New video backends (working on them!).

    • More Acid3 tests passing.
    • SMIL
    • SVG CSS: SVG Gradients and Patterns as backgrounds for HTML elements, etc.
    • Worker Threads
    • Tons of JS performance improvements.
    • Offline versioned app caches.
  • Look here for interesting queries related to Gecko 1.9.1.
  • Still 17 1.9.1 blockers.
  • 87 wanted bugs
    • 25 P1s. These are bugs we feel would really, really make a good release if we had a solid handful completed.

    • 23 P2s. These are medium complexity bugs/changes that are nice to have.
    • 20 P3s. The lowest priority bugs for this release. These are the ones that we will definitely take, but the others take priority.


Firefox 3


Mobile

  • implementing UI for Fennec

  • on track for M5 release on Friday


IT

  • working with build on unit test issues

  • build-out of new mini farm
  • kernel updates/rhel 5 updates coming this week
  • mrz and oremj out this week - IT response may not be as fast this week


Release Engineering

  • Intermittent unittest failures: code/framework/machine? bug 438871
  • TB20.0.16 automation
  • FF 2.0.0.16 *and* FF3.0.1 on the same day
  • proposed changes to buildIDs

  • out of office:

    • nthomas, joduinn

    • please file bugs to mozilla.org:ReleaseEngineering


QA

Firefox/Thunderbird 2.0.0.x [ss, abillings, juanb, hali]

  • Firefox 2.0.0.15 - Completed final release testing and shipped on Tuesday, July 1st!

  • Started testing Firefox 2.0.0.16. See test plan [abillings]

Firefox 3.0.1 [ss, tchung, marcia, juanb, hali]

  • Created the Test Plan [tchung]

  • Received builds on July 2 and started bug fix verification, smoketests, BFTs, L10n spot checks, and update testing. Results.
  • Expect to release to Beta on Thurs July 10th

Firefox 3.0/3.1

  • Feedback monitoring: Worked with contact at ebay to help resolve bug 441779. Escalated Yahoo Mail issue that was causing lots of issues- bug 443280. This was a high visibility issue that was hitting lots of users suddenly. [tchung, marcia, tomcat]

  • Accessibility: Developed fix for bug 442659 having to do with ARIA menus. Verified landing of bug 439566. With this, screen readers using IAccessible2 or ATK now have access to all CSS display properties (except for display: none, which we don’t provide accessible objects for at all). Landed patches for bug 442862 and bug 442648, giving us a set of tests for HTML and XUL textboxes and textareas. [marcoz]

WebDev Testing [stephend]

  • AMO: Continued developing Selenium-based search test suite. Wrote documentation on creating/executing Selenium IDE scripts via Selenium RC

  • SUMO: Verified 12 FIXED bugs
  • General: Verified 39 bug fixes

Test development and automation

  • Gristmill: Made progress with Windows events handling, observer, and JSBridge. Working on a library called ChromeLib.js to be used to manage windows and tabs via fuel/xpcom interfaces in MozMill. Developing initial proof of concept scripts [mikeal, adam, ctalbert, hali]

  • Test Coverage analysis. Completed first hack at extracting the distribution of tests in the source tree. [martijn]
  • Minotaur/L10n: Some progress automating the testing of preferences for locales, now that Build has automated the building of locales and hand-off to testing processes. [ctalbert]
  • Mobile: progress on geo-location testing and running mochitest suites on fennec. [harthur, ctalbert]
  • Sisyphus JS test framework: Fixed bug 443154 (do not require js tests to be on path) and bug 443156 (generalize std::bad_alloc -> out of memory post processing) [bc]

Community

  • QMO Redesign- Research on Drupal AHAH (form AJAX feature), extended QMO Bugzilla module and outlined a more flexible version [paulc]

  • Working on Intro to QA BOF for OSCON [tchung, tony, ctalbert]
  • Provided patch for bug 441991 which, in conjunction with bug 443037, will allow the Calendar team to do some better ARIA magic with Calendar once they move to Gecko 1.9.1. [marcoz]
  • Spent a lot of time testing the WebVisum extension, writing a review on it, and in general getting this very promising extension off the ground. This extension is probably going to be as important to visually impaired users as Firebug is for web developers. Also completed leak testing of this extension and found some serious leaks. [marcoz, tomcat]
  • No test day last week. We are switching to holding these every two weeks until 3.1 milestone releases.


Security


Marketing/PR

PR

Events

  • Events Triage call on Wednesday July 9th at 10 a.m. PDT. Dial-in: 650-903-0800, ext 91, pass 248.

  • Overview of OSCON activities here.

Download Day

Spread Firefox Affiliates Program


Support

  • No updates, except 0.6 live push was delayed and will happen tomorrow (Tuesday)

  • Bug triaging session for 0.7 tomorrow [1]


Metrics

  • no updates


Evangelism

  • Making sure that JavaScript, DOM, CSS, XML, SVG bugs are getting into the proper triage queues for 1.9.1.

  • collecting feedback on the MDC dekiwiki test site, via thread on dev-mdc
  • starting work on a survey related to what people find most and least useful about this very weekly meeting, to see if we can make it even more effective as a way of coordinating the project


Mozilla Labs


Webdev, Add-ons, AMO


L10n

  • Builds we are working on launching (as betas) for 3.0.x: Assamese, Bengali, Estonian, Esperanto, Galician, Hindi, Icelandic, Kannada, Kinyarwanda, Latvian, Malayalam, Marathi, Nepali, Thai

    • Shout out to all the localizers behind these builds who are working towards launch (in same order): Amitakhya, Runa, Sander, Eduardo, Suso, Rajesh, Christjian, Shankar, Stephen, Raivis, Joyce, Sandeep & Prithi, Basanta, Isriya


Foundation Updates

  • Grants and related expenditures

    • Peter Jaros completed work on his Camino scriptability project (a 2007 grant); for more information see bugs 390072 (preliminary support), 385989 (windows and tabs), and 390846 (bookmarks).

    • Frank received and is reviewing two new accessibility-related grant applications.
  • CAs and related issues

    • Frank started the first public comment period for EV-related requests from GlobalSign.
  • Conferences

    • Zak continued preparing for the FOSSCoach event at OSCON.
  • Website

    • David continued work on updating www.mozilla.org site.
  • Other

    • Gerv continued work on projects from last week, including tracking Google Summer of Code work for Mozilla-related projects, updating the public suffix list, working toward the proposed Bugzilla reorganization, review of a new proposal for site security policies, a proposal for replacing the Despot system, and various other things. David continued work on brochure project.
  • Upcoming activities

    • David, Gerv, and Zak will be attending OSCON (July 21-25 in Portland OR) and the Firefox Summit (July 29-31 in Whistler BC). Frank will be attending the Firefox Summit but not OSCON.

For more information please see the individual status reports from David, Frank, Gerv, and Zak.


Internship update

We have the following interns for today’s internship presentations:

  • Clare (Firefox)

  • Hasham (QA)
  • Juliana (Marketing)
  • Jacob P. (Web Dev)
  • Brian (Web Dev)
  • Maria (Labs)
  • Eric (Platform)


Roundtable


Other Business

[Source: Planet Mozilla]

Jan Odvarko: List of Firebug Extensions

Have you ever been interested in what extensions are available for Firebug? If yes, take a look at what I have found. Frankly, I was quite surprised how many Firebug extensions already exists out there.

  • YSlow
  • Firecookie
  • FirePHP
  • RainbowForFirebug
  • Jiffy
  • Firequark
  • LiveCoder
  • PixelPerfect
  • FirebugCodeCoverage
  • Firebug Net Panel History Overlay
  • Fireclipse
  • Chromebug

(more...)

[Source: Planet Mozilla]

Taras Glek: Where is the sanity in the C++ std library?

Dear lazyweb,

Please explain to me why the following code works the way it does. From looking at the following code and stringstream::str(), stringstream::str(string) docs the behavior of the following code does not make sense to me.

#include <sstream>
#include <iostream>

using namespace std;

int main(int argc, char**) {
stringstream ss(”foo”);
cout << ss.str() << endl;
ss << “bar”;
cout << ss.str() << endl;
//cout << ss.str() << endl;
ss << “more”;
cout << ss.str() << endl;
}

Why is doing << after str(string) causing this stringstream to loose the initialization string? What possible API usecase would justify such behavior?

For the curious, output is:

foo
bar
barmore

[Source: Planet Mozilla]

John Lilly: Global Voices

Rebecca and Joi have each made postings (here and here) about the Global Voices Summit that happened a couple of weeks ago in Budapest, and it sounds like it was an incredible, wonderful event. I’ve been tracking Global Voices for just a little while, so not long enough to know the history, but long enough to know that it’s a wondrous thing that shows so much of the global promise of the web. The idea is simple: it’s a set of bloggers from all around the world, collected in one stream. The impact is profound: you get a sense of some of the real-time feelings & thoughts & perspectives that are happening around the world, not mediated through our traditional media or governmental channels.

The last couple of years I’ve been lucky to do some traveling for Mozilla — in particular to China, Japan, and Europe — and have found my perspective on what the world looks like (and can/should look like) changing greatly. (And I’m currently in the middle of Fareed Zakaria’s excellent new book The Post-American World on this subject.)

I’m just repeatedly blown away (and sometimes overwhelmed) by what Global Voices is doing — it seems to me a necessary point of view in a world where national boundaries seem more & more artificial and sometimes obstructive to the way people are having conversations and getting things done.

[Source: Planet Mozilla]

Songbird: Songbird @ OSCON 2008

Songbird is heading to OSCON 2008!

stevel, pvh, and our fearless leader b0bg0d, will be heading up to Portland, Oregon to spread the good word about the ‘bird. Here’s a run-down of our Songbird activities:

  • stevel will be presenting a talk on Songbird, Thursday 07/24 at 2:35pm in room E146
  • The whole ‘bird crew will be manning a Songbird pod in the Mozilla Booth during the exhibition show on Wednesday & Thursday. We’ll have Songbird posters, stickers, pins, and t-shirts - so make sure you drop by. All proceeds from t-shirt sales will be donated to the Mozilla Foundation, so you can both feel AND look good!
  • Songbird PARTY!!! We’re throwing a party with our friends at Mozilla, OSL, OpenSourcery, Vidoop, and Jive. So make sure you come by our booth and grab an invite (and RSVP here) to Beerforge happening Thursday evening from 8pm to 11pm at the Bossanova Ballroom)
[Source: Planet Mozilla]

Blog of Metrics: Colbert Bump - Firefox 3 Proves its Existence

Many of us at Mozilla and within the Mozilla community were excited when Stephen Colbert gave Firefox 3 his “Colbert Bump” on the day of Firefox 3’s launch (a big thanks to Jonathan Zittrain).  You can watch the video here.

Download Day was a wild success, and we were happy to share some thanks and credit with Stephen.  However, a few questions naturally arose, e.g., what was the direct impact of the Colbert Bump? and could the effect be precisely measured?

Here’s what we did:  we looked at downloads of Firefox 3 by users within the U.S. – and then we drilled down to a minute-by-minute view to see what, if anything, could be detected.  At minute 23 of the broadcast, Colbert said, “Firefox 3 just got the Colbert Bump.”  What happened next?

We saw a big spike in downloads exactly one and two minutes later:

Apparently we’re not the first to find scientific evidence proving the Bump’s effect.  If you’re interested in that previous study by James Fowler of the University of California at San Diego, you can read the complete version here.

[Source: Planet Mozilla]

Mozilla Developer DevNews: about:mozilla — Official World Record, Firefox 2.0.0.15, security metrics, Weave, JavaScript, and more…

In this issue…

Official Guinness World Record!

The Firefox community is the proud holder of a new Guinness World Record. On July 2nd, Mozilla received confirmation from Guinness that we’ve officially achieved the record for the “largest number of software downloads in 24 hours,” with a final total of 8,002,530 downloads. This is another in a long line of wonderful accomplishments for our community. Ever since Firefox was launched in 2004 we’ve relied on Firefox supporters to help spread the word, and we now have over 180 million users in more than 230 countries. It’s an amazing accomplishment, and we’re all extremely grateful. Don’t forget to get your very own personalized Download Day certificate!

Firefox 2.0.0.15 released

As part of Mozilla Corporation’s ongoing stability and security update process, Firefox 2.0.0.15 is now available for Windows, Mac, and Linux. Please note that Firefox 2.0.0.x will be maintained with security and stability updates until mid-December 2008. We encourage you to upgrade to Firefox 3, which is now available at GetFirefox.com. For more information, please see the DevNews blog post.

Mozilla security metrics project

Mozilla has been working with security researcher and analyst Rich Mogull on developing a metrics model to measure the relative security of Firefox over time. The team is trying to develop a model that goes beyond simple bug counts and more accurately reflects both the effectiveness of secure development efforts and the relative risk to users over time. The goal for the first phase of the project is to build a baseline model that can evolve over time. A preliminary version of the project goals and a spreadsheet of the model have been published by the team. These, along with more information about the project, are available through the Mozilla Security blog.

Weave 0.2 development milestone

Weave is a Mozilla Labs project focused on building online services into the browser. The project’s goals are to enhance the new Firefox user experience and increase your control over how you share your personal information between computers, and with other people. Version 0.2 is a major update to the Weave client and to the servers than control it, and has significant new features. For more information, including details about the changes, or to try it out for yourself, check out the Mozilla Labs’ weblog post.

Two new members of the about:* newsletter family

Mozilla has started two new newsletters: about:addons and about:mobile. Strictly dealing with add-on related news and development information, about:addons is targeted at our increasingly large and vibrant addon development community. The more recent addition, about:mobile, is all about Mozilla’s nascent mobile project. Both newsletters plan to publish on a monthly basis, and both are available by email, web, and RSS feed. For more information, including how to sign up, see Mark Finkle’s blog post for about:addons, and Chris Blizzard’s blog post for about:mobile.

Help test-drive the new Mozilla Developer Center!

Eric Shepherd, Mozilla’s Developer Documentation lead and MDC project coordinator, is looking for help testing the new Mozilla Developer Center system and design. Before diving in to help out, it’s important to note that changes made on the test server will not be ported back into the real database. The test version of the site is available at http://devmo.dekiwiki.mozilla.org. For further information and up-to-date details about the state of the server and testing, see Eric’s weblog.

Next generation JavaScripting

Mozilla Labs’ Aza Raskin has posted about “next generation JavaScripting” over on the Labs’ weblog. In it he points to three very interesting recent JavaScript-related projects by folks in the Mozilla community: John Resig’s Processing.js, a port of the Java-based Processing programming language; Atul Varma’s Parchment project, which is a JavaScript-based interpreter for the Z-Machine; and Aza’s own ContextFree.js, a project focused on drawing striking images and making art with minimal amounts of code. Check out the full blog post for more details.

Developer calendar

Monday

Tuesday

Wednesday

Thursday

Friday

Subscribe to the email newsletter
If you would like to get this newsletter by email, just head on over to the about:mozilla newsletter subscription form. Fresh news, every Tuesday, right to your inbox.

[Source: Planet Mozilla]

Mitchell Baker: Sometimes a phone call is the answer!

I had a long talk with Dave Eaves today as a result of a couple of his recent posts which I didn’t quite understand.   It’s fun to find someone explicitly interested in how Mozilla works as well as what we do.  But I was confused, especially by the post on the Manifesto.  It felt a bit to me like a post that said “let’s replace the Manifesto” in order to appeal to an undefined set of people for unknown reasons.  That seemed odd.

I was pretty sure this wasn’t quite what was intended, but I couldn’t figure out what was intended.  Sometimes it really is good to be able to talk to someone, “real-time,” voice to voice — rather than exchange comments back and forth through a blog or IM or email.

Dave’s focus as I understand it now, without putting too many words in Dave’s mouth — though he has read this post in draft form, so I know I’m close — is whether we can make it easier for people  to adopt the Mozilla Manifesto as their own, to figure out what they want to do to move the goals of the Mozilla Manifesto forward.     In particular, for people outside the current Mozilla Communities of Practice and Action to do this.  We can see there are a bunch of people who care about these goals (or goals similar to them, since the Manifesto isn’t perfect) but don’t see their main contribution as building software.  There’s many interesting contributions this group could make to an open, transparent, participatory Internet.  Is there some way we can be more welcoming to people wanting to do this?  Dave was suggesting maybe making the Manifesto more approachable would be a way to do this.  And the underlying question is:  can we be more welcoming to people who want to move the Mozilla Manifesto forward through new types of activities?

That’s a great question.  It’s something I want to see happen. However,my top priorities each day are still more  tightly focused on supporting our current communities.  So it’s good to have new energy looking at this question.

[Source: Planet Mozilla]

Dave Townsend: Keeping Track

In the past year or so that I’ve been working for Mozilla I’ve found myself slowly working my way through a bunch of different ways to keep track of all of the work on my plate. I still don’t think I’ve found the best way so I wondered what other people do to manage suck things?

For a rough idea of my work, most of my work is bug oriented. Either bugs that I want to work on when I get some time, bugs I am actively working on, bugs I am waiting for review on, bugs I am reviewing, bugs I am waiting to check in, bugs I want to backport to a branch… and so on. Then there is other work like planning future work and working with extension authors to help resolve their problems.

A few different approaches I’ve tried:

Bug ASSIGNED status

Simplest of all, gives me a long list of stuff I am looking at. Totally fails for prospective work though and the list gets somewhat daunting.

Status whiteboard flags

I tried for a while sticking special flags into the status whiteboard that could then be spotted in special bug queries so I could see what state each bug was in. This kind of worked, though I imagine irritated some with bugspam as I maintained the flags and a couple of times other people changed the flags.

Bugzilla tagging

Bugzilla has this tagging feature that basically lets you create named buglists. Basically like using the whiteboard stuff without having to use the whiteboard. Sadly Bugzilla’s tagging UI sucks really hard.

Bookmark tagging

With Firefox 3 I can bookmark my bugs and tag them, and use smart bookmark folders as my buglists right? Well sort of, the folder list isn’t really enough detail and there are issues with manually created smart folders that kept losing my bookmarks.

Task management software

Finally bit the bullet and stuck all of this stuff into some task managent software (Omnifocus as it happens). This is so far going ok but seems to require more dedication to keep the list up to date, I think because of having to switch to a different application so much.

So what are other people doing?

[Source: Planet Mozilla]

Robert Helmer: OS as platform

I’ve been thinking a lot about the role of operating systems lately. Why is there no operating system vendor that focuses on being a platform for applications, rather than trying to compete directly in the application space?

Maybe this is a naive question, but it really makes application developer’s lives a huge pain to have to compete with platform vendors all the time, and it’s surprising to me that the market puts up with it. It also brings up the whole “core competency” argument, can one company really do two fairly specialized things well?

These are who I consider to be the top-tier OS vendors:

  • Microsoft Windows
  • Apple Mac OS X
  • Ubuntu Linux

Why don’t any of them provide just the base OS + gotta-have applications (editor, email, web), and give the ISVs the ability to:

  • register new applications in a central catalog
  • deliver updates to specific applications
  • send crash data back to the vendor

This would allow the OS vendor to focus on the core OS functionality, and provide means to the users to select applications that suited their needs (shipping preinstalled with the top editor, email and web clients, of course). Having formal reviewers as well as user ratings would be a great way to promote good and trustworthy applications.

I don’t anticipate any of these top-tier OS vendors focusing on this space, although for different reasons.

Microsoft is particularly adept at watching application vendor’s innovations and making functional facsimiles (some say “Worse is Better” versions). For example “Word Perfect”, “Lotus 123″, and “Netscape”. Once they’ve decided to commit serious developer time though they tend to slowly overwhelm and overtake the slice of the market that they target. I think that the convenience of a single vendor is what people like, and I guess dominating the stack is one way to control the pipeline.

Prior to OS X, Apple seemed to avoid this (with the notable exception of Claris) but since has embarked on Office competitors, and it’s own web browser (Safari/WebKit). Maybe this is a copy out of the Windows playbook, but it seems just as likely that it’s a bid to control the full user experience, which is very Apple.

Ubuntu comes closest to my ideal, but still insists on packaging everything themselves, and doesn’t do a 1:1 mapping for bug and crash reports. They have their own build, their own crash reporting system, etc.

Why can’t I log into an interface for each of these vendors, register my latest release, and let them handle updating the user catalog, advertising updates to existing users, and a means to funnel back crash reports?

If history is any guide, OS vendors will continue to oscillate between focusing on their core competency (providing an interface between the bare metal and the human) and trying to take over the full application stack flavor of the week. There’s just too much money and power on the table when you control the whole thing for people to leave it alone.

[Source: Planet Mozilla]

Myk Melez: Why I Host Projects on Mozdev I've been using Mozdev for almost eight years, ever since it started hosting Forumzilla, my project to build a Mozilla-based web forum reader (which eventually became a Thunderbird extension and then Thunderbird's built-in feed reading feature).

Mozdev plays the critical role in the Mozilla community of hosting Mozilla-related projects that aren't considered core enough to the Mozilla mission to host on official community infrastructure.  It's a great adjunct to AMO, which distributes many of the projects that Mozdev hosts.

Over the years, I've been happy to host a number of such projects there, including the aforementioned Forumzilla plus Bugxula (defunct), Tinderstatus, and revision control/bug tracking for the Labs project Personas.

Although there have always been alternatives, they have been unpalatable: SourceForge has a cumbersome and unfamiliar interface, and hosting on my own server would have meant doing all my own systems administration.  I use Mozdev because I want to focus on my projects, not on the infrastructure for developing them.

Over the last couple of years, Google Code has become an option.  Although it provides much less functionality than Mozdev (and limits how many projects you can create), it does have a simpler interface and a more modern revision control system.

The folks who run Mozdev (which includes me) want simplicity and modern services (without sacrificing power) for Mozdev too, and we've identified three priorities in that regard: adding Mercurial for revision control, implementing WYSIWYG content editing, and automating project creation and management.

So I'm thrilled to read Mozdev developer Doug Warner's announcement today, via a post to the project owners mailing list, that he has landed Mercurial support.  Now you can get all the goodness of Hg hosted on your behalf for any of your Mozilla-related projects.

Eight years later, I think Mozdev remains the best place to host my projects, and it's just getting better.  I can't wait to see what's next (and I have some ideas about what simple WYSIWYG editing could look like, about which more soon).

[Source: Planet Mozilla]

More News


Sponsored by: