keybase / keybase/client

[Inquiry] Translation and i18n plans

Open
#7,368 12 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Are there any? May I help? Are you opposed as a project to translating at this point in the project?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the discussion on issue #7368, since no files, tests, or entry points are identified. Clarify whether the project wants translation support and define the languages, scope, and acceptance criteria before implementation; the issue currently does not specify what done looks like.

Written by the indexing model from the issue text.

Assessment

Domain
internationalization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.