MozillaTeam

Differences between revisions 39 and 74 (spanning 35 versions)
Revision 39 as of 2007-02-05 20:39:13
Size: 2571
Editor: 82-44-193-109
Comment: Buh Bye Disclaimer.
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:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| <<Include(MozillaTeam/Header)>>

||<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 5: Line 7:
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 based products, we are dedicated to triaging, fixing, providing support for all the applications throughout the suite. It is a vast operation as these applications are highly visible within Ubuntu, however it's a challenge that we all relish. 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 7: Line 9:
== How do I help? == == Communication ==
Line 9: Line 11:
The first step is to find the bugs, we are always on the lookout for bugs ourselves. More information can be found at ["MozillaTeam/Bugs"]. On IRC, on the Freenode server '''irc.freenode.net''' at #ubuntu-mozillateam.
Line 11: Line 13:
The next step is usually to triage the reports, essentially this means to gather enough information to enable a developer to come along, pick out the report and fix it without having to exchange in more conversation with the initial reporter. More information can be found at ["MozillaTeam/Bugs/Triage"]. == Getting Involved ==
Line 13: Line 15:
The last step is to fix the report, more information can be found at ["MozillaTeam/Develop"]. === Bug Reporting ===
Line 15: Line 17:
More information in general can be found at the getting started guide, ["MozillaTeam/GettingStarted"]. 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 17: Line 19:
== How do I join? == === Bug Triage ===
Line 19: Line 21:
Interested? More information can be found at ["MozillaTeam/Membership"]. 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 21: Line 23:
== Meetings == === Bug Fixing ===
Line 23: Line 25:
The next meeting, which will take place in {{{#ubuntu-meeting}}}, will be on Monday 5th February at 20:00 UTC. The next step is fixing the properly triaged issue reports, more information can be found on our [[MozillaTeam/Develop|development]] page.
Line 25: Line 27:
Please see ["MozillaTeam/Meetings"] for more details. === Quality Assurance ===
Line 27: Line 29:
== Contact == We document our QA procedures in [[MozillaTeam/QA]]
Line 29: Line 31:
'''IRC:''' {{{#ubuntu-mozillateam}}} on the [http://freenode.net Freenode Network][[BR]]
'''Mailing List:''' [https://lists.ubuntu.com/mailman/listinfo/ubuntu-mozillateam ubuntu-mozillateam]
==== Preview Testing ====
Line 32: Line 33:
== Quick Links ==
=== Swimming Upstream ===
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 35: Line 35:
When reporting upstream bugs in plugins (such as Java or Flash), make sure you report the bug in the right place. You can check which plugin you're using by going to the URL about:plugins in your Mozilla browser. ==== Trunk Testing ====
Line 37: Line 37:
==== Debian ==== We don't provide prebuilt binary packages for the main firefox development line (aka trunk).
Line 39: Line 39:
 * [http://www.debian.org/Bugs/ Debian] To test trunk (e.g. firefox 3.0 alpha) you can build the latest bzr sources. See [[MozillaTeam/BuildTrunk]] for instructions.
Line 41: Line 41:
==== Mozilla ==== === Wiki Maintenance ===
Line 43: Line 43:
 * [https://bugzilla.mozilla.org/ Mozilla] 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 45: Line 45:
==== Java ====
 * [http://bugs.sun.com/bugdatabase/index.jsp Sun Java]
 * [http://www.gnu.org/software/classpath/bugs.html GNU Classpath] (GCJ)
== 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 49: Line 48:
==== Flash ==== 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 51: Line 50:
 * [http://www.adobe.com/misc/bugreport.html Adobe Flash] == Subpages ==
Line 53: Line 52:
 * [http://sourceforge.net/tracker/?group_id=110956&atid=657852 GPL Flash]

 * [https://savannah.gnu.org/bugs/?group=gnash Gnash]
||<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 58: Line 56:
[:CategoryMozillaTeam], [:CategoryBugSquad], [:CategoryUbuntuTeams] [[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)