1028957 - Establish zone administration support for non-admins

Status: RESOLVED INVALID

(developer.mozilla.org Graveyard :: Wiki pages, enhancement)

Description

[Eric Shepherd [:sheppy]]

What problems would this solve?
===============================
We need to allow localization teams to create and manage zones so that they can do this without relying on admins to do the work for them, often without knowing the language they're trying to help build menus for.

Who would use this?
===================
Localization team leads, primarily, but possibly also select topic team leaders.

What would users see?
=====================
We need to be able to assign permission to convert a page to a zone, unconvert a page from a zone (if that's something that's even possible), and edit the zone's configuration. Then we need all the UX required for doing these things to be available to people with the permissions.

What would users do? What would happen as a result?
===================================================
Users would then use the gear menu options to create and manage zones as admins currently can, but with a (presumably) non-Django UX for doing the configuration work.

Is there anything else we should know?
======================================

Comment 1

[Eric Shepherd [:sheppy]]

This needs to block the general completion of localization improvements but I can't find any such tracking bug.

Comment 2

[Florian Scholz (Open Web Docs)]

This depends on findings in bug 943979 as we are unclear how to handle zone stuff in general.

Comment 3

[Jean-Yves Perrier [:teoli]]

Yeah, it looks like we are now talking about activating a zone for all locales at the same time. So this will make this bug void.

Also, we are more and more willing to have the CSS of zones under the control of the devs.

Except for localizing existing en-us zones, the creation of new zones is extremely rare.

Comment 4

[John Whitlock [:jwhitlock]]

Zones have been removed (bug 1462475).