3
edits
Changes
m
The gratis release of Cobbler is a collection of web fonts in 1996 had a devastating effect on many font projectsLinux install server that simplifies tasks associated with fully automated installation such as DHCP, DNS, kickstart, yum, drainning the font market in western countries and limiting the use of other typefaces virtualization. It aims to typography nichesbe a universal install server for all linux distributions. However, this program Currently Cobbler has been discontinued and the gratis versions a web interface that allows users an easier way of those fonts interacting with cobbler. There are no longer updatedseveral core improvements that can be made. Since Unicode.org 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's codification pace of human scripts has not abated, and the font formats have evolved (with the OpenType specificationst care about), this font set . Another is increasingly obsoleteto enable search features in the web app to make it tolerate thousands of systems to a better extent. Also Finally, many scripts were never coveredanother feature is to add a task engine to cobblerd, leaving entire world regions without mass access to a way make it possible to write run commands like "cobbler import" and "cobbler reposync" in the background and see their language output in the digital ageweb interface via an AJAXy type system.
An operating system 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 wide variety of browser that relies on potential ideas, and ideas beyond the 1996 font set for its text rendering is not really freeones listed are also fair game. And text is still our main information media See https://fedorahosted.org/cobbler/report/1?sort=type&asc=1
Faced with this problem many individuals and organisations have started creating and publishing new fonts, but they lack the clout of multinationals to get successfully distributed, and are often poorly structuredResources: http://fedoraproject. 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 a core component of Fedora's art spin, and as basis for a richer international experience in Fedora (and derivatives such as OLPC)org/cobbler
This project is mainly targeted at free software (in this case fonts) distribution dynamics. You'll learn some rpm packaging skills, and be exposed to many different font projects worldwide, some big, some small, some efficient, some poorly run. A project second stage would be to capitalize on the experience acquired and publish a set of distribution best practices for font authors, including recommended release composition, generic makefile, etc. The Fedora [http://fedoraproject.org/wiki/Categories:Fonts_SIG Fonts special interest group] will provide mentoring, technical support, and [http://fedoraproject.org/wiki/Category:Fonts_packaging documentation]. An initial [http://fedoraproject.org/wiki/Category:Font_wishlist list of fonts to package] has already been published. Contact: Nicolas Mailhot <nim AT fedoraproject.org> == Corresponding Source Web App == Finish design and implement web application that provides downloadable SRPMS for any package+tag in the Fedora Package Source Code Control system. While we provide SRPMS for all packages at release, the updates and rawhide trees churn their packages more rapidly, and will remove 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 otherwise. Resources: MattDomsch, http://git.fedorahosted.org/git/?p=correspondingsource.git;a=blob;f=DESIGN;hb=HEADMichael DeHaan
JBoss is Using Puppet, or some other management tool, create a Java middleware project with grid of a large number of sub projectsdozen machines, then turn that into 12,000 machines. Packaging JBoss and maintaining them is a challenging task and would require several weeks of full time Address the network characteristics - how much bandwidth do you need on different components, the communication mechanisms - does UDP work. Since OpenJDK and at such a number of Java components is already in Fedora 9scale, it should help get startedthe grid topology - what happens when two nodes are behind firewalls.
Initial ContactResource: Greg Dek <gdk AT redhat.com>[[:fedora:Nightlife|Nightlife wiki page]], Matthew Farrellee
References:== Create Test Suite for Condor == Along 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 * http://fedoraprojectkey.org/wiki/Packaging/Java* httpResource: [[:fedora://jpackage.orgNightlife|Nightlife wiki page]], Matthew Farrellee
<!-- - Below: Commented out by Chris Tyler 2008-08-31 -- I think we'll get all the students doing this.
Resources: ctyler, (roc, callion for dbus)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.
== Create Adding a MDRK Spin ==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.
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.Reference: armenzg
Edit == 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 spin image (from Revisor/Live CD Tools) so 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, in addition takes a long time to being check each one of them.If we had a bootablejoint view that would improve our systems. An example of that view is:https://l10n-stage-sj.mozilla.org/pushes/installable disc, but the image can format should be run in a VM under Windowsmore like this:http://Mac OSXhg. The disc image must be edited to include Windowsmozilla.org/mozilla-central/Mac OSX versions of the tools, so that if the disc pushlogwhich is inserted into a running Windows or Mac OSX system, the appropriate version can be installedwhat 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.
ResourcesReference: humph, ctyler, http://142.204.133.123/mxr, http://zenit.senecac.on.ca/wiki/dxr = Potential Mozilla 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. == 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-zimbraarmenzg -with-firefox.html porting Zimbra]. Pick another web app and add offline support, for example: [http://moodle.org Moodle]. References: mfinkleBug 498641
== 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, robcee== <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.sResources: plasticmillion, mfinkle, #mozpad, #prism</strike>
== [[Spellcheck Extension <strike>Write an extension to leverage the existing spellcheck code in Mozilla and add the ability to highlight spelling mistakes for Arbitrary Web Pages]] ==a given web page (i.e., vs. a textbox).</strike>
Write an extension == <strike>Modify Firefox to leverage the existing spellcheck code in Mozilla and add the ability handle files downloaded to highlight spelling mistakes for a given web page (i.e., vs. a textbox).Temp more appropriately </strike>==
== Modify Firefox to handle files downloaded to Temp more appropriately == <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:
== 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
It's "Specifically, Mozilla has a well known fact that it takes longer to great system called “try servers” where one can submit patches against the tree, and the build system runs builds on Windows than on a comparable Linux or , Mac machine. We don't know exactly whyand Windows, however. There have been many theoriesusing those patches, but no real datathen serves those builds for testing. Profiling the build system would allow us This is really helpful to figure out where all of the time is being spentif proposed patches solve specific problems... The best place only problem is that there’s a little bit of patching needed to start might be by adding some profiling the try server code itself to GNU Make, make it able to figure out which work with other targets besides Firefox, as described in our makefiles take the most timebug 431375" ([http://ascher. From there, depending on the results, profiling could be added to other parts of the ca/blog/2008/05/02/thunderbird-team-needs-help-from-pythonperl-build system to narrow down specific bottlenecks.-assist/ Ascher])
References== 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 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://wikidev.serviceschromium.openofficeorg/developers/design-documents/inter-process-communication IPC] and [http://dev.chromium.org/wikidevelopers/design-documents/BuildSpeedup plugin-architecture plug- OpenOfficein 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 == Mozilla has a symbol server which is used by developers to debug issues in release builds that don't include debug information (i.e., symbols). However, many crashes are related to third-party binary plugins or extensions, for which Mozilla has no symbols. This project would create a web-based self-serve solution for third-parties to upload symbols for their binary components in breakpad-formatted .sym file format. Ideally this could happen in an automated way, such that third-parties could add a step to their build system to do it automatically with each release. See [https://bugzilla.mozilla.org did something similar/show_bug.cgi?id=419879 bug# 419879].
Make it possible to look for bugs across old nightly builds of Firefox using automated tools. For example, <strike>Mozilla [http://db48xmxr.mozilla.netorg/regressionmozilla-searchcentral/source/dom/tests/mochitest/ regression-searchajax/ uses] is a script that allows you many common JavaScript library test suites to add additional coverage to do binary searches across binaries, looking for the existence of a bugit's JavaScript implementation. This One test suite that is not currently used by Mozilla, but could be improved through , is the use of tools like [http://servicesopenlayers.alphaworksorg OpenLayer's] js [http://trac.ibmopenlayers.comorg/browser/coscriptertrunk/browseopenlayers/about co-scriptertests test suite]. Ideally the user could look for bugs in automated ways, without having to download and install tons of browser versionsSee [https://bugzilla.mozilla.org/show_bug.cgi?id=399311 bug# 399311].
We're just starting to use <strike>Mozilla uses an exciting new embedded version of [http://betterexplainedwww.sqlite.comorg/ SQLite] extensively to [http://articlesdeveloper.mozilla.org/intro-to-distributed-version-control-illustrateden/ distributed version controlstorage store data] tool: 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://developermxr.mozilla.org/enmozilla-central/source/storage/test/docsunit/Mercurial Mercurialtest_like.js work has already been done], but more is required to get full test coverage.
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 linearReferences: [https://bugzilla. It frequently has ''branches'' and ''merges''mozilla.org/show_bug. This is actually a good, important featurecgi?id=391756 bug 391756], 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://officewww.smedbergs0xdeadbeef.uscom/viewerweblog/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).?p=368
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 ([httpResources:sdwilsh <//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''.strike>
Your mission is to rectify this sad situation by writing an awesome browser-based UI for navigating Mercurial repository historyTake : [http://zenit.senecac.on.ca/wiki/index.php/Import_sqlite_test_suite Park,KiWon]
Resources: jorendorff, bsmedberg == Extend Try Server to test Make chromebug work in Thunderbird patches ==
"Specifically, Mozilla has a great system called “try servers” where one can submit patches against the tree, and the build system runs builds on Linux, Mac and Windows, using those patches, then serves those builds for testing. This is really helpful to figure out if proposed patches solve specific problems...The only problem is that there’s a little bit of patching needed to the try server code itself to make it able to work with other targets besides Firefox, as described in bug 431375" ([http://ascher.ca/blog/2008/05/02/thunderbird-team-needs-help-from-pythonperl-build-assist/ Ascher])TBD
Many (poorly behaved) web sites attempt to move and/or resize your browser window. It is possible to stop this behaviour (cf. dom.disable_window_move_resize) but it would be nice to have an infobar that informed the user that a web page attempted to move/resize the window, and allow it or ignore it (default). This behaviour is similar to the current Pop-up Blocker already present in Firefox. NOTE: it is not clear whether such a feature would be accepted in the tree or if this would need to be done as an extension.TBD
[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 would like across its code base.TBD
== Colour Management Tests ==
Write [http://developer.mozilla.org/en/docs/Creating_reftest-based_unit_tests reftests] to compare images in order to deal with floating point tolerance. This includes dealing with things like Monitor Profiles, profiles in JPEG (i.e., JPEGs get changed based on colour profile info). See discussion of colour profiles in Firefox 3 [http://www.dria.org/wordpress/archives/2008/04/29/633/ here]. It would be useful to be able to compare to PNGs with a reftest, perhaps creating an image diff tool, where pixels outside a floating point tolerance (> 0.n) would somehow be highlighted so you can see what is different. Little CMS (lcms) needs test coverage too.
This will require some graphics and image knowledge (i.e., Photoshop, what colour is on a computer, etc).== HTML page set sanitizer ==
Resources: #gfxThe 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, joesince they're mirrors of copyrighted web pages. In addition, vladmany 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.
== Plugin Code Test Suite ==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.
Create a [httpResources://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 ted (e.g., swf to load that tests flash specific codebut find someone better!). 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.
'''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 =
Lots of good ideas are listed in [[:fedora: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.
== Free-open font packaging Cobbler Web ==
== Personal Koji Repositories ==
* https://fedorahosted.org/bodhi/ticket/160
== Packaging JBoss Benchmark Nightlife Scalability Issues ==
== Review Packages ==
-->
= Potential Fedora+Mozilla 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.
== NetworkManager Web Authentication Improve Localization build system == [http://www.gnome.org/projects/NetworkManager/ 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 and wireless networks such as [http://www.senecac.on.ca/senenet/ SeneNET] and [http://www.yorku.ca/computng/students/internet/airyork/index.html AirYork]. Modify NetworkManager so that it talks (though dbus) to a Firefox extension for automatic login to a web-authenticated network.
== Thunderbird SMTP Auto-Sensing ==
References: #maildev
Help to develop an [http://www.mozpad.org/doku.php?id== application_build_system_project automated packaging system] for XULRunner Application Packaging ==applications.
== 'Compact databases' feature for Mozilla calendaring applications (Lightning, Sunbird) ==
Resources: ctalbert, daniel in #calendar on irc.mozilla.org
== Thunderbird Draft Scheduler <strike>[[Spellcheck Extension for Arbitrary Web Pages]]</strike> == 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
* 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=280419 bug 280419] and [https://bugzilla.mozilla.org/show_bug.cgi?id=369108 bug 369108], and code [http://mxr.mozilla.org/mozilla-central/source/uriloader/exthandler/nsExternalHelperAppService.cpp#2077 here].
== Standalone Test Harnesses ==
References: Ben Hearsum (bhearsum), Rob Helmer (rhelmer)
== Port the Firefox Release Repackager to other platforms ==
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 build system (why are my Windows builds so slow?) 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 ==
Resources: ted
== RegressionTry <strike>Add OpenLayers test suite to Mozilla </strike>==
Resources: db48x, tedsayrer</strike>
== Mercurial history browsing <strike>Import sqlite test suite</strike> ==
== Add an Infobar style warning for window resize/Help gristmill move forward in Thunderbird ==
== Add DTrace probes and scripts for Mozilla code base Help Calendar integration on Trunk ==
Resources: sayrerFallen
== 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 will require C programming, as well as light web development (htmlparticular project looks at how to perform "picking". That is, jswhen given a coordinate within the canvas, perhaps swf)return the 3D object at that location.
Resources: jstcathy, Andor (http://www.c3dl.org)
= Potential OOo Projects =
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)
