Closed Bug 965836 Opened 11 years ago Closed 11 years ago

Determine our process for "turning on" a new language

Categories

(Webmaker Graveyard :: webmaker.org, defect)

Product:
Webmaker Graveyard
Component:
webmaker.org
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: cassie, Assigned: alicoding)

Details

(Whiteboard: [workweek-l10n] [workweek])

Perhaps as MVP, this announcement gets folded into a blog post / email newsletter, but we could also have a messaging system to maker users aware of changes. Alternatively, this could be a part of a "Systems Status and Updates" page we had previously discussed for Webmaker.
Whiteboard: uxdesign, communications → [uxdesign][communications][workweek-l10n]
Whiteboard: [uxdesign][communications][workweek-l10n] → [workweek-l10n] [workweek]
Assignee: nobody → ali
This is our current process of turning on new language. When a language reach at a certain percentage where we determine that it is ready to be on our production site (Current state 80%+) we will: 1. Send an announcement on Transifex to let people from that team know. 2. Weekly changelog blog post from Matt (Might not be for a while) 3. Sending email in our mailing list (Dev list or if they have their own l10n dedicated list I usually email them too) 4. Let them know on their IRC channel One thing that is still missing which is the Notification based on their locale, but this is not possible until our notification system is implemented and ready.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.