L10n:Features/Web/Editor

From MozillaWiki
Jump to navigation Jump to search
Please use "Edit with form" above to edit this page.

Status

Web-based Editor (TBD)
Stage Draft
Status `
Release target `
Health OK
Status note Needs a full definition of phases and scope

{{#set:Feature name=Web-based Editor (TBD)

|Feature stage=Draft |Feature status=` |Feature version=` |Feature health=OK |Feature status note=Needs a full definition of phases and scope }}

Team

Product manager `
Directly Responsible Individual Axel Hecht
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=`

|Feature feature manager=Axel Hecht |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

A web-based editor for product localization.

The current idea is to have a mix of etherpad and koala, with some additional tools to hook into mozilla's l10n infrastructure.

The goal is a source editor that makes it easy to do things right, and hard to get things wrong.

2. Users & use cases

Localizers for Firefox and other projects using the same infrastructure.

Right now, the existing tools are not created to be interoperable, and none fits the bill for everyone. We need a tool that's easy to get started with and doesn't lock you in to use that one tool for the rest of your life.

3. Dependencies

Webdev: We'll need webdev resources, potentially external. Infrastructure: In particular for new contributors, we need low-policy hg repositories (assuming hg for product here) Governance: The idea is to edit hg repositories on the web. Need to figure out how to do that from a policy and security standpoint. Release Engineering: Likely not the initial stage, but we'd like to have a tool to trigger aurora repacks out of this system. For new contributors, this wouldn't be the regular repos, but more like try builds.

4. Requirements

The UI needs to be snappy. Most webtools for l10n suffer from the network lag inbetween minor items of work. There need to be assistive components like compare-locales, local parsers with error reports, strong highlighting. Also MT and TM hooks. The tool should be "easy" to set up independently, to take with you on l10n sprints and the like.

Non-goals

This is a separate tool from other l10n-related tools, in particular, integrating this into elmo is a non-goal. Also, it's not intended to be a form-based editor, or mimick what other popular tools do.

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=A web-based editor for product localization.

The current idea is to have a mix of etherpad and koala, with some additional tools to hook into mozilla's l10n infrastructure.

The goal is a source editor that makes it easy to do things right, and hard to get things wrong. |Feature users and use cases=Localizers for Firefox and other projects using the same infrastructure.

Right now, the existing tools are not created to be interoperable, and none fits the bill for everyone. We need a tool that's easy to get started with and doesn't lock you in to use that one tool for the rest of your life. |Feature dependencies=Webdev: We'll need webdev resources, potentially external. Infrastructure: In particular for new contributors, we need low-policy hg repositories (assuming hg for product here) Governance: The idea is to edit hg repositories on the web. Need to figure out how to do that from a policy and security standpoint. Release Engineering: Likely not the initial stage, but we'd like to have a tool to trigger aurora repacks out of this system. For new contributors, this wouldn't be the regular repos, but more like try builds. |Feature requirements=The UI needs to be snappy. Most webtools for l10n suffer from the network lag inbetween minor items of work. There need to be assistive components like compare-locales, local parsers with error reports, strong highlighting. Also MT and TM hooks. The tool should be "easy" to set up independently, to take with you on l10n sprints and the like. |Feature non-goals=This is a separate tool from other l10n-related tools, in particular, integrating this into elmo is a non-goal. Also, it's not intended to be a form-based editor, or mimick what other popular tools do. |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority Unprioritized
Rank 999
Theme / Goal `
Roadmap `
Secondary roadmap `
Feature list `
Project `
Engineering team `

{{#set:Feature priority=Unprioritized

|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=` }}

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}