Difference between revisions of "Universal Firefox on a USB Key"

From CDOT Wiki
Jump to: navigation, search
(Universal Firefox on a USB Key)
(Project Description)
Line 3: Line 3:
 
== Project Description ==
 
== Project Description ==
  
Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, http://google.com or [http://developer.mozilla.org MDC].
+
Create a portable USB installation of Firefox that will work on all of Windows, Linux, and Mac. Currently there are binaries for doing this with Windows/Linux. You'll need to get binaries for the app on each platform, figure out how to share a common profile, and get it all on a single USB key.
 +
 
 +
Resources: sxip/dick, http://developer.mozilla.org/en/docs/Chrome_Registration#platform_.28Platform-specific_packages.29, http://developer.mozilla.org/en/docs/Bundles#Platform-specific_Subdirectories, http://ted.mielczarek.org/code/mozilla/crashme.xpi
  
 
== Project Leader(s) ==
 
== Project Leader(s) ==

Revision as of 23:21, 24 January 2008

Universal Firefox on a USB Key

Project Description

Create a portable USB installation of Firefox that will work on all of Windows, Linux, and Mac. Currently there are binaries for doing this with Windows/Linux. You'll need to get binaries for the app on each platform, figure out how to share a common profile, and get it all on a single USB key.

Resources: sxip/dick, http://developer.mozilla.org/en/docs/Chrome_Registration#platform_.28Platform-specific_packages.29, http://developer.mozilla.org/en/docs/Bundles#Platform-specific_Subdirectories, http://ted.mielczarek.org/code/mozilla/crashme.xpi

Project Leader(s)

Project Contributor(s)

Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki

NOTE: only Project Leader(s) should add names here. You can’t add your own name to the Contributor list.

Project Details

Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them.

Project News

This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc.

Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.