MozillaTeam

Differences between revisions 29 and 74 (spanning 45 versions)
Revision 29 as of 2007-01-11 12:37:07
Size: 2629
Editor: 82-44-193-109
Comment:
Revision 74 as of 2015-05-26 14:35:14
Size: 2829
Editor: bryanquigley
Comment: remove mailing list
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
{{{
Please consider all information found in this and it's sub pages as the opinions of the authors rather than Ubuntu policy until this disclaimer has been removed with the approval of the technical board and community council.
}}}
<<Include(MozillaTeam/Header)>>
Line 5: Line 3:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>||
Line 7: Line 5:
== Vision == == Welcome ==
Line 9: Line 7:
As a team, we hope to create a place where people can come together to help improve the user's experience with software the Mozilla Foundation releases on the Ubuntu platform. Welcome to the home of the Ubuntu Mozilla Team, we are the guys and gals that deal with most of the requests based on Mozilla [[MozillaTeam/Packages|software]]. We are dedicated to triaging, fixing, testing, and providing support for all the applications throughout the suite. Please see our [[MozillaTeam/Roadmap|road map]] for tasks we are working on. It is a vast operation as these applications are highly visible within Ubuntu, however it's a challenge that we all relish.
Line 11: Line 9:
== Goals ==
 
 1. To report, triage, and fix bugs relating to Mozilla software.
== Communication ==
Line 15: Line 11:
 2. To work closely with upstream developers on technical, professional, and personal levels. On IRC, on the Freenode server '''irc.freenode.net''' at #ubuntu-mozillateam.
Line 17: Line 13:
 3. To create an environment which both attracts experienced developers and helps new developers improve their skills. == Getting Involved ==
Line 19: Line 15:
 4. To have fun. === Bug Reporting ===
Line 21: Line 17:
== Joining the team == The [[MozillaTeam/Bugs|bug reporting]] page contains useful information on how you can report bugs in a way that will helps the team to process them more efficiently.
Line 23: Line 19:
What to join the team? Information can be found at ["MozillaTeam/Membership"]. === Bug Triage ===
Line 25: Line 21:
== Team Meetings == If you want to join the Mozilla Team or just want to help out, triaging bugs is a fairly easy task that always needs to be done. Information on bug triaging can be found on [[MozillaTeam/Bugs/Procedures|triage procedures]].
Line 27: Line 23:
The next meeting is on Thursday 11th January 2007, at 5pm UTC, in #ubuntu-mozillateam. === Bug Fixing ===
Line 29: Line 25:
Please see ["MozillaTeam/Meetings"] for more details. The next step is fixing the properly triaged issue reports, more information can be found on our [[MozillaTeam/Develop|development]] page.
Line 31: Line 27:
== Quick Links ==
=== Squashing Bugs ===
==== Reporting a bug ====
=== Quality Assurance ===
Line 35: Line 29:
 If you want to report a bug, please go to ["MozillaTeam/Bugs"]. We document our QA procedures in [[MozillaTeam/QA]]
Line 37: Line 31:
==== Triaging a bug ==== ==== Preview Testing ====
Line 39: Line 33:
 Please go to ["DebuggingFirefoxDevels"], or ["MozillaTeam/Bugs/Triage"] which is the experimental new page for bug triagers. The last step is testing our new build before pushing them in the Ubuntu repositories. We have a set of [[MozillaTeam/PreviewArchives|preview archives]] for testing recent fixes.
Line 41: Line 35:
 To see the procedures for triaging other bugs, please go to ["DebuggingProcedures"] ==== Trunk Testing ====
Line 43: Line 37:
==== Fixing a bug ==== We don't provide prebuilt binary packages for the main firefox development line (aka trunk).
Line 45: Line 39:
 Please go to ["MozillaTeam/DevelopingFirefox"]. (Under construction). To test trunk (e.g. firefox 3.0 alpha) you can build the latest bzr sources. See [[MozillaTeam/BuildTrunk]] for instructions.
