You don’t have to be a coder to help improve Ubiquity. We’re looking for Javascript coders to help out, but we’re also looking for testers, translators, and people who can write good documentation.

Test and Triage Bugs

1. Issue Tracker – Used to report/discuss bugs and submit patches for Ubiquity.
2. Trac Components and Keywords – Keywords and categories to use when filing Trac tickets.

Write documentation

1. Help Document the 0.5 code here – working copies of the wiki documentation for the latest source version
2. Help us improve the built-in command documentation by editing this page
3. Help us improve the interactive tutorial by editing this page

Localize

Help localize Ubiquity to your language! Ubiquity has already been partly translated to Danish, English, Japanese, and Portugese, and volunteer localizers are working on many other languages too.

1. Localizing Ubiquity to Your Language
2. Localizing Commands to Your Language
3. Ubiquity i18n Google Group/mailing list for discussion of internationalization and localization topics

Help out other users

1. General Google Group/mailing list – Useful for discussion of command development, user interface, feature suggestions, and other high-level discussions.

Write code

1. Developer meetings are open to anyone to call into: main Mozilla number, extension 92, conference room 202, at 5pm Pacific time on Wednesdays. Any changes to the meeting schedule are announced on the mailing list.
2. Core Google Group/mailing list – Discussion of low-level internals of Ubiquity.
3. Ubiquity HG Repository – The Mercurial source code repository for Ubiquity.
4. Ubiquity Code Documentation – Generated from the latest source code via Code Illuminated.
5. Contributing to Core Development