L10n:Ownership: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Following announcements: add bugzilla watching)
Line 20: Line 20:
=== Following announcements ===
=== Following announcements ===


Mozilla assumes that all owners follow the communication in .l10n on a regular basis.
Mozilla assumes that all owners follow the communication in the newgroups mozilla.dev.l10n on a regular basis.


We also assume that Localization Owners watch the alias firefoxl10n@otmail.com on bugzilla.
We also assume that Localization Owners watch the alias firefoxl10n@hotmail.com on bugzilla.


=== Firefox owners ===
=== Firefox owners ===

Revision as of 17:47, 6 November 2006

This is a draft, don't rely on any of this information just yet

Role

For each combination of a particular locale (en-US, pl, de, etc) and product (Firefox, Thunderbird, Toolkit, (SeaMonkey is a little special for now)), Mozilla requests an owner. This has nothing to do with someone owning stuff, but is a project management role. The owner role includes the following tasks, among others:

  • default owner of bugs,
  • key spokesperson in communications between the Mozilla project and the localization, or the specific part of the localization,
  • team leadership internal to the l10n team in question, in the particular area.

As you can tell by now, Owners are much more holding responsibility than ownership. It's just that owner is a prettier nown. We assume that owners will follow the Mozilla way of doing project management, shortly put iron fist in velvet glove.

Other obligations

CVS

Owners have CVS write access to the l10n repository.

Fill in full details of the process here

Following announcements

Mozilla assumes that all owners follow the communication in the newgroups mozilla.dev.l10n on a regular basis.

We also assume that Localization Owners watch the alias firefoxl10n@hotmail.com on bugzilla.

Firefox owners

Please look at L10n:Firefox Extras.

Trademarks

Owners should have read and understood the trademarks documents. And of course follow them.

Communication within the Mozilla Project

Every L10N team has to participate in the communication within the Mozilla project. This includes reading announcements as well as giving updates on big moves, changes, projects and situation inside the community/country to the Mozilla project management. Overall, it would be good to have Mozilla Localization Project up to date with your work. It does help everybody involved, if localization teams do this in a timely manner, notifying Mozilla of changes before they happen instead of afterwards. This is extremly important in any case related to trademarks use, promotion etc. Locale team should not start new mozilla related webpage or campaign, without Mozilla Foundation agreement. Depending on your region, you may want to cooperate with the Mozilla Foundation affiliate as well.

Peers

Every locale owner can choose his peers. He can choose as many peers as needed, but he is responsible for all their moves. Peer can reques CVS account and his owner should be his voucher.