Open main menu

CDOT Wiki β

Changes

Potential Projects

4,182 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.
= Projects ='''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 [[Sample Projectuser:Chris Tyler | Chris Tyler]] ==or [[user:David.humphrey | David Humphrey]]).
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.= SBR600 Potential Projects =
NOTE: if someone has already created For possible projects for the project pageSBR600 Software Build and Release Course, speak to this person and lease see if you can join them. If so, simply add your name to the '''Project Leader(s)''' [[SBR600 Potential Projects]] page. Otherwise, you can become a contributor later.
== Mozilla Tree Visualization =Potential Eclipse WTP Projects =
Use See the canvas element in order to create a generic front-end for data visualization list of the Mozilla sourcepotential bugs [https://bugs.eclipse. Many types of information about the Mozilla project can be keyed to the source treeorg/bugs/report. For example, file changecgi?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-rates, code0-coverage, bug activity per module, checkins per module, etc0=. The visualization will be a heatmap, showing certain types of activity in the tree@ca.ibm. Doing this visualizaiton using canvas3d would allow for a third axis, and changes over time to be showncom&field0-0-1=noop&type0-0-1=noop&value0-0-1= here].
Resources: Cathy<!--
== Mozilla Data Visualization Back-ends =Potential Fedora Projects =
Create a data-source for the Mozilla Tree Visualization project. This means data mining cvs.mozilla.org, bugzilla.mozilla.org, bonsai.mozilla.org and preparing the data for use in a heatmap visualization.== [[Sample Project]] ==
Resources: CathyThis 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.
== Add OpenID support NOTE: if someone has already created the project page, speak to Bugzilla ==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.
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.== Ideas Pool ==
ReferencesLots of good ideas are listed in [[: reed, [httpsfedora:SummerCoding/2008/bugzillaIdeas|Summer Coding Ideas (Fedora Wiki)]].mozilla.org/show_bugThese projects were originally proposed for Google Summer of Code projects; if you want to use one of them, please discuss it with [[User:Chris Tyler|Chris Tyler]] before selecting it, because the scope and mentorship model for GSOC is different from that of the LUX projects.cgi?id=294608 bug 294608]
== Tbeachball - Quantifying Mozilla's Responsiveness Cobbler Web ==
This project will add instrumentation to Mozilla in order to determine how much time Cobbler is spent away from the main event loopa Linux install server that simplifies tasks associated with fully automated installation such as DHCP, DNS, kickstart, yum, and therefore from the user's mouse/keyboard inputvirtualization. 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. When the user does something, how long does One idea is to extend cobbler web to produce views that make it take easier for Mozilla users to act on edit fields that stimulus? only they edit (let me reinstall systems I own but don't show me fields I shouldn't care about). One thing that sometimes interferes with interface responsiveness Another is spending too long away from to enable search features in the main event loopweb app to make it tolerate thousands of systems to a better extent. Finally, perhaps in layout or some other intensive computation. This leads another feature is to add a task engine to new events from the usercobblerd, such as mouse clicks or keypresses, not being noticed to make it possible to run commands like "cobbler import" and acted upon. This could also be expanded "cobbler reposync" in order to include the triggering of log points background and specific dialog openings, etc. with a view to understanding what see their output in the long-running events actually areweb interface via an AJAXy type system.
References: httpPossible 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 wide variety of potential ideas, and ideas beyond the ones listed are also fair game. See https://shaver.offfedorahosted.net/diary/2007/08/25/tbeachball/ and http:/org/shaver.off.netcobbler/miscreport/latency-tracing-patch.txt1?sort=type&asc=1
== Port distcc to MSYS ==Resources: http://fedoraproject.org/cobbler
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 [httpContact://developer.mozilla.org/en/docs/Windows_Build_Prerequisites Mozilla Win32 build docs). Port distcc so that it works with the new MSYS environment.Michael DeHaan
References: Cesar and Tom== Personal Koji Repositories ==
== Add Multi-File transfer Koji Personal Repos (KoPeR) is a concept to distcc ==allow Fedora maintainers to create personal repos of packages to build against and share with others.
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 buildsResources: http://fedoraproject.org/wiki/JesseKeating/KojiPersonalRepos
ReferencesContact: Cesar and TomJesse Keating
== Add password managers for various platforms Port Wubi to Fedora ==
Previous work was done on adding [[OS X Keychain integration]] If upstream is willing to Firefox. This work was focused on tightly binding C++ integrate it, port wubi-installer and Mac API calls. Since then make it 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.mozillacross distribution.org/show_bug.cgi?id=309807 309807]Otherwise, [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]provide a similar implementation for Fedora.
Referenceshttp: dolske//wubi-installer.org/
== Convert password storage to a SQLite database Delta RPM support in Koji build system ==
Currently, Firefox stores logins in a text file in the user'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 the same kind of storage would be good. Some work was started in [ * https://bugzilla.mozillafedorahosted.org/show_bug.cgi?id=288040 bug 288040].bodhi/ticket/160
References: dolske== Benchmark Nightlife Scalability Issues ==
== Refactor master password out Using Puppet, or some other management tool, create a grid of NSS ==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.
Users can enable a "master password" in their browser, which securely encrypts all their stored passwords. The current implementation can be awkward to use and has some limitations, see Resource: [[https://bugzilla.mozilla.org/show_bug.cgi?id=322617 bug 322617fedora:Nightlife|Nightlife wiki page]]. 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 encrypt/decrypt entries. Matthew Farrellee
== Add Offline Support to an open source web app Create Test Suite for Condor ==
Firefox 3 will support offline abilitiesAlong with a good build infrastructure, such a strong test framework and methodology is key to survival of modern software. Condor is a system that web developers can write their apps so they is shipped on, currently, 14 different platforms - OS + Arch combinations. New features need to be verified to work even when on all those platforms and shown to cause no network is presentregressions in other features. Good headway Condor has been made already [http://www.bluishcodera large test suite, but no suite covers everything or in sufficient depth.co.nz/2007/02/offline-zimbra-with-firefox.html porting Zimbra]. Pick another web app a few features, say the VM Universe or Concurrency Limits, and add offline supportdemonstrate full understanding of them by testing all of the corner cases. This is far from a simple task, for example: [http://moodleand requires more than a cursory understand of the system to properly complete.org Moodle]Understanding the complex interactions of distributed components, common patterns exist across many distribute systems, as well as intimate interactions with the OS is key.
ReferencesResource: mfinkle[[:fedora:Nightlife|Nightlife wiki page]], Matthew Farrellee
== Thunderbird SMTP Auto-Sensing ==-- Below: Commented out by Chris Tyler 2008-08-31 -- I think we'll get all the students doing this.
Modify Thunderbird so that it uses the correct SMTP server for your current network and IP. In other words, if 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.== Review Packages ==
References: #maildevThere is a lot of 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.
== [[Bugzilla component-watching]] ==The general process is described in http://fedoraproject.org/wiki/PackageMaintainers/HowToGetSponsored and in http://fedoraproject.org/wiki/Packaging/ReviewGuidelines.
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. === Review Requests 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* Unassigned review requests - http: reed, [https//fedoraproject.org/PackageReviewStatus/NEW.html* In progress review requests - http://bugzillafedoraproject.mozillaorg/wiki/PackageMaintainers/InProgressReviewRequests* Approved review requests - http://fedoraproject.org/show_bug.cgi?id=76794 Bug 76794]wiki/PackageMaintainers/ApprovedReviewRequests-->
== Litmus Extension =Potential Mozilla Projects =
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-GonsalvesSample Project]], who created the Buggy Bar extension.==
== This is a sample project stub. You can use the template for [["Avoid loading the same page twice" ExtensionSample Project]] ==in order to create a project page for one of the stubs below. This is how you 'sign-up' for a project.
Create an extension NOTE: if someone has already created the project page, speak to Firefox this person and see if you can join them. If so that when a bookmark is clicked, and that site is already open in any tab in any window, that tab/window is brought simply add your name to the front rather than loading the '''Project Leader(s)''' page again. Otherwise, you can become a contributor later.
Related tech and skills: XUL, JavaScript== Improve Localization build system ==
== Firebug "linting" for portability problems ==Currently it requires many many steps to produce another language of Firefox.It would really easy to package these many steps to reduce the required knowledge to generate a new language.
Lots of web developers use Firebug Adding a few make steps to wrap this process would help everyone.This is a very easy project to tackle but very benefitial if the time and Firefox for building their applications, but we want those apps love is given 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.
ResourcesReference: mfinklearmenzg
== AddCreate a cross-on update helper tools for developers repo pushlog to see all locales's checkins ==We currently check many different repositories to trigger builds when a developer makes a change. We also check the localizer's repositories to see if they have pushed any changes. The problem is that we have close to eighty different localization repositories and that takes a long time to check each one of them.If we had a joint view that would improve our systems. An example of that view is:https://l10n-stage-sj.mozilla.org/pushes/but the format should be more like this:http://hg.mozilla.org/mozilla-central/pushlogwhich is what our release engineering systems check for.This project would require you to hack hg and pushlog to make it work.armenzg has many blog posts explaining how to setup pushlog in your local machine.
As Firefox 3 gets ramped up, there are nearly 3000 addReference: armenzg -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.Bug 498641
Resources== Thunderbird SMTP Auto-Sensing == Modify Thunderbird so that it uses the correct SMTP server for your current network and IP. In other words, if 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. References: mfinkle#maildev
== 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== <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/MXR rely on regression-search/ 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/C++ 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: 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 by 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 correctlycode base == [http://en.wikipedia. It would be awesome org/wiki/DTrace DTrace] was created by Sun in OpenSolaris to allow developers to write simple scripts in order to have probe and instrument executing programs in a GCC plugin or tool built way not possible otherwise. One of the advantages of DTrace is that it allows you to turn on Elsa that 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 parse C++ properly for LXR/MXR add probes to extract all the useful informationparticular function. The results could be used to improve searching and syntax highlighting Writing the probes is not difficult, however there are hundreds or thousands of probes that Mozilla would like across its code baseResources: sayrer
References:== Plugin Code Test Suite == # Create a [http://wikideveloper.mozilla.org/DeHydra# 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 involve creating a plugin or set of plugins and some html/js to drive that plugin in order to push test coverage. Maybe look at the JRE tests, create some specific plugin cases (e.g., swf to load that tests flash specific code). The newly announced Google Chromium browser [http://wikidev.mozillachromium.org/Dehydra_GCC# developers/how-tos/getting-around-the-chrome-source-code seems to have something like this] with regard to using the npapi for driving tests via plug-in. See also docs on [http://wwwdev.cschromium.berkeley.eduorg/~smcpeakdevelopers/elkhounddesign-documents/# inter-process-communication IPC] and [http://timelessdev.justdavechromium.netorg/mxrdevelopers/design-testdocuments/webtools/source/lxr/genxrefplugin-architecture plug-in design] in Chromium. This will require C programming, as well as light web development (html, js, perhaps swf). Resources: 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
 
== <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.
 
TODO: more info....
 
Resources: humph, taras
 
== Existing Subjects proposed by OpenOffice.org Education Project ==
 
FIXME : the projects proposed on the OpenOffice.org Education Project will be adapted to the current section.
 
Waiting we encourage you to have a look at the '''[http://wiki.services.openoffice.org/wiki/Education_Project/Effort OpenOffice.org Education Project Effort page]'''
 
Other links:
 
[http://wiki.services.openoffice.org/wiki/Education_Project OpenOffice.org Education Project on the Wiki]
 
 
[[User:Ericb|Ericb]] 21:05, 26 September 2008 (UTC)
3
edits