3
edits
Changes
m
Finish design Cobbler is a Linux install server that simplifies tasks associated with fully automated installation such as DHCP, DNS, kickstart, yum, and implement 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 application to produce views that provides downloadable SRPMS make it easier for any package+tag 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 Fedora Package Source Code Control systemweb app to make it tolerate thousands of systems to a better extent. While we provide SRPMS for all packages at release 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 updates background and rawhide trees churn see their packages more rapidly, and will remove output in the koji-built SRPMS when the binary packages are removed. This would allow people to request source corresponding to the packages they have on ISO media or otherwiseweb interface via an AJAXy type system.
Resources: MattDomschPossible 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, httpand ideas beyond the ones listed are also fair game. See https://git.fedorahosted.org/gitcobbler/report/1?psort=correspondingsourcetype&asc=1 Resources: http://fedoraproject.git;a=blob;f=DESIGN;hb=HEADorg/cobbler Contact: Michael DeHaan
The gratis release of a collection of web fonts in 1996 had a devastating effect on many font projects, drainning the font market in western countries and limiting the use of other typefaces to typography niches. However, this program has been discontinued and the gratis versions of those fonts are no longer updated. Since Unicode * https://fedorahosted.org's codification pace of human scripts has not abated, and the font formats have evolved (with the OpenType specifications), this font set is increasingly obsolete. Also, many scripts were never covered, leaving entire world regions without mass access to a way to write their language in the digital age./bodhi/ticket/160
An operating system of browser that relies on the 1996 font set for its text rendering is not really free. And text is still the may information age material.== Benchmark Nightlife Scalability Issues ==
Faced with this problem many individuals and organisations have started creating and publishing new fontsUsing Puppet, but they lack the clout or some other management tool, create a grid of multinationals to get successfully distributeda dozen machines, then turn that into 12, and are often poorly structured000 machines. The aim of this project would be to identify as many of those free fonts as possible and package them in Fedora. The result would serve as Address the network characteristics - how much bandwidth do you need on different components, the communication mechanisms - does UDP work at such a core component of Fedora's art spinscale, and as basis for a richer international experience in Fedora (and derivatives such as OLPC)the grid topology - what happens when two nodes are behind firewalls.
This project is mainly targeted at free software (in this case fonts) distribution dynamics. You'll learn some rpm packaging skillsResource: [[:fedora:Nightlife|Nightlife wiki page]], and be exposed to many different font projects worldwide, some big, some small, some efficient, some poorly run.Matthew Farrellee
A project second stage would be to capitalize on the experience acquired and publish a set of distribution best practices == Create Test Suite for font authors, including recommended release composition, generic makefile, etc.Condor ==
The Fedora [http://fedoraprojectAlong with a good build infrastructure, a strong test framework and methodology is key to survival of modern software.org/wiki/Categories:Fonts_SIG Fonts special interest group] will provide mentoringCondor is a system that is shipped on, technical supportcurrently, 14 different platforms - OS + Arch combinations. New features need to be verified to work on all those platforms and [http://fedoraprojectshown to cause no regressions in other features.org/wiki/Category:Fonts_packaging documentation]Condor has a large test suite, but no suite covers everything or in sufficient depth. An initial [http://fedoraprojectPick a few features, say the VM Universe or Concurrency Limits, and demonstrate full understanding of them by testing all of the corner cases.org/wiki/Category:Font_wishlist list This is far from a simple task, and requires more than a cursory understand of fonts the system to package] has already been publishedproperly 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.
ContactResource: FAS2/nim[[:fedora:Nightlife|Nightlife wiki page]], Matthew Farrellee
= Potential Fedora+Mozilla Projects =--- Below: Commented out by Chris Tyler 2008-08-31 -- I think we'll get all the students doing this.
== NetworkManager Web Authentication ==There 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.
[The general process is described in http://www.gnomefedoraproject.org/projectswiki/NetworkManagerPackageMaintainers/ NetworkManager] knows how to connect to many different types of networks, both wired and wireless, and can auto-authenticate to WEP and WPA networks. However, it can't auto-authenticate to networks that require a web-based login, which includes many wired HowToGetSponsored and wireless networks such as [in http://wwwfedoraproject.senecac.on.ca/senenet/ SeneNET] and [http://www.yorku.caorg/computngwiki/studentsPackaging/internet/airyork/index.html AirYork]ReviewGuidelines.
Modify NetworkManager so that it talks (though dbus) to a Firefox extension for automatic login to a web-authenticated network.=== Review Requests ===
Resources* Unassigned review requests - http: ctyler, (roc, callion for dbus) == Create a MDRK Spin == The [[Mozilla Developer Resource Kit]] is a set of tools, code, and documentation intended to make it easy for new Mozilla developers to get up to speed. Package the MDRK components (including the software tools, a Moz source tree, and documentation) as RPM packages and then create a Fedora "spin" (Live + Installable DVD) of these packages. Edit the spin image (from Revisor/Live CD Tools) so that, in addition to being a bootable/installable disc, the image can be run in a VM under Windowsfedoraproject.org/Mac OSX. The disc image must be edited to include WindowsPackageReviewStatus/Mac OSX versions of the tools, so that if the disc is inserted into a running Windows or Mac OSX system, the appropriate version can be installedNEW.html Resources: humph, ctyler, * In progress review requests - http://142fedoraproject.204.133.123org/wiki/PackageMaintainers/mxr, InProgressReviewRequests* Approved review requests - http://zenitfedoraproject.senecac.on.caorg/wiki/dxrPackageMaintainers/ApprovedReviewRequests-->
References: reed, [https://bugzillaCurrently it requires many many steps to produce another language of Firefox.mozillaIt would really easy to package these many steps to reduce the required knowledge to generate a new language.org/show_bug.cgi?id=294608 bug 294608]
== Tbeachball - Quantifying Mozilla's Responsiveness == 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 love is given to it.
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.Reference: armenzg
References== 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 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: httphttps://shaverl10n-stage-sj.offmozilla.netorg/diarypushes/2007/08/25/tbeachball/ and but the format should be more like this:http://shaverhg.offmozilla.netorg/miscmozilla-central/latency-tracing-patchpushlogwhich 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.txt
== Convert password storage to a SQLite database == 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.mozilla.org/show_bug.cgi?id=288040 bug 288040]. References: dolske == Refactor master password out of NSS == 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 [httpsReference://bugzilla.mozilla.org/show_bug.cgi?id=322617 bug 322617]. Fixing this would involve having password manager being more involved with the cryptography operations -armenzg - deriving a key from a passphrase with PKCS#5, and using NSS and PKCS#11 to encrypt/decrypt entries. == Add Offline Support to an open source web app == Firefox 3 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: mfinkleBug 498641
== [["Avoid loading the same page twice" Extension]] ==
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.
Related tech and skills: XUL, JavaScript
== 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.
Resources: mfinkle
== Add-on update helper tools for developers ==
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
== 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
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
Make it possible to look for bugs across old nightly builds of Firefox using automated tools. For example, [http://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.alphaworks.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.TBD
== Mercurial history browsing ==
We're just starting to use an exciting new [http://betterexplained.com/articles/intro-to-distributed-version-control-illustrated/ distributed version control] tool: [http://developer.mozilla.org/en/docs/Mercurial Mercurial].
One of the exciting things about Mercurial is that the history—the list of all 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://office.smedbergs.us/viewer/index.xhtml#mozilla-central:acb5456539c668d3ec0ec755dd3b64ddb56363d2 Benjamin Smedberg'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).== HTML page set sanitizer ==
There have been a couple attempts The Talos performance testing system at showing history in an intuitive, graphical way. Mercurial comes with Mozilla currently runs on a large set of web UI for browsing pages pulled from the repositoryAlexa Top 500. These pages can't be redistributed, including history ([http://hgsince they're mirrors of copyrighted web pages.mozilla.org/mozilla-central/indexIn addition, many of them contain adult content.cgi/log/13540 here's what This makes it looks like]). It also comes with an "hg glog" extension difficult for people to duplicate the Talos results or to test changes that draws history as ASCII art, and have an "hg view" extension that does roughly the same thing with a little GUI. Sadly, none of these applications qualifies as ''awesome''expected performance impact.
Your mission is A useful solution to rectify this sad situation problem would be a tool that takes a mirrored copy of a website and "sanitizes" it, by writing an awesome browser-based UI for navigating Mercurial repository historychanging 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.
"SpecificallyResources: cathy, 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" Andor ([http://ascherwww.c3dl.ca/blog/2008/05/02/thunderbird-team-needs-help-from-pythonperl-build-assist/ Ascher]org)
'''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 =
== Ideas Pool ==
Lots of good ideas are listed in http[[:fedora://fedoraproject.org/wiki/SummerCoding/2008/Ideas|Summer Coding Ideas (Fedora Wiki)]]. These 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.
== Corresponding Source Cobbler Web App ==
== Personal Koji Repositories ==
http://wubi-installer.org/
== Free-open font packaging Delta RPM support in Koji build system ==
== [[Sample Project]] Review Packages == 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.
= Potential Mozilla Projects =
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 Improve Localization build system == Use the canvas element in order to create a generic front-end for data visualization of the Mozilla source. Many types of information about the Mozilla project can be keyed to the source tree. For example, file change-rates, code-coverage, bug activity per module, checkins per module, etc. The visualization will be a heatmap, showing certain types of activity in the tree. Doing this visualizaiton using canvas3d would allow for a third axis, and changes over time to be shown. Resources: Cathy == Mozilla Data Visualization Back-ends == 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. Resources: Cathy == Add OpenID support to Bugzilla == 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.
== Thunderbird SMTP Auto-Sensing ==
References: #maildev
== <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
== 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
== 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
== Profile RegressionTry == Make it possible to look for bugs across old nightly builds of Firefox using automated tools. For example, [http://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.alphaworks.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: 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 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" (why [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 my Windows builds so slow?hundreds or thousands of probes that Mozilla would like across its code base. 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 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://dev.chromium.org/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://dev.chromium.org/developers/design-documents/inter-process-communication IPC] and [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) . Resources: jst == Create self-serve symbol upload system ==
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 ==
Resources: db48x, tedFallen
Resources: jorendorff, bsmedbergted (but find someone better!)
== Extend Try Server to test Thunderbird patches 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.
= Potential OOo Projects =
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)
