References: http://shaver.off.net/diary/2007/08/25/tbeachball/ and http://shaver.off.net/misc/latency-tracing-patch.txt
== Port distcc to MSYS ==
The recent work to add [[Distcc With MSVC|MSVC support]] to distcc works using the cygwin build environment. However, since this project was completed, Mozilla has switched to MSYS (see the [http://developer.mozilla.org/en/docs/Windows_Build_Prerequisites Mozilla Win32 build docs). Port distcc so that it works with the new MSYS environment.
References: Cesar and Tom
== Add Multi-File transfer to distcc ==
The recent work to add [[Distcc With MSVC|MSVC support]] to distcc only allows for a single file to be sent back from build slaves. This means that extra debugging info (e.g., .pdb files) cannot be sent with binaries. Modify distcc so that it can support debug Mozilla builds.
References: Cesar and Tom
== Add password managers for various platforms ==
Previous work was done on adding [[OS X Keychain integration]] to Firefox. This work was focused on tightly binding C++ and Mac API calls. Since then more work has been done to [http://blog.mozilla.com/dolske/2007/05/28/followup-password-manager-changes-coming-in-ff3-alpha-5/ modularize the password manager] in Firefox. Various platform "keychains" need to be integrated with the new system. See bugs [https://bugzilla.mozilla.org/show_bug.cgi?id=309807 309807], [https://bugzilla.mozilla.org/show_bug.cgi?id=106400 106400], and [https://bugzilla.mozilla.org/show_bug.cgi?id=371000 371000]. See also [http://mail.gnome.org/archives/desktop-devel-list/2007-August/msg00241.html this e-mail message].
References: dolske
== Convert password storage to a SQLite database ==
== Add Offline Support to an open source web app ==
Firefox 3 will support supports offline abilities, such that web developers can write their apps so they work even when no network is present. Good headway has been made already [http://www.bluishcoder.co.nz/2007/02/offline-zimbra-with-firefox.html porting Zimbra]. Pick another web app and add offline support, for example: [http://moodle.org Moodle].
References: mfinkle
References: #maildev
== [[Bugzilla component-watching]] ==
It's common for a developer to want to "watch" all the bugs that are filed in a certain [https://bugzilla.mozilla.org Bugzilla] component. Mozilla uses a convoluted and painful system of synthetic accounts to simulate this capability, and we'd all really prefer to be able to do it more directly and with less opportunity for error.
Reference: reed, [https://bugzilla.mozilla.org/show_bug.cgi?id=76794 Bug 76794]
== Litmus Extension ==
We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to [http://litmus.mozilla.org http://litmus.mozilla.org]. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration. So we need some ideas there. If you're interested, you could consult the work of [[User:djhamp-g|David Hamp-Gonsalves]], who created the Buggy Bar extension.
== [["Avoid loading the same page twice" Extension]] ==
* References: http://xoatlicue.blogspot.com/2008/01/standalone-test-product.html
* Possible Resources: Rob Campbell (robcee), Ben Hearsum
== Provide a way to easily perform bookmark queries in JS ==
Right now the only way of finding bookmarks in FUEL is to recursively iterate folders beginning with the root. Because the assumption is that in Firefox 3 users are going to accumulate a lot of bookmarks, this could be not efficient enough (not to mention inconvenient). It would be useful if [http://developer.mozilla.org/en/docs/FUEL FUEL] provided an interface for querying bookmarks, as a wrapper for nsINavHistoryQuery and friends. An example of how it could look like in action:
var query = bookmarks.newQuery();
query.type = "folder";
query.searchTerms = "goats";
var results = query.execute();
References: Mark Finkle (mfinkle), [https://bugzilla.mozilla.org/show_bug.cgi?id=409279 bug 409279]
== Provide an easier mechanism for creating History Listeners in JS ==
A better way for adding easy history event listeners to FUEL is needed, perhaps. Some initial design work has been done on this, see [https://bugzilla.mozilla.org/show_bug.cgi?id=406974 bug 406974].
References: Mark Finkle (mfinkle)
== Add source checkout to buildbot ==
Resources: mkaply, ted, http://www.frontmotion.com/Firefox/index.htm, http://forums.mozillazine.org/viewtopic.php?t=138033
== gdb symbol server support ==
# http://sourceware.org/gdb/current/onlinedocs/gdb_9.html#SEC80
Resources: ted, Stan Shebs, Jim Blandy
== gcc plugin for better mxr code parsing ==
Currently LXR/MXR rely on a Perl script to parse C/C++ and extract variable and function names. We now have static analysis tools that can parse all of the C++ used by Mozilla correctly. It would be awesome to have a GCC plugin or tool built on Elsa that could parse C++ properly for LXR/MXR to extract all the useful information. The results could be used to improve searching and syntax highlighting.
References:
# http://wiki.mozilla.org/DeHydra
# http://wiki.mozilla.org/Dehydra_GCC
# http://www.cs.berkeley.edu/~smcpeak/elkhound/
# http://timeless.justdave.net/mxr-test/webtools/source/lxr/genxref
Resources: Taras Glek, timeless
== Profile the build system (why are my Windows builds so slow?) ==
== Extend Try Server to test Thunderbird patches ==
"Specifically, Mozilla has a great system called “try servers” where one can submit patches against the tree, and the build system runs builds on Linux, Mac and Windows, using those patches, then serves those builds for testing. This is really helpful to figure out if proposed patches solve specific problems...The only problem is that there’s a little bit of patching needed to the try server code itself to make it able to work with other targets besides Firefox, as described in bug 431375" ([http://ascher.ca/blog/2008/05/02/thunderbird-team-needs-help-from-pythonperl-build-assist/ Ascher])
