[tracker] Require Latin characters on some profile fields

RESOLVED INVALID

Status

Participation Infrastructure
Phonebook
RESOLVED INVALID
5 years ago
a year ago

People

(Reporter: hoosteeno, Assigned: williamr)

Tracking

(Depends on: 1 bug, Blocks: 1 bug)

Details

(Whiteboard: [Triage 2015-04-17])

In order to limit the complexity of certain functions in Mozillians, we may need to require that some fields (such as location data fields) be limited to Latin characters. WilliamR will attach a list of these.
(Assignee)

Comment 1

5 years ago
Fields that should require non-Latin characters:
- The new location field(s) (bug 838766)
- Full Name

It appears these fields already require non-Latin characters:
- Groups
- Skills
- Languages

We should also create an optional field for 'Local Name' that allows users to add their name using non-Latin characters. This is tracked in bug 841224.

Are there other fields you suggest we require Latin characters?

The code for this bug should not be pushed until bug 841224 is resolved.
Depends on: 841224
So the full_name field should contain one or more of the following characters A-Z or a-z or ' or space (or in more precise regex "^[A-Za-z' ]+$").

Groups, Skills and Languages do not enforce latin characters now, it's just a bug of the fancy javascript library we're using (bug 835318). I believe that every field must be examined separately:
 - Languages can be latin only, same as full name "^[A-Za-z' ]+$"
 - Skills _maybe_ can be latin only. If we make them we definitely need a broader character set, for example allow the skill 'C++'. Let's brainstorm on the character set.
 - Groups: Are we re-structuring groups to 'Tags' (whatever) and 'Functional Areas' [1] and 'Internal Structure' (such as Brand Team). If yes we need to deal with each separately.

For all fields that we enforce a character set we need to provide a migration plan. 

[1] https://wiki.mozilla.org/Contribute/Areas

Hmmm this can grow big. Maybe turn this into a tracker and have different bugs per field?
(Assignee)

Comment 3

5 years ago
(In reply to Giorgos Logiotatidis [:giorgos] from comment #2)
>  - Groups: Are we re-structuring groups to 'Tags' (whatever) and 'Functional
> Areas' [1] and 'Internal Structure' (such as Brand Team). If yes we need to
> deal with each separately.

Great question - let's address this in a separate bug for Groups.

> For all fields that we enforce a character set we need to provide a
> migration plan. 

Noted. I can help make some suggestions with your help.

> Hmmm this can grow big. Maybe turn this into a tracker and have different
> bugs per field?

Yes, let's make this a tracker and I'll file bugs for each profile field we want to require Latin characters.
Assignee: nobody → williamr
Summary: Require Latin characters on some profile fields → [tracker] Require Latin characters on some profile fields
(Assignee)

Updated

5 years ago
Depends on: 841518
Whiteboard: [Triage 2015-04-17]
Blocks: 1154617
This is not valid anymore. Closing
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.