667
edits
Changes
First pass at separating active from potential projects
You can get involved with any of the projects below. Please see [[Assignment 2]] for details. To join a project create a page for it, following the example of [[Sample Project]] below.
==[[Generalization of Joga extension]] ==
Related tech and skills: XUL, JavaScript, documentation, web services
== [[XULRunner Guide]] ==
Reference: http://cs.senecac.on.ca/fsoss/2006/workshop.html#XULRunner
== [[Updating JS guide and JS reference]] ==
Related tech and skills: documentation, JavaScript
== [[Bugzilla component-watching]] ==
Speed up Mozilla's builds by letting them use MSVC with distcc on Windows.
== [[Unit Testing]] ==
Reference: Work with Mozilla's Rob Campbell and Jay Patel from the QA Team.
== [[OpenGL Backend in Firefox 3]] ==
Administration of the Mozilla cluster at Seneca.
== [[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.
== SVN access control via LDAP ==
We have a tool called "[https://despot.mozilla.org/ Despot]" which gives us fine-grained control over access to the [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_Via_CVS Mozilla CVS repository]. As we start to have development hosted in [http://weblogs.mozillazine.org/preed/2006/08/subversive_subversion_conversi.html Subversion] (SVN), with account information maintained in [http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol LDAP], we'd like to have a tool to enforce and manage such controls there as well.
Related tech and skills: server config, LDAP, scripting, web interface/app development
Reference: See https://despot.mozilla.org/help.html and http://lxr.mozilla.org/mozilla/source/webtools/despot/README. Also, please speak with [[User:Reed|Reed Loden]] (reed) about this project.
== Updating and migrating of MDC content ==
The [http://developer.mozilla.org Mozilla Developer Center] has rights to a bunch of content that's still hosted on various strange corners of http://www.mozilla.org and the old [http://developer.mozilla.org/en/docs/DevEdge DevEdge] archives. There are some gems in there that need dusting off and updating to reflect the realities of the modern web.
Related tech and skills: web authoring, documentation, scripting, technology domains of chosen articles.
== Test framework development ==
We have a number of promising prototype or proof-of-concept test frameworks for exercising Mozilla code from different directions. They need varying amounts of work to make them more robust and general, document them, and integrate them into different kinds of automation.
Related tech and skills: Python, Perl, Makefiles, shell scripting, JavaScript
== OpenDarwin tinderbox image ==
We would love to have a [http://en.wikipedia.org/wiki/Tinderbox_%28software%29 Tinderbox] image (e.g., VM) for testing and building on the Mac, based on the [http://www.opensource.apple.com/darwinsource/ freely-available OS X source]. Also, we'd like to get it wired into [[User:Bhearsum|Ben Hearsum's]] (bhearsum) [http://en.wikipedia.org/wiki/Buildbot buildbot] system.
Related tech and skills: system configuration, scripting, light C/C++, Makefile
== FAQ mining for extension developers ==
Literally every day, there are informal exchanges on IRC (e.g., #extdev, #developers, #firefox, #seneca, etc.) and newsgroups that are fantastic fodder for small, focused documents. Collect these exchanges and fleshing them out as recipes for extension authors that include sample code.
== Functional Testing ==
Testing performed from a user's perspective. Includes the running and writing of test cases in [http://litmus.mozilla.org Litmus], filing and tracking bugs through [bugzilla.mozilla.org bugzilla], stress-testing and exploratory debugging. This project requires a dedication to breaking software in an organized and repeatable fashion. There is no such thing as "the wrong way" to use software and the functional tester is adept at abusing a system in previously-unknown ways.
Reference: Work with Mozilla's Rob Campbell and Jay Patel from the QA Team.
== Performance Testing ==
Extending the performance tookit and tinderbox reporting system. The project begins with a framework for testing pageloads and startup times in Win32. The successful completion of this project will see this framework develop into a more robust system complete with processor-timing information and graphing. Memory analysis and samples during runs would also be beneficial. Further success or subprojects could include porting the system Linux and OS X platforms.
Reference: [https://bugzilla.mozilla.org/show_bug.cgi?id=346785 Bug 346785]. Work with Mozilla's Rob Campbell and Jay Patel from the QA Team.
== Automated Testing ==
Programmatically driving the browser to perform human-like tasks repeatedly. The programmer will have to create a framework for driving browser components in JavaScript or other scripting language to repeatedly test various pieces of the application. Ideally, the successful completion of this task will see a test or suite of tests that can be invoked by command line to start the browser, run the test suites and then exit and record the results for display or analysis.
Reference: Work with Mozilla's Rob Campbell and Jay Patel from the QA Team.