Open main menu

CDOT Wiki β

Changes

Potential Projects

1,438 bytes added, 14:17, 17 April 2013
m
Reverted edits by Saoagent (Talk) to last revision by Chris Tyler
= Introduction =
This is a list of potential projects that need people. If you'd like to work on one of these, move the chosen project to the [[Project List]] and create a page for your work based on the [[Sample Project]] template.
'''Students:''' If you'd like to work on one of these, move the chosen project to the [[Project List]] and create a page for your work based on the [[Sample Project]] template. '''Open Source Community Members:''' We welcome your recommendations for potential projects. Please create an account on this Wiki and create a description for your proposed project below. Please list your contact info (just an IRC or FAS2 name is OK) as well as links to any related web pages as Resources for the proposed project. (Questions? Ask [[user:Chris Tyler | Chris Tyler]] or [[user:David.humphrey | David Humphrey]]). = SBR600 Potential Projects = For possible projects for the SBR600 Software Build and Release Course, lease see the [[SBR600 Potential Projects]] page. = Potential Eclipse WTP Projects = See the list of potential bugs [https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=product&z_axis_field=bug_severity&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=WTP+Common+Tools&product=WTP+ServerTools&product=WTP+Source+Editing&product=WTP+Webservices&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=REOPENED&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&priority=P2&priority=P3&priority=P4&priority=P5&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=assigned_to&type0-0-0=regexp&value0-0-0=.@ca.ibm.com&field0-0-1=noop&type0-0-1=noop&value0-0-1= here]. <!-- = Potential Fedora Projects =
== [[Sample Project]] ==
NOTE: if someone has already created the project page, speak to this person and see if you can join them. If so, simply add your name to the '''Project Leader(s)''' page. Otherwise, you can become a contributor later.
== Mozilla Tree Visualization Ideas Pool ==
Use the canvas element Lots of good ideas are listed in order to create a generic front-end [[:fedora:SummerCoding/2008/Ideas|Summer Coding Ideas (Fedora Wiki)]]. These projects were originally proposed for data visualization Google Summer of the Mozilla source. Many types Code projects; if you want to use one of information about the Mozilla project can be keyed to the source tree. For examplethem, file change-ratesplease discuss it with [[User:Chris Tyler|Chris Tyler]] before selecting it, code-coverage, bug activity per module, checkins per module, etc. The visualization will be a heatmap, showing certain types because the scope and mentorship model for GSOC is different from that of activity in the tree. Doing this visualizaiton using canvas3d would allow for a third axis, and changes over time to be shownLUX projects.
Resources: Cathy== Cobbler Web ==
== Mozilla Data Visualization Back-ends ==Cobbler is a Linux install server that simplifies tasks associated with fully automated installation such as DHCP, DNS, kickstart, yum, and virtualization. It aims to be a universal install server for all linux distributions. Currently Cobbler has a web interface that allows users an easier way of interacting with cobbler. There are several core improvements that can be made. One idea is to extend cobbler web to produce views that make it easier for users to edit fields that only they edit (let me reinstall systems I own but don't show me fields I shouldn't care about). Another is to enable search features in the web app to make it tolerate thousands of systems to a better extent. Finally, another feature is to add a task engine to cobblerd, to make it possible to run commands like "cobbler import" and "cobbler reposync" in the background and see their output in the web interface via an AJAXy type system.
Create Possible features are not limited to the above (or just working on the web interface), Cobbler has an ongoing RFE list in Trac that has a data-source for wide variety of potential ideas, and ideas beyond the Mozilla Tree Visualization projectones listed are also fair game. This means data mining cvs.mozilla.org, bugzilla.mozilla.org, bonsai.mozillaSee https://fedorahosted.org and preparing the data for use in a heatmap visualization./cobbler/report/1?sort=type&asc=1
Resources: Cathyhttp://fedoraproject.org/cobbler
== Add OpenID support to Bugzilla ==Contact: Michael DeHaan
Many open source projects rely on bugzilla for bug tracking, and open source developers use different instances, forcing them to have multiple logins. Complete OpenID support in bugzilla.== Personal Koji Repositories ==
References: reed, [https://bugzillaKoji Personal Repos (KoPeR) is a concept to allow Fedora maintainers to create personal repos of packages to build against and share with others.mozilla.org/show_bug.cgi?id=294608 bug 294608]
== Tbeachball - Quantifying Mozilla's Responsiveness == Resources: http://fedoraproject.org/wiki/JesseKeating/KojiPersonalRepos
This project will add instrumentation to Mozilla in order to determine how much time is spent away from the main event loop, and therefore from the user's mouse/keyboard input. When the user does something, how long does it take for Mozilla to act on that stimulus? One thing that sometimes interferes with interface responsiveness is spending too long away from the main event loop, perhaps in layout or some other intensive computation. This leads to new events from the user, such as mouse clicks or keypresses, not being noticed and acted upon. This could also be expanded in order to include the triggering of log points and specific dialog openings, etc. with a view to understanding what the long-running events actually are.Contact: Jesse Keating
References: http://shaver.off.net/diary/2007/08/25/tbeachball/ and http://shaver.off.net/misc/latency-tracing-patch.txt== Port Wubi to Fedora ==
== Port distcc If upstream is willing to MSYS ==integrate it, port wubi-installer and make it more cross distribution. Otherwise, provide a similar implementation for Fedora.
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.mozillawubi-installer.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== Delta RPM support in Koji build system ==
== Add Multi-File transfer to distcc == * https://fedorahosted.org/bodhi/ticket/160
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.== Benchmark Nightlife Scalability Issues ==
References: Cesar and TomUsing Puppet, or some other management tool, create a grid of a dozen machines, then turn that into 12,000 machines. Address the network characteristics - how much bandwidth do you need on different components, the communication mechanisms - does UDP work at such a scale, the grid topology - what happens when two nodes are behind firewalls.
== Add password managers for various platforms ==Resource: [[:fedora:Nightlife|Nightlife wiki page]], Matthew Farrellee
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?idCreate Test Suite for Condor ==371000 371000]. See also [http://mail.gnome.org/archives/desktop-devel-list/2007-August/msg00241.html this e-mail message].
References: dolskeAlong with a good build infrastructure, a strong test framework and methodology is key to survival of modern software. Condor is a system that is shipped on, currently, 14 different platforms - OS + Arch combinations. New features need to be verified to work on all those platforms and shown to cause no regressions in other features. Condor has a large test suite, but no suite covers everything or in sufficient depth. Pick a few features, say the VM Universe or Concurrency Limits, and demonstrate full understanding of them by testing all of the corner cases. This is far from a simple task, and requires more than a cursory understand of the system to properly complete. Understanding the complex interactions of distributed components, common patterns exist across many distribute systems, as well as intimate interactions with the OS is key.
== Convert password storage to a SQLite database ==Resource: [[:fedora:Nightlife|Nightlife wiki page]], Matthew Farrellee
Currently, Firefox stores logins in a text file in the user--- Below: Commented out by Chris Tyler 2008-08-31 -- I think we's profile (signons2.txt). The format is simple, but inflexible. Storage of other browser data, such as cookies and form history, has steadily been moving towards using SQLite-backed databases so moving password storage to ll get all the same kind of storage would be good. Some work was started in [https://bugzilla.mozilla.org/show_bug.cgi?id=288040 bug 288040]students doing this.
References: dolske== Review Packages ==
== Refactor master password out There is a lot of NSS ==packages in Fedora waiting for someone to review it. While a completely new Fedora contributor needs to be sponsored before his package is approved, subsequent packages can be reviewed and approved by any Fedora package maintainer. In addition to that, virtually anybody with a Red Hat Bugzilla account can do do unofficial reviews. Working through the review queue and doing this work might be fun and useful learning process for folks interested in RPM and packaging in general.
Users can enable a "master password" The general process is described in their browser, which securely encrypts all their stored passwordshttp://fedoraproject. The current implementation can be awkward to use org/wiki/PackageMaintainers/HowToGetSponsored and has some limitations, see [httpsin http://bugzilla.mozillafedoraproject.org/show_bug.cgi?id=322617 bug 322617]. Fixing this would involve having password manager being more involved with the cryptography operations -- deriving a key from a passphrase with PKCS#5, and using NSS and PKCS#11 to encryptwiki/Packaging/decrypt entriesReviewGuidelines.
== Add Offline Support to an open source web app = Review Requests ===
Firefox 3 will support 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 [* Unassigned review requests - http://wwwfedoraproject.bluishcoderorg/PackageReviewStatus/NEW.cohtml* In progress review requests - http://fedoraproject.nzorg/2007wiki/02PackageMaintainers/offline-zimbraInProgressReviewRequests* Approved review requests -with-firefox.html porting Zimbra]. Pick another web app and add offline support, for example: [http://moodlefedoraproject.org Moodle]./wiki/PackageMaintainers/ApprovedReviewRequests-->
References: mfinkle= Potential Mozilla Projects =
== Thunderbird SMTP Auto-Sensing [[Sample Project]] ==
Modify Thunderbird so that it uses the correct SMTP server for your current network and IPThis is a sample project stub. In other words, if you are at home, use your home ISP's SMTP, but if you You can use the template for [[Sample Project]] in order to create a school wireless network, switch to project page for one of the school's SMTPstubs below. These various SMTP configurations should be manually controlled by the user, that This is, how you don't have to try and figure out which SMTP to use. Rather, it should be configurable in an options dialogsign-up' for a project.
ReferencesNOTE: #maildevif someone has already created the project page, speak to this person and see if you can join them. If so, simply add your name to the '''Project Leader(s)''' page. Otherwise, you can become a contributor later.
== [[Bugzilla component-watching]] Improve Localization build system ==
Currently it requires many many steps to produce another language of Firefox.It's common for a developer would really easy to want package these many steps to "watch" all reduce the bugs that are filed in required knowledge to generate 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 errornew language.
Reference: reed, [https://bugzillaAdding a few make steps to wrap this process would help everyone.mozillaThis is a very easy project to tackle but very benefitial if the time and love is given to it.org/show_bug.cgi?id=76794 Bug 76794]
== Litmus Extension ==Reference: armenzg
== Create a cross-repo pushlog to see all locales's checkins ==We currently check many different repositories to trigger builds when a developer makes a change. We wanted also check the localizer's repositories to see if they have an extension pushed any changes. The problem is that would be able we have close to serve users testcases eighty different localization repositories and that takes a long time to try and allow check each one of them to submit results to [http.If we had a joint view that would improve our systems. An example of that view is:https://litmusl10n-stage-sj.mozilla.org /pushes/but the format should be more like this:http://litmushg.mozilla.org]/mozilla-central/pushlogwhich is what our release engineering systems check for. We could expand the feature set of the extension This project would require you to do a lot of other cool things with Bugzilla hack hg and Website Reporter integrationpushlog to make it work. 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 extensionarmenzg has many blog posts explaining how to setup pushlog in your local machine.
== [["Avoid loading the same page twice" Extension]] ==Reference: armenzg - Bug 498641
Create an extension to Firefox so that when a bookmark is clicked, and that site is already open in any tab in any window, that tab/window is brought to the front rather than loading the page again.== Thunderbird SMTP Auto-Sensing ==
Related tech Modify Thunderbird so that it uses the correct SMTP server for your current network and skills: XULIP. In other words, JavaScriptif you are at home, use your home ISP's SMTP, but if you use a school wireless network, switch to the school's SMTP. These various SMTP configurations should be manually controlled by the user, that is, you don't have to try and figure out which SMTP to use. Rather, it should be configurable in an options dialog.
== Firebug "linting" for portability problems == Lots of web developers use Firebug and Firefox for building their applications, but we want those apps to work well in other browsers as well. If Firebug knew about JS or CSS patterns that could cause problems in other browsers, it would make it much easier to have those applications work in all browsers. ResourcesReferences: mfinkle == Add-on update helper tools for developers ==#maildev
As Firefox 3 gets ramped up, there are nearly 3000 add-ons that need to get updated to some degree. Write tools (web or XULRunner) to look in add-ons and find things that developers will need to update. You'll want to work with the Mozilla documentation and evangelism teams to figure out what you're looking for and what to recommend to users.
Resources: mfinkle
== <strike>XULRunner Application Packaging ==
Help to develop an [http://www.mozpad.org/doku.php?id=application_build_system_project automated packaging system] for XULRunner applications.
Resources: plasticmillion, mfinkle, #mozpad, #prism</strike>
== 'Compact databases' feature for Mozilla calendaring applications (Lightning, Sunbird) ==
Resources: ctalbert, daniel in #calendar on irc.mozilla.org
== Thunderbird Draft Scheduler Extension == Write an extension for Thunderbird so that the user has the ability to mark a draft email for sending later. This is not the same as having to save emails in your DRAFT box because users would have to remember to go back in and click Send later. What is different here is that users could set the date and time for each email to be sent. This feature would be helpful to those who work late into the night but prefer not to send emails at such a late hour. This feature would also benefit support staff, e.g., administrative assistants, who constantly have to send out regular email reminders, e.g., for meetings, timesheets, etc. Resources: Vivian Ngo == <strike>[[Spellcheck Extension for Arbitrary Web Pages]] </strike> ==
<strike>Write an extension to leverage the existing spellcheck code in Mozilla and add the ability to highlight spelling mistakes for a given web page (i.e., vs. a textbox).</strike>
== <strike>Modify Firefox to handle files downloaded to Temp more appropriately </strike>==
<strike>Often files downloaded by the browser are put in a temporary folder that is emptied on close. Users (and especially novice users) should be protected from inadvertent data loss as a result of important files being saved to this temp folder. This project will add fixes to the browser so that users are protected. Ideas include:
* Make Firefox aware of common productivity file types (e.g., .doc, .pdf) and whitelist these types so they aren't deleted
* Have the browser pop-up a Save As dialog instead of automatically saving to temp, and use a documents path
Other ideas are possible, and a combination of these might be necessary. Ultimately, this fix should target regular users without much knowledge of the filesystem.</strike>
Resources: ted, mfinkle
See also: [https://bugzilla.mozilla.org/show_bug.cgi?id== Implement Audio 280419 bug 280419] and Visual Mute in the Browser == It would be useful if you could pause[https:/mute/freeze distracting content in a tabbugzilla. Often this means plugins, which are playing music or animatingmozilla. One possible solution is to expose the API that bfcache uses to freezeorg/thaw a window, since plugins are themselves "windows." Other platform specific approaches may also be available (e.gshow_bug.cgi?id=369108 bug 369108], hooking sound API calls in Windows). References: and code [http://wwwmxr.melezmozilla.comorg/mozilla-central/mykzillasource/2007uriloader/04exthandler/tab-specific-mutensExternalHelperAppService.cpp#2077 here].html
== Standalone Test Harnesses ==
* 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 ==
Increasingly, Mozilla is moving toward using the Python based buildbot system for automated builds and tests. It would be good to add a Source class for client.mk checkouts. This would mean creating a a general Source class that understands the idea of checking out a file, and which could then be used to drive the checkout and allow for integration with client.mk.
References: Ben Hearsum (bhearsum), Rob Helmer (rhelmer) == Thunderbird Image Auto-Resize == Write an extension for Thunderbird that gives functionality similar to that of Outlook, where image attachments in an email can be automatically re-sized to one of a set of smaller sizes. This is helpful for users who would otherwise try to send megabytes of image data, when they can safely scale the images down and still share their pictures with friends. References: #maildev
== Port the Firefox Release Repackager to other platforms ==
Resources: mkaply, bsmedberg
 
== Add MSI packaging to the Firefox build system ==
 
Firefox is not currently available on Windows as an [http://en.wikipedia.org/wiki/Windows_Installer MSI], which is something IT departments and others deploying on many desktops routinely request. The [http://en.wikipedia.org/wiki/WiX Windows Installer XML toolset (WiX)] is an open source tool provided by Microsoft that allows the creation of MSI files based on XML config files. This project will add MSI packaging to the Firefox build system so that it happens by default.
 
Resources: mkaply, ted, http://www.frontmotion.com/Firefox/index.htm, http://forums.mozillazine.org/viewtopic.php?t=138033
 
== LiveCD for Resource Kit ==
 
We'd like to produce a DVD resource kit for teaching Mozilla development. This disc could be used in two ways: as a bootable (and installable) "Live Disc" containing a full Linux (Fedora) development environment, or it could be inserted into a running Windows system to install MozillaBuild 1.2 and some other tools. This project involves packaging: creating RPM packages of material that should be included on the disc but which is not presently available in RPM format (such as a Firefox trunk snapshot, the Mozilla videos, documentation, and possibly a local MXR instance) and creating a suitable Windows installer.
 
Resources: dave, ctyler
== gdb symbol server support ==
# http://www.linuxcommand.org/man_pages/objcopy1.html (see --add-gnu-debuglink and --only-keep-debug)
# http://www.totalviewtech.com/Documentation/Tips/gnu_debuglink.html
 
Resources: ted, Stan Shebs, Jim Blandy
# http://sourceware.org/gdb/current/onlinedocs/gdb_3.html#SEC7
# 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== RegressionTry == Make it possible to look for bugs across old nightly builds of Firefox using automated tools. For example, [http://db48x.net/regression-search/MXR rely on regression-search] is a Perl script that allows you to parse Cdo binary searches across binaries, looking for the existence of a bug. This could be improved through the use of tools like [http://services.alphaworks.ibm.com/coscripter/browse/C++ about co-scripter]. Ideally the user could look for bugs in automated ways, without having to download and install tons of browser versions. Resources: db48x, ted == 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 extract variable the build system runs builds on Linux, Mac and function namesWindows, using those patches, then serves those builds for testing. This is really helpful to figure out if proposed patches solve specific problems... We now have static analysis tools The only problem is that can parse all there’s a little bit of patching needed to the C++ used 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]) == Add DTrace probes and scripts for Mozilla code base == [http://en.wikipedia.org/wiki/DTrace DTrace] was created by Sun in OpenSolaris to allow developers to write simple scripts in order to probe and instrument executing programs in a way not possible otherwise. One of the advantages of DTrace is that it allows you to turn on probing when you need it, but not incur an execution penalty with regard to performance (i.e., when probes aren't being scripted, they aren't run). This requires developers to add "probes" to their source code. For example, if you wanted to know when a particular function is entered/exited, get info about what happened, etc. you could add probes to the particular function. Writing the probes is not difficult, however there are hundreds or thousands of probes that Mozilla correctlywould like across its code base. It  Resources: sayrer == Plugin Code Test Suite == Create a [http://developer.mozilla.org/en/docs/Plugins plugin] test suite. There are currently no tests of any kind, and this code is very brittle and not well understood. This would be awesome to have involve creating a GCC plugin or tool built on Elsa set of plugins and some html/js to drive that could parse C++ properly for LXR/MXR plugin in order to extract all push test coverage. Maybe look at the useful informationJRE tests, create some specific plugin cases (e.g., swf to load that tests flash specific code). The results could be used newly announced Google Chromium browser [http://dev.chromium.org/developers/how-tos/getting-around-the-chrome-source-code seems to have something like this] with regard to improve searching using the npapi for driving tests via plug-in. See also docs on [http://dev.chromium.org/developers/design-documents/inter-process-communication IPC] and syntax highlighting[http://dev.chromium.org/developers/design-documents/plugin-architecture plug-in design] in Chromium. This will require C programming, as well as light web development (html, js, perhaps swf).
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/genxrefResources: Taras Glek, timelessjst
== Profile the build Create self-serve symbol upload system (why are my Windows builds so slow?) ==
It's Mozilla has a well known fact symbol server which is used by developers to debug issues in release builds that it takes longer to build on Windows than on a comparable Linux or Mac machine. We don't know exactly whyinclude debug information (i.e., howeversymbols). There have been However, many theoriescrashes are related to third-party binary plugins or extensions, but for which Mozilla has no real datasymbols. Profiling the build system This project would allow us create a web-based self-serve solution for third-parties to figure out where all of the time is being spentupload symbols for their binary components in breakpad-formatted .sym file format. The best place to start might be by adding some profiling to GNU Make, to figure out which targets Ideally this could happen in our makefiles take the most time. From therean automated way, depending on the results, profiling such that third-parties could be added add a step to other parts of the their build system to narrow down specific bottlenecksdo it automatically with each release. See [https://bugzilla.mozilla.org/show_bug.cgi?id=419879 bug# 419879].
References:
# http://wiki.services.openoffice.org/wiki/BuildSpeedup - OpenOffice.org did something similar
Resources: ted
== RegressionTry <strike>Add OpenLayers test suite to Mozilla </strike>== <strike>Mozilla [http://mxr.mozilla.org/mozilla-central/source/dom/tests/mochitest/ajax/ uses] many common JavaScript library test suites to add additional coverage to it's JavaScript implementation. One test suite that is not currently used by Mozilla, but could be, is the [http://openlayers.org OpenLayer's] js [http://trac.openlayers.org/browser/trunk/openlayers/tests test suite]. See [https://bugzilla.mozilla.org/show_bug.cgi?id=399311 bug# 399311]. Resources: sayrer</strike> == <strike>Import sqlite test suite</strike> == <strike>Mozilla uses an embedded version of [http://www.sqlite.org/ SQLite] extensively to [http://developer.mozilla.org/en/storage store data] such as bookmarks, history, etc. To insure that it runs properly within Mozilla, it would be good to add the entire sqlite test suite to Mozilla's tests, so that testing the browser also means testing sqlite. The sqlite test suite is written in TCL and needs to be ported to JavaScript. Some [http://mxr.mozilla.org/mozilla-central/source/storage/test/unit/test_like.js work has already been done], but more is required to get full test coverage. References: [https://bugzilla.mozilla.org/show_bug.cgi?id=391756 bug 391756], http://www.0xdeadbeef.com/weblog/?p=368 Resources: sdwilsh </strike> Take : [http://zenit.senecac.on.ca/wiki/index.php/Import_sqlite_test_suite Park,KiWon] == Make chromebug work in Thunderbird == TBD == Help gristmill move forward in Thunderbird == TBD == Help Calendar integration on Trunk == TBD Resources: Fallen   == HTML page set sanitizer == The Talos performance testing system at Mozilla currently runs on a large set of web pages pulled from the Alexa Top 500. These pages can't be redistributed, since they're mirrors of copyrighted web pages. In addition, many of them contain adult content. This makes it difficult for people to duplicate the Talos results or to test changes that have an expected performance impact. A useful solution to this problem would be a tool that takes a mirrored copy of a website and "sanitizes" it, by changing the page text and image contents (making them junk or filler text or something). The caveat here is that this *cannot* change the performance characteristics of the page. For example, taking a page that is all Chinese text and replacing it with "Lorem Ipsum" filler text would cause the page to take different text rendering paths, which would change what is measured. As another example, making all JPEG images solid black would likely make them decode and render much faster. Any solution should have some analysis performed that shows that performance is not significantly altered in the sanitized page set. Resources: ted (but find someone better!) == 3D object picking ==Canvas 3D JS Library is a library for the creation and manipulation of 3D scenes in the browser without needing to know much 3D programming. Part of this project is to handle mouse input. This particular project looks at how to perform "picking". That is, when given a coordinate within the canvas, return the 3D object at that location. Resources: cathy, Andor (http://www.c3dl.org) = Potential OOo Projects = == [[Sample Project]] == This is a sample project stub. You can use the template for [[Sample Project]] in order to create a project page for one of the stubs below. This is how you 'sign-up' for a project. NOTE: if someone has already created the project page, speak to this person and see if you can join them. If so, simply add your name to the '''Project Leader(s)''' page. Otherwise, you can become a contributor later. == Generate an OOo XREF based on Dehydra == Using Dehydra, build OOo and generate an xref in the same way we are indexing for dxr.
Make it possible to look for bugs across old nightly builds of Firefox using automated tools. For example, [httpTODO://db48x.net/regression-search/ regression-search] is a script that allows you to do binary searches across binaries, looking for the existence of a bug. This could be improved through the use of tools like [http://services.alphaworksmore info.ibm.com/coscripter/browse/about co-scripter]. Ideally the user could look for bugs in automated ways, without having to download and install tons of browser versions.
Resources: db48xhumph, tedtaras
== Mercurial history browsing Existing Subjects proposed by OpenOffice.org Education Project ==
We're just starting to use an exciting new [httpFIXME ://betterexplainedthe projects proposed on the OpenOffice.com/articles/intro-org Education Project will be adapted to-distributed-version-control-illustrated/ distributed version control] tool: [http://developer.mozilla.org/en/docs/Mercurial Mercurial]the current section.
One of the exciting things about Mercurial is that the history—the list of all Waiting we encourage you to have a look at the changes that have ever been checked in—is not linear. It frequently has ''branches'' and ''merges''. This is actually a good, important feature, as you know if you've read a little about distributed version control. The downside is that the history becomes a maze of twisty little passages. [http://officewiki.smedbergsservices.usopenoffice.org/viewerwiki/indexEducation_Project/Effort OpenOffice.xhtml#mozilla-central:acb5456539c668d3ec0ec755dd3b64ddb56363d2 Benjamin Smedbergorg Education Project Effort page]'''s demo] shows the history of a repository with lots of merges (each box is a check-in; you can click on the boxes to move around).
There have been a couple attempts at showing history in an intuitive, graphical way. Mercurial comes with a web UI for browsing the repository, including history ([httpOther links://hg.mozilla.org/mozilla-central/index.cgi/log/13540 here's what it looks like]). It also comes with an "hg glog" extension that draws history as ASCII art, and an "hg view" extension that does roughly the same thing with a little GUI. Sadly, none of these applications qualifies as ''awesome''.
Your mission is to rectify this sad situation by writing an awesome browser-based UI for navigating Mercurial repository history[http://wiki.services.openoffice.org/wiki/Education_Project OpenOffice.org Education Project on the Wiki]
Resources: jorendorff, bsmedberg
== 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[User:Ericb|Ericb]] 21://ascher.ca/blog/05, 26 September 2008/05/02/thunderbird-team-needs-help-from-pythonperl-build-assist/ Ascher](UTC)
3
edits