WordPress.org

Making WordPress.org

Opened 4 years ago

Closed 3 years ago

Last modified 5 weeks ago

#1398 closed enhancement (fixed)

New user roles for Rosetta sites

Reported by: petya Owned by:
Milestone: Priority: high
Component: International Sites (Rosetta) Keywords:
Cc:

Description

Given the changed demand for translation work coming from the plugins and themes added to translate.wordpress.org, here's a suggestion for a change in the user roles and privileges of users of the Local Rosetta sites.

There are three main types of roles we need to think about that are granted from a Rosetta site:

  • A community and publishing role – people who update the site, publish content about releases, take care of the showcase, publish information about local events, meetups. Having dedicated roles for this will help local communities pick up the communication from their official tool.
  • A translation management role – people who are in charge of translations, releasing translations and managing translation permissions
  • Forum moderators - people who are can moderate content on local forums

Some of the roles might overlap, but it's important to be able to separate the two should people be interested in that.

Based on that, here’s the proposed changes to roles, role titles and permissions:

Locale Manager role

Add a Locale Manager role (current Editor role with a couple of new perks in the future)

A Locale manager will be able to:

  • Create and edit site content
  • Add new users for all roles
  • Modify the showcase
  • Update the theme settings - change the header, change the welcome message
  • Manage menus
  • Validate strings on any project for the associated locale
  • Can add other General translation editors
  • Can add Per project translation editors
  • Can create and release translations
  • Can do deploy requests for Rosetta

Community/publishing roles:

We keep the general WordPress roles for the community/publishing users:

  • Editor
  • Author
  • Contributor
  • Subscriber

None of these roles should have any translation management privileges. Editors should be able to add other editors.

Translation management roles

Two new roles suggested here

General translation editor

  • Can validate strings on any project for the associated locale
  • Can add other General translation editors
  • Can add Per project translation editors
  • Can create and release translations
  • Can do deploy requests for Rosetta

Per project translation editor

  • Can validate strings for a project they’re assigned to by a General Translation Editor

Change History (11)

#1 @ocean90
4 years ago

  • Priority changed from normal to high

This ticket was mentioned in Slack in #polyglots by petya. View the logs.


4 years ago

#3 @ocean90
4 years ago

Related: #1240

Point 3 is done with r2197​.

Last edited 4 years ago by ocean90 (previous) (diff)

This ticket was mentioned in Slack in #meta by ocean90. View the logs.


3 years ago

#5 @ocean90
3 years ago

#1930 was marked as a duplicate.

This ticket was mentioned in Slack in #polyglots by ocean90. View the logs.


3 years ago

#7 @ocean90
3 years ago

In 4080:

Rosetta: Add role manager for custom roles which are used on the main site.

See #2003, #1398.

#8 @ocean90
3 years ago

In 4083:

Translate, Rosetta Roles: Add support for the new locale manager role.

See #1398.

#9 @ocean90
3 years ago

In 4084:

Rosetta Roles: Remove handling for custom roles.

This has been migrated to the Rosetta plugin.

See #2003, #1398.

#10 @ocean90
3 years ago

  • Resolution set to fixed
  • Status changed from new to closed

This ticket was mentioned in Slack in #polyglots by tobifjellner. View the logs.


5 weeks ago

Note: See TracTickets for help on using tickets.