pontoon icon indicating copy to clipboard operation
pontoon copied to clipboard
verified publisher icon mozilla

Improve project setup experience

Open bugzilla-to-github opened this issue 5 years ago • 2 comments

This issue was created automatically by a script.

Bug 1608225

Bug Reporter: @mathjazz CC: @flodolo Depends on: Bug 1685818 See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1593600

Bug 1593600 hints at a couple of issues of the current project setup:

  1. Having to set up a project on stage server just to test that sync actually works is not acceptable:
  • It requires each deployment to have at least two instances of Pontoon, which doesn't scale
  • It requires the same setup to be done twice for each project
  • To a large extent, it can be automated

UPDATE 09/01/21: This issue has been mitigated as part of bug 1627877.

  1. The project setup form has become huge (UX) PITA over time, which is even more annoying when setting up simple (or test) projects:
  • Only 5 fields are required, and yet we always show all sections, including the barely used ones like In-context localization.
  • Save/Sync buttons are only shown at the bottom and need to be clicked on one after another, but since the page reload in-between, one needs to scroll.
  • Tag management UX is inconsistent with the rest of the app and requires the use of Django Admin to set deadlines.

Let's use this bug to collect issues of the current process and ideas for the new one.

bugzilla-to-github avatar Jan 09 '20 03:01 bugzilla-to-github

Comment Author: @mathjazz

A quick idea for a new project setup process:

  1. PM only provides the repository URL
  • optionally, more complex repository config can be specified (including toml file)
  1. A dry run sync checks and reports if it can:
  • pull from and push to repository
  • detect reference and l10n files (via project configuration or without)
  1. A simplified project setup form is pre-filled and shown for review, only containing required fields:
  • slug (retrieved from repository URL)
  • name (same as slug)
  • locales (retrieved in step 2, see bug #960291)
  • repository type, url and branch (given in step 1)

  1. Optionally, other sections get filled (project info, tags, in-context)

  2. Project setup form should also allow to:

  • Sync (and Force Sync? and Save and Sync?) a project
  • Make project only visible to PMs during testing period (bug #1602490 might be related)

bugzilla-to-github avatar Jan 09 '20 03:01 bugzilla-to-github

Comment Author: @mathjazz

*** Bug #1593600 has been marked as a duplicate of this bug. ***

bugzilla-to-github avatar Jan 20 '20 01:01 bugzilla-to-github