Line 47: Line 41:
=== Swimming Upstream === === Wiki Maintenance ===
Line 49: Line 43:
When reporting upstream bugs in plugins (such as Java or Flash), make sure you file your bug report in the right place. You can check which plugin you're using by going to the URL about:plugins in your Mozilla browser. At the present moment the wiki is growing quickly, we need a few more people to help get it into shape, please see our [[MozillaTeam/Wiki|wiki standards]] page for more information.
Line 51: Line 45:
==== Debian ==== == Mozilla extensions ==
We used to try to include a lot of extensions in the Ubuntu archive; that's no longer the case. There are some key ones, like Ubufox, Unity-*, etc.
Line 53: Line 48:
 * [http://www.debian.org/Bugs/ Debian] I've deleted most of the pages regarding extentions from 2008, but a few looked like they could still be useful under [[MozillaTeam/Extensions/List]]
Line 55: Line 50:
==== Mozilla ==== == Subpages ==
Line 57: Line 52:
 * [https://bugzilla.mozilla.org/ Mozilla] ||<tablestyle="width:90%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''This Team wiki page contains the following sub-pages:'''||
||<<Navigation(children,1)>>||
Line 59: Line 55:
==== Java ====
 * [http://bugs.sun.com/bugdatabase/index.jsp Sun Java]
 * [http://www.gnu.org/software/classpath/bugs.html GNU Classpath] (GCJ)

==== Flash ====

 * [http://www.adobe.com/misc/bugreport.html Adobe Flash]

 * [http://sourceforge.net/tracker/?group_id=110956&atid=657852 GPL Flash]

 * [https://savannah.gnu.org/bugs/?group=gnash Gnash]

=== Learning, Teaching, Growing ===

IRC freenode #ubuntu-mozillateam

== Getting Started ==

Does this sound interesting? ["MozillaTeam/GettingStarted"] is the place to jump in.
 
----
[[CategoryMozillaTeam]], [[CategoryBugSquad]]

Welcome

Welcome to the home of the Ubuntu Mozilla Team, we are the guys and gals that deal with most of the requests based on Mozilla software. We are dedicated to triaging, fixing, testing, and providing support for all the applications throughout the suite. Please see our road map for tasks we are working on. It is a vast operation as these applications are highly visible within Ubuntu, however it's a challenge that we all relish.

Communication

On IRC, on the Freenode server irc.freenode.net at #ubuntu-mozillateam.

Getting Involved

Bug Reporting

The bug reporting page contains useful information on how you can report bugs in a way that will helps the team to process them more efficiently.

Bug Triage

If you want to join the Mozilla Team or just want to help out, triaging bugs is a fairly easy task that always needs to be done. Information on bug triaging can be found on triage procedures.

Bug Fixing

The next step is fixing the properly triaged issue reports, more information can be found on our development page.

Quality Assurance

We document our QA procedures in MozillaTeam/QA

Preview Testing

The last step is testing our new build before pushing them in the Ubuntu repositories. We have a set of preview archives for testing recent fixes.

Trunk Testing

We don't provide prebuilt binary packages for the main firefox development line (aka trunk).

To test trunk (e.g. firefox 3.0 alpha) you can build the latest bzr sources. See MozillaTeam/BuildTrunk for instructions.

Wiki Maintenance

At the present moment the wiki is growing quickly, we need a few more people to help get it into shape, please see our wiki standards page for more information.

Mozilla extensions

We used to try to include a lot of extensions in the Ubuntu archive; that's no longer the case. There are some key ones, like Ubufox, Unity-*, etc.

I've deleted most of the pages regarding extentions from 2008, but a few looked like they could still be useful under MozillaTeam/Extensions/List

Subpages


CategoryMozillaTeam, CategoryBugSquad

MozillaTeam (last edited 2015-05-26 14:35:14 by bryanquigley)