Week ending 7/19
This report previews planned work. Nothing below has shipped yet.
Executive summary
This week's focus is designing volunteer login with edit rights, so trusted volunteers can review, update, and approve Language Package content directly instead of routing every change through the internal team.
What's new
-
Change
Planning volunteer login with edit rights to review, update, and propose changes to Language Package content.
Impact
Distributed reviewers could correct doctrine-risk terms and glossary entries directly, instead of every fix routing through the internal team.
Next action
Draft the login and permissions design, scoped to which fields a volunteer editor may change.
-
Change
Planning a two-approver requirement before any volunteer-submitted edit goes live.
Impact
No single volunteer account, if mistaken or compromised, can change doctrine-checked content unilaterally.
Next action
Write the approval-routing instructions covering who qualifies as an approver and how a second approver is assigned per language.
-
Change
Planning an edit history view so every approved change is traceable to its two approvers.
Impact
Any future doctrine question can be traced to exactly who approved a change and when.
Next action
Confirm whether edit history lives in the existing Language Package files or a separate audit log.
Business impact
Volunteer edit access is the platform's biggest lever for scaling doctrine review capacity without growing the internal team, but it only works if every approved change is provably safe before it reaches Crowdin.
Metrics
No metrics recorded for this period yet.
Risks
Opening edit access before the two-approver workflow is proven risks an unreviewed doctrinal change reaching production; login and permissions security also has to be right from day one given the sensitivity of the content.
Decisions needed
Leadership: decide whether the two-approver requirement applies to every volunteer edit or only Critical- and High-risk doctrine terms, and confirm who is authorized to serve as an approver for each language.
Next Week
- Circulate the volunteer login and approval workflow design for feedback
- Begin scoping which Language Package fields are editable by volunteers
Key dates
- August 1, 2026 — Target: circulate the volunteer login and two-approver workflow design for